What are Triggers?
Triggers define how a composer’s workflow is started. Each composer has a trigger type configured at the composer level. When a trigger fires, it passes contextual data into the workflow that you can access with{{trigger.*}} template variables.
Trigger Types
Manual
Run the workflow on demand using the Run button in the composer or canvas header. Manual triggers are useful for testing and for workflows that should only run when explicitly started.Event
Event triggers fire automatically when specific database events occur. The trigger data from the event is available as{{trigger.*}} in your steps.
Available events:
| Event | Description |
|---|---|
| Contract Created | Fires when a new contract is created |
| Contract Updated | Fires when an existing contract is modified |
| Contract Deleted | Fires when a contract is removed |
Schedule
Schedule triggers run the workflow automatically based on a CRON expression. Common patterns:| CRON Expression | Schedule |
|---|---|
0 0 * * * | Daily at midnight |
0 9 * * 1-5 | Weekdays at 9 AM |
0 */6 * * * | Every 6 hours |
0 0 1 * * | First day of every month |
*/30 * * * * | Every 30 minutes |
Webhook (Coming Soon)
Webhook triggers will allow external systems to start a workflow by sending an HTTP request to a unique URL. This enables integrations with third-party services that support outbound webhooks.Related Documentation
Composers
Triggers are configured at the composer level.
Steps
Use trigger data in your steps with template variables.
Test & Deploy
Test your triggers before deploying to live.