| Trigger | Starts when | Has a contact? |
|---|---|---|
| External Integration Event Received | Any event your store or website sends through the integration API. Use Provider filter, Event type filter and External instance filter to narrow it down (blank = all events) | Created or linked automatically from the event’s customer data before the first action step |
| Store and website events: Customer…, Cart…, Checkout…, Product…, Order…, Lead…, Form Submitted, Newsletter…, Coupon… and similar | That specific event arrives (21.3) | Maybe. Add Add/Upsert Contact first if later steps need one |
| Post Published / Updated / Deleted, Product Published / Updated | Content changes on a connected site | Never (contactless) |
| Triggered from Broadcast | A broadcast event you attach it to: WhatsApp sent / delivered / read / replied, or email sent / opened / link clicked | Yes, the recipient |
| Scheduled | On a daily, weekly or monthly schedule (11.9) | Never (contactless) |
Watch out:
- Every store event starts two triggers: its specific trigger (for example Order Completed) and External Integration Event Received. If you have an unfiltered "External Integration Event Received" workflow as well as an "Order Completed" workflow, both run for each order and the customer may get two messages. Filter the general one, or use only the specific ones.
- On External Integration Event Received, an event without a customer name, email or WhatsApp number fails at the first action step ("…does not contain enough customer data to create a contact"). Use the specific contactless trigger for content events.
- Triggered from Broadcast never runs on its own. Publish it, then attach it on a campaign’s New Broadcast page under Automation → Add workflow (9.4.3, 10.5.2).
