Flow-control nodes
| Node | Role |
|---|---|
| Start | The entry point — one per flow, runs no action. |
| Goal | A successful end. Reaching it marks the run completed. A flow can have several. |
| Error | An error end — handles failure cases without marking the run complete. |
| Condition | Branches on a comparison. Operators: equals, !=, >, <, >=, <=, contains, starts_with, ends_with, in, not_in, is_null, is_not_null, is_true, is_false, regex, combined with and / or. |
| Wait | Pauses the flow for a set time before continuing. |
| Load View | Counts a saved View and fires an event per record (scheduled / system templates). See Scheduled events. |
Action node
An action node runs one action plugin — the unit of work that calls a webhook, updates a contact, creates content, sends an email, and so on.Field mappings
Almost every action injects values through field mappings. A mapping is either a fixed literal or a value resolved dynamically from the run’s context by a dot-notation path:| Source | Resolves to |
|---|---|
| Fixed | A literal value you type (string, number, array). |
| Path / context | A value read from the run context (see roots below). |
| Function | A built-in value computed at run time (for example now). |
| Root | Meaning | Examples |
|---|---|---|
object.* | The triggering subject — contact, user, or changed record. | object.id, object.email, object.attributes.tier |
enrichment.* | Data supplied when the event fired (validated against the template schema). | enrichment.rating, enrichment.amount |
nodes.{slug}.* | The output of a node that ran earlier in the flow. | nodes.fetch-data.response.items |
Action plugins
Each action node uses one plugin. The substantial plugins each have their own page; the ecommerce cart and order actions share one:Webhook
Call an external HTTP endpoint.
Endpoint
Call an internal CXF endpoint.
Contact update
Update the contact’s data.
Content instance
Create/update/delete content.
Set insight
Aggregate events onto an attribute.
Send email
Email one contact.
Send email to contacts
Email a set of contacts.
Document creation
Create a contact document.
Document update
Update a contact document.
Manage document
Create/update/delete/publish a document.
Product creation
Create a product with inventory.
Asset creation
Create a DAM asset.
Cart & order actions
Build a cart and take payment.
Availability matrix
Which actions a template can use depends on its type:| Action | Contact | User | Scheduled | System |
|---|---|---|---|---|
| Webhook | ✅ | ✅ | ✅ | ✅ |
| Set insight | ✅ | ✅ | ✅ | ✅ |
| Send email | ✅ | ✅ | ✅ | ❌ |
| Send email to contacts | ❌ | ✅ | ✅ | ❌ |
| Content instance | ❌ | ✅ | ❌ | ❌ |
| Endpoint | ✅ | ❌ | ❌ | ❌ |
| Contact update | ✅ | ❌ | ❌ | ❌ |
| Document creation | ✅ | ❌ | ❌ | ❌ |
| Document update | ✅ | ❌ | ❌ | ❌ |
| Manage document | ❌ | ✅ | ❌ | ❌ |
| Product creation | ❌ | ✅ | ❌ | ❌ |
| Asset creation | ❌ | ✅ | ❌ | ❌ |
| Cart & order actions | ✅ | ❌ | ❌ | ❌ |
Related
Events & Automation
Back to the overview.
Event types
What each template type can trigger and use.