contact) is triggered by a contact action through the
public Contact API — a survey submission, a chat message, a form completion. It runs
as the contact (an authenticated session or a ghost). It’s the public surface of
Events & Automation.
Authentication
| Aspect | Behaviour |
|---|---|
| Actor | The triggering contact (authenticated or ghost). |
| Anonymous | Supported when requires_authentication = false. |
| Goal node | Required to enable the template. |
Sessionless (anonymous) events
Settingrequires_authentication = false makes the event sessionless: an
anonymous (ghost) contact can trigger it. When sessionless:
- Only unbound attributes (those not tied to a profile) can be updated.
- The ghost’s data is limited to basic identification.
- Enrichment is still validated against the template schema.
Available actions
These action plugins can run in a contact event:Webhook
Set insight
Send email
Endpoint
Contact update
Document creation
Document update
Cart & order actions
Related
Event types
All four types compared.
Contacts
Who triggers a contact event.