Overview
Placeholders let you inject dynamic data into your workflows. They can access data from multiple sources and handle both regular and sensitive information.
Using Placeholders
Standard Placeholders
Use double curly braces for regular data:
{{ user.name }}{{ trigger.form_id }}{{ previous_action.response.id }}
Sensitive Data Placeholders
Use percent and curly braces for sensitive data:
{% api_key %}{% webhook_secret %}
Data Sources
Account Data
Data available across your application:
- Configuration values
- API credentials
- Global settings
User Data
User-specific information stored in user_data:
- Preferences
- Settings
- Custom fields
Execution Data
Data provided when the workflow starts:
- Event information
- Form submissions
- API payload
- Scheduled event data
Action Data
Data from previously executed actions:
- API responses
- Calculation results
- Transformed data
Node Data
Data configured in the action form by the workflow designer:
- Custom parameters
- Action settings
- Configured values
Data Precedence
When the same field exists in multiple sources, from lowest to highest precedence:
- Account Data (most general)
- User Data
- Execution Data (trigger data)
- Action Data
- Node Data (most specific)
Schema Definition
When creating triggers and actions, define their data schemas to:
- Show available placeholder fields
- Document data types
- Enable autocomplete in the builder
- Validate data usage