Comparison
| Aspect | Contact | User | Scheduled | System |
|---|---|---|---|---|
| Triggered by | A contact action via the public Contact API | An authenticated staff user via the User API | A recurring schedule (RRULE), every minute scanner | Automatically, on record create/update/delete |
| Actor | A contact (authenticated or ghost) | A user | None (system) | None (system); the subject is the changed record |
| Anonymous | Yes — when requires_authentication = false | No | N/A | N/A |
| Context seeded | The contact + enrichment | The user + enrichment | Built from the schedule / iterated View | The record + the changes diff |
| Goal node required | Yes | Yes | No | No |
The set of action plugins you can
use depends on the template type — see the
availability matrix. For
example,
endpoint and the cart actions are contact-only, while content_instance,
product_creation, and asset_creation are user-only.The four types
Contact events
Triggered by a contact — the public surface, with anonymous (sessionless) support.
User events
Triggered by an authenticated staff user; internal workflows.
Scheduled events
Fired on a recurring schedule, typically iterating a View.
System events
Fired automatically when a record is created, updated, or deleted.
Related
Events & Automation
Back to the overview.