Automation and agent triggers
Choose a suitable time or event source and understand its requirements.
Only options offered by your installation and permitted for your account can be configured. A source event does not grant permission to read additional data or perform an action.
| Trigger | Typical use | What to check |
|---|---|---|
| When I run it | On-demand task | Input and action approvals |
| At a specific time | One future job | Date, local time and timezone |
| On a schedule | Recurring work | Schedule preview and timezone |
| At regular intervals | Repeated checks | Interval and expected workload |
| Incoming email | Process matching mail | Connected mailbox and filters |
| Webhook / HTTP request | Receive an event from another service | Displayed endpoint, authentication and sender configuration |
| Website changes | Check a URL for changes | Reachable URL and polling interval |
| RSS / Atom feed | React to feed entries | Valid feed URL and interval |
| Another automation finishes | Follow-up workflow | Source automation and desired completion state |
| Plugin event | Events offered by a connected plugin | Supported event, filters and delivery method |
Knowledge-change or connector-event types can appear on existing configurations. Do not assume an event type mentioned in an integration is available for creating a new trigger in the current editor.
Schedules and timezones
Select the intended timezone rather than relying on your browser's location. Review the next-run preview, especially around daylight-saving changes. A schedule pause is not a stop command for a running job.
Incoming email
Choose or connect the intended mailbox, configure the available subject/source filters and test with a harmless message. A Knowledgebase email connector does not automatically configure an automation mailbox. Maintain or remove the mailbox through the automation's mailbox controls.
Webhooks and HTTP requests
Copy the endpoint and authentication instructions from the saved configuration. Treat the displayed secret as a password. Configure the sending service accordingly and inspect one test delivery before enabling routine traffic. Do not publish a private trigger URL in a public repository or webpage.
Repeated or delayed deliveries can occur at external services. Design tasks to check whether an external change already happened before repeating it.
Plugin events
- Choose Plugin event, then open Choose a plugin.
- Select an installed, permitted plugin that explicitly offers events.
- Choose its event and complete the described filters.
- Set the supported check interval and save.
- Trigger a harmless source change and inspect the resulting run.
Not every MCP plugin can be used as a trigger. This feature currently supports polling delivery for compatible event sources. An event requiring another delivery method is not selectable. Installing a plugin for tool calls alone does not add event support.
If a plugin connection or its available events change, reopen the trigger and confirm the selection. Trigger selection and action-tool selection remain separate.