Integrations
Integration health — Everything we sent to GoHighLevel, everything it sent back, and every lead your vendors posted in. Admins only; agents don’t get this tab.
The dialer writes to GoHighLevel constantly: tagging a contact with the disposition an agent picked, updating contact fields, marking a contact Do-Not-Call, posting a finished call and its recording to the contact’s timeline, and creating a contact for someone who rings in and isn’t in GoHighLevel yet. GoHighLevel writes back too, telling us a contact was created, updated or deleted, had its tags changed, or was marked Do-Not-Call. This tab is the record of both halves, and whether each one worked.
Every row is a plain sentence, not a technical log line — Tag contact as “dialer-sale”, Update 3 contact fields, Log completed call recording to GoHighLevel timeline, GoHighLevel changed a contact’s Do-Not-Call flag.
Leads your vendors post in are the third thing recorded here, and they’re their own Source: pick Vendor posts to see only those. A lead you turned away — a duplicate, a do-not-call number — shows as Rejected carrying the same response code you sent back to the vendor, so it’s the screen to open when a vendor asks why their leads aren’t arriving.
Filters
Section titled “Filters”| Filter | Options |
|---|---|
| Date range | All time, Today (the default here), Last 7 days, Last 30 days, or Custom range — pick From and To, then Apply |
| Source | All, We called GHL (something we sent), GHL called us (something GoHighLevel told us), Vendor posts (a lead a vendor sent in) |
| Result | Failures (the default), Rate-limited, Everything |
| Search box | Search what happened… — matches the sentence in the What happened column |
Anything you change from the defaults shows as a removable chip under the filters, with Clear all beside them. Reset in the header does the same job as Clear all: both put Source, Result and the search box back to their defaults, and neither touches the date range.
The table
Section titled “The table”| Column | What it shows |
|---|---|
| Time | When it happened, in your timezone |
| What happened | The plain-English sentence. On something we sent, how long GoHighLevel took to answer, in milliseconds |
| Result | The badge below |
| Related | View contact → when the event was about one specific contact. It opens that contact in GoHighLevel, in place of this screen |
| Result | What it means |
|---|---|
| OK | We sent it and GoHighLevel accepted it |
| Processed | GoHighLevel told us something, or a vendor posted a lead, and we handled it |
| Rate-limited | GoHighLevel refused it because too much was sent at once |
| Failed (404) | It didn’t land — the number is the status code that came back. Failed on its own means it never got far enough to have one |
| Rejected (210) | A vendor’s lead that we turned away on purpose — the number is the response code the vendor got back, listed in full on their posting instructions |
Reading a failure
Section titled “Reading a failure”Click any row to expand it. You get a labelled list — Source (We called GoHighLevel, GoHighLevel called us or A vendor posted to us), When, the status or response code, and Latency — never a wall of code. Copy technical details puts the underlying message on your clipboard, which is what to send on if you’re asking for help.
Then act on it:
- A failure means that change wasn’t in GoHighLevel at that moment — a tag, a contact field, a recording on the timeline. Open that contact in GoHighLevel to see whether it’s there now, and put it right by hand if it isn’t.
- A failure on creating an incoming caller is the one with no contact to open: that caller has no record at all, so their call shows as a plain phone number on Calls with nothing to click. Add them by hand if it was a caller worth keeping.
- A single Rate-limited row is usually self-correcting. We slow our own writes down for a moment when GoHighLevel says to. A run of them means the account is pushing more at GoHighLevel than it will take.
- The same failure on every row points at the connection to GoHighLevel rather than at any one contact. That’s the point to copy the technical details and get in touch.
- A Rejected vendor lead is not a fault to repair — it’s your own rules working. The response code says which rule: a duplicate you’d already been sent, a number on your do-not-call list, a number outside the area you dial. Send the vendor the code if they’re asking why a lead didn’t arrive.
How long rows are kept
Section titled “How long rows are kept”Stated at the foot of the table: Failures are kept 90 days, successes 7. A failure from three months ago is gone, so investigate while it’s fresh — and note that the date range can’t reach back further than the rows that still exist.