🇪🇸 Español 🇬🇧 English 🇧🇷 Português

Trigger: Message Delivered

Fires when Meta confirms an outbound message reached the contact's device (the grey double check).

Jul 11, 2026

The Message Delivered trigger fires when the channel (WhatsApp or another supported channel) confirms that an outbound message reached the contact's device — the grey double check, technically distinct from "read".

When to use it

  • Measure actual deliverability of a campaign, beyond just "sent".
  • Start a wait period before retrying contact, only if the message actually got delivered.
  • Feed internal reporting on messaging quality per channel.

Requirements

A channel that supports delivery receipts (WhatsApp Cloud API is the main case). No special plan is required.

Filters available

  • Channel type.
  • Specific channel.

Variables available

  • $message.id: internal message ID
  • $message.external_id: Meta's wamid
  • $message.delivered_at: when delivery was confirmed
  • Conversation and contact variables

How to build it

  1. Go to WorkflowsNew workflow.
  2. Drag a Trigger node → pick Message Delivered (under Messages).
  3. Filter by channel type or a specific channel if you run several WhatsApp lines.
  4. Add an action, e.g. Log activity with $message.delivered_at.
  5. Save and activate.

Example

Workflow "Delivery metrics": fires on the "WhatsApp Sales" channel → Log activity: Message {{message.external_id}} delivered at {{message.delivered_at}}.

Tips

Don't confuse this with "read": a message can be delivered and never opened. If you need to know the customer actually saw it, use the Message Read trigger instead.

Troubleshooting

If you never see any runs, check that the contact has WhatsApp active on their phone (delivery reports depend on Meta) and that the channel's number isn't blocked.

Was this helpful?

Related articles