Pause the repeated action and inspect history
If a customer receives repeated copies, pause the relevant external workflow while you inspect the sends. Compare the sending number, message IDs, timestamps, and workflow execution records.
Look for overlapping automations, repeated enrollment, a teammate replying alongside an automation, or a retry after a timeout. Similar text alone does not show whether two distinct sends occurred; compare the recorded IDs.
Deduplicate before creating a send
The public send API does not currently accept a client-supplied idempotency key. Your integration should durably record the workflow execution or business action before sending and save the returned Miss Blue message ID.
A webhook delivery can be retried. Process each event envelope ID once, and update existing message mappings when new information arrives for the same message. Do not turn your own outbound synchronization events into a fresh customer reply.
Reconcile an uncertain result
- If a send times out or reports Outcome unknown, inspect the message record and the conversation first.
- If a file and text were sent together, check each resulting message separately.
- Only retry after you can distinguish a confirmed failure from an attempt that may already have reached the sending system.
- If the outcome stays uncertain, give support the request and message details before sending another copy.
Check GoHighLevel confirmation states
The connected inbox deduplicates repeated deliveries of the same GHL message ID. Different workflow executions can still represent separate sends. Confirmation missing requires checking the actual GHL conversation; the integration deliberately avoids blindly posting another copy.