Workflow Inputs
- What workflow inputs are and how the
{{variable}}placeholder syntax works - Common input variables available from different trigger types
- How to define custom inputs for manual workflows
- How to use inputs inside workflow steps
Workflow inputs are dynamic values that carry data from the trigger event into your workflow steps. They use the {{variable}} placeholder syntax, which gets replaced with real data each time the workflow runs. This is what makes your workflows flexible -- instead of hardcoding values, you use placeholders that adapt to each specific execution.
How the placeholder syntax works
Anywhere you can enter text in a workflow step, you can insert a placeholder by wrapping a variable name in double curly braces. When the workflow runs, each placeholder is replaced with the actual value from the trigger event or the system context.
For example, if you type the following in a message step:
Hello {{client.name}}, your appointment is confirmed for {{event.date}}.
The system replaces {{client.name}} with the real client name (e.g., "Maria Silva") and {{event.date}} with the actual date (e.g., "2025-03-15"), producing:
"Hello Maria Silva, your appointment is confirmed for 2025-03-15."
Common input variables
The variables available to your workflow depend on the trigger type and the event that fired it. Here are some common examples:
| Variable | Description |
|---|---|
{{client.name}} | The name of the client associated with the event |
{{client.phone}} | The client's phone number |
{{client.email}} | The client's email address |
{{event.date}} | The date of a scheduled event or appointment |
{{trigger.channel}} | The channel through which the trigger event occurred (e.g., WhatsApp, web chat) |
{{message.text}} | The content of a received message |
{{employee.name}} | The name of the employee associated with the event |
Variable names use dot notation to access nested data. The part before the dot (e.g., client, event, trigger) indicates the data source, and the part after the dot (e.g., name, date, channel) indicates the specific field.
Using inputs in steps
When configuring any step in the Etapas section, simply type the {{variable}} placeholder directly into the text fields. The system will recognize the placeholder and replace it at runtime. You can combine static text with multiple placeholders in the same field:
Dear {{client.name}}, you have an upcoming appointment on {{event.date}}. If you need to reschedule, reply to this message on {{trigger.channel}}.
Custom inputs for manual workflows
When your workflow uses a manual trigger, you can define custom input fields that the employee must fill in before executing the workflow. This is useful when the workflow needs information that is not available from an automatic event.
For example, you might define a custom input called report_date that the employee enters when clicking the executeManual button. That value then becomes available as a {{variable}} placeholder throughout the workflow steps.
Custom inputs make manual workflows more versatile, since the same workflow can produce different results depending on what the employee enters each time.
Always wrap {{variable}} references in backticks when writing about them in documentation or notes. The double curly brace syntax is interpreted by the system as a placeholder, so leaving it unescaped in documentation contexts can cause parsing errors.