Outbound Send Status (pending, sent, failed) and Provider Message ID, and set Outbound Send Status = pending as the first step before your webhook or n8n send node runs.
message_id is present in the response payload: only update Outbound Send Status to sent when the ID exists, and route empty or error responses straight to an Internal Notification alert.
15-minute Wait step in your workflow), check whether Outbound Send Status is still pending: if no provider message_id was written back within 15 minutes, move the card to a retry queue and ping your ops channel.
Add silent-failure detection and 15-minute send confirmation checks in sub-account <YOUR_LOCATION_ID>: 1. In Settings > Custom Fields, create Outbound Send Status (pending / sent / failed) and Provider Message ID fields. 2. In Automation > Workflow Builder and n8n, set Outbound Send Status to pending before the send step, disable Continue On Fail and Always Output Data, and verify a non-empty message_id before marking the send complete. 3. Add a 15-minute Wait and If/Else watchdog in Automation > Workflow Builder that sends an Internal Notification if Outbound Send Status remains pending.
# Inspect custom fields and webhook send verification workflows in the sub-account ghl-crm custom-fields list --context <YOUR_CONTEXT> --location <YOUR_LOCATION_ID> ghl-crm workflows list --context <YOUR_CONTEXT> --location <YOUR_LOCATION_ID>
Official GHL MCP vs. ghl-tools: HighLevel’s official hosted MCP (services.leadconnectorhq.com/mcp) covers public v2 CRM records (contacts, opportunities, appointments, conversations). ghl-tools MCP complements it with workflow graph inspection & recipes, funnel/form builders, DNS/BIMI checks, and ghl-crm doctor audits.
200 OK with {} or status: 'queued' and no message ID, or n8n's Always Output Data / Continue On Fail toggle passes an empty item downstream.pending > sent state transition in Settings > Custom Fields, check for a real provider message_id right after the send step in Automation > Workflow Builder (and n8n)| Step | Menu Path in GHL | Action |
|---|---|---|
| Step 1 | Settings > Custom Fields | Create Contact or Opportunity fields for Outbound Send Status (pending, sent, failed) and Provider Message ID, and set Outbound Send Status = pending as the first step before your webhook or n8n send node runs. |
| Step 2 | Automation > Workflow Builder | In Automation > Workflow Builder (and your n8n send node with Continue On Fail and Always Output Data turned off), place an immediate If/Else check verifying that message_id is present in the response payload: only update Outbound Send Status to sent when the ID exists, and route empty or error responses straight to an Internal Notification alert. |
| Step 3 | Automation > Workflow > Execution Logs | In Automation > Workflow > Execution Logs (paired with a 15-minute Wait step in your workflow), check whether Outbound Send Status is still pending: if no provider message_id was written back within 15 minutes, move the card to a retry queue and ping your ops channel. |
Connect Claude Code, Cursor, or OpenAI Codex to our ghl-tools MCP Server & Rust CLI to build workflows, forms, and funnels from your editor, or start your GoHighLevel plan through our partner link to unlock $612+ in ready-to-import kits (including GHL & n8n Silent Node Failure Watchdog Pack) and weekly live clinics.