09. Automation Engine/Dynamic Context
Stateful Context & Variables
Inject dynamic customer names, order totals, and previous step outputs into downstream SMS, WhatsApp, and Email actions using real-time variable interpolation.
DYNAMIC INTERPOLATION
100% Dynamic
Dot-Notation Path Resolution
“Personalize every message on the fly. Reference customer names, discount codes, or previous node outputs with double-bracket tags.”
Stateful Workflow Variables
The {{variable.path}} Syntax
GN-Apex scans all action configurations and recursively resolves double-bracket tags against the live WorkflowContext before dispatching payloads:
handlebars
| 1 | Hello {{triggerPayload.customerName}}, your order #{{triggerPayload.orderNumber}} for {{triggerPayload.total}} has been confirmed! |
Available Context Namespaces
Reference data across two primary variable namespaces:
| Parameter | Type | Requirement | Description |
|---|---|---|---|
| triggerPayload.* | Initial Event | Optional | Data emitted by the root trigger (e.g., customerName, email, phone, totalAmount, cartItems, admissionNumber). |
| steps.[nodeId].output.* | Step Output | Optional | Outputs returned by previous action nodes (e.g., generated discount codes, tracking IDs, payment verification references). |
Dynamic Communication Templates
Examples of dynamic message templates configured in the visual builder:
text
| 1 | Hi {{triggerPayload.name}}! 👋 You left {{triggerPayload.itemCount}} items in your cart. Complete your purchase now: https://yourbrand.com/checkout?recover={{triggerPayload.cartId}} |
Safe Fallbacks & Type Coercion
Safe Property Resolution
If a referenced path (e.g.
{{triggerPayload.lastName}}) is undefined or null, the interpolation engine replaces the tag with an empty string instead of failing the workflow step.