Flow Triggers
Run a Flow on a schedule, from an integration event, or from a voice call by attaching a trigger to the Flow's Start node.
Flow triggers start a Flow without someone selecting Run Flow in the Designer. Add them directly to the Start node so the trigger, its settings, and the data it supplies remain visible with the Flow.
Trigger types
Choose the trigger type based on what should start the Flow:
| Trigger type | Use it when | What you configure |
|---|---|---|
| Scheduled Trigger | The Flow should run at a recurring time, such as every Monday morning or every hour. | The schedule, Flow version, optional agent identity, failure notifications, and input data. |
| Integration Trigger | An event in a connected application should run the Flow. | The application provider, a connected Integration, the provider's event type, and any event-specific options. |
| Voice Trigger | An inbound or outbound phone call should run a voice Flow. | A Twilio Integration, call type, phone number, voice settings, and the Flow inputs used for the call. Voice Trigger is available on voice Flows. |
Integration and Voice triggers depend on an Integration configured for the account. The Integration holds the application's authorization; the trigger selects the event and Flow that use it. See Integrate for provider-specific setup and Twilio for voice calls.
Add a trigger in the Designer
- Open Flows, select the Flow, and switch to Design.
- Find the Start node.
- Select Add Trigger below the node.
- Choose Scheduled Trigger, Integration Trigger, or Voice Trigger from Trigger Type.
- Complete the settings for that trigger and select Apply Changes.
Add Trigger is part of the Start node in the current Designer; it is not in the Flow Settings menu or a separate top-right trigger dialog.
Configure a Scheduled Trigger
Choose Scheduled Trigger to run a Flow automatically on a recurring schedule. BotDojo shows the calculated Next run and its time zone after the schedule is valid. Review this preview before saving, especially when the Flow must run at a specific local time.
This weekly example shows the Start node and the Scheduled Trigger panel together, including the next run and time zone.
Scheduled Trigger settings
| Setting | What it does |
|---|---|
| Trigger Name | Identifies the schedule on the Start node and in Flow Trigger management. Use a name that describes the work and cadence, such as Weekly Sales Report. |
| Run As Agent (optional) | Runs the scheduled execution as the selected agent identity. Use this when the Flow needs that agent's configured permissions and resource access. |
| Schedule Type | Selects an Interval, Daily, Weekly, Monthly, or Custom (Cron) schedule. The fields below it change with the selected type. |
| Failure notification recipients (optional) | Sends scheduled-run failure notifications to the listed email addresses. Separate addresses with commas or semicolons. Leave it blank to use the project's configured recipients. |
| Flow Version | Selects default or a published release alias for each scheduled run. Choose a stable release when the schedule should not follow changes to the default version. |
| Input Data Configuration | Supplies the Start-node inputs for every run. The controls come from the input schema of the selected Flow version. |
| Apply Changes | Saves the trigger and attaches its reference to the Start node. The button remains unavailable while required settings are incomplete or invalid. |
Scroll through the panel to choose the Flow version and provide the same input values that the selected version expects at its Start node.
Schedule types
| Schedule type | Configuration |
|---|---|
| Interval | Run every 30 minutes, 1 hour, 3 hours, 6 hours, or 12 hours. |
| Daily | Choose a Schedule Time that applies every day. |
| Weekly | Select one or more days and a Schedule Time. |
| Monthly | Select a day from 1 through 28 and a Schedule Time. |
| Custom (Cron) | Enter a standard five-field cron expression when the built-in schedules do not describe the required cadence. |
For example, 0 12 * * 1-5 runs at noon Monday through Friday in the time zone
shown in the Next run preview.
Configure an Integration Trigger
Use an Integration Trigger when an event from another application should start the Flow—for example, a Slack message, a Zendesk conversation, or a HubSpot record change.
The panel walks through these choices:
- Select the application provider.
- Select the connected Integration that receives or authorizes the event.
- Select the provider's Trigger Type.
- Optionally select Run As Agent.
- Configure the options exposed by that event, then select Apply Changes.
Available providers, event types, and options depend on the Integrations configured for the account. Follow the relevant guide under Integrate before adding the trigger.
Configure a Voice Trigger
Use a Voice Trigger for phone calls handled by a voice Flow. Voice Trigger appears only when the Flow uses the voice schema. Configure the Twilio Integration and call settings first, then map the call inputs required by the Flow. See Twilio for the complete phone-number, voice, greeting, escalation, and call-control setup.
Troubleshooting
- Apply Changes is disabled: Enter a Trigger Name and complete the fields required by the selected schedule. Weekly schedules need at least one day; Custom schedules need a valid cron expression.
- The expected Integration is missing: Confirm the application Integration exists and that you can access it in the current account and project.
- The wrong Flow inputs appear: Check Flow Version. Input Data Configuration is generated from that version's Start-node schema.
- The next run is at the wrong time: Review the time zone shown beside Next run, then adjust the scheduled time for that zone.
- Failure emails go to the wrong recipients: Update the trigger-level list, or leave it blank and review Notification Settings.