Action bodies (email subject + body, message text, queue instructions, etc.) support {{path}} substitution. Paths reference the trigger payload using dotted notation.
Common trigger-payload variables
Variable | Notes |
|---|---|
| The numeric area ID. Use this for links. |
| The acting user's display name. Most-used. NB: not `user_name`. |
| Email of the acting user (when present). |
| Plain-text body, for diary entries. |
| Form answers keyed by question label (forms triggers). |
| eMAR outcome code 1-8 (eMAR triggers). |
| Medication name (eMAR triggers). |
System variables
The executor automatically injects current-time variables into every payload:
{{system.current_date}}— YYYY-MM-DD format.{{system.current_time}}— HH:MM:SS.{{system.current_iso}}— full ISO-8601 timestamp.{{system.current_unix}}— Unix seconds.
Workflow variable store
Use vars.set / vars.increment to write into the variable store. Reading back via {{vars.<name>}} is supported in live runs but may not surface in the test endpoint — test the production behaviour with a real fire.
Missing paths
A reference to a path that doesn't exist in the payload renders as an empty string () rather than {{undefined}}. Double-check field names against the trigger's payload schema when testing.