What are Triggers?
Triggers are the automation catalysts that initiate flow execution based on various events, schedules, and external signals. They transform reactive flows into proactive automation systems by monitoring for specific conditions and automatically starting flows when those conditions are met.Triggers bridge the gap between manual flow execution and fully automated
systems, enabling flows to respond to real-world events, time-based schedules,
and external system changes without human intervention.
Available Trigger Types
Each trigger type handles authentication, event filtering, and data formatting
automatically, enabling seamless integration with external platforms and
services.
Database Row Added
Runs a SELECT on a saved PostgreSQL, MySQL or Microsoft SQL Server connection every 1, 5, 15, 30 or 60 minutes and starts one run per new row, passing the row as JSON.- Query: a single SELECT. Leave out ORDER BY, the trigger sorts by the cursor column. On Microsoft SQL Server the query can’t start with WITH; write the CTE as a subquery.
- Cursor column: a column whose value only grows for new rows, holding whole numbers, decimals, dates, timestamps or text (not floating-point numbers, which compare inexactly). A row is new when its value is above the last one seen, so each row starts a run once and rows that existed when the trigger was switched on never do. A row that arrives later with an equal or lower value (for example a timestamp set when a transaction began but committed late) never starts a run, so a unique, increasing id is the safest choice. On Microsoft SQL Server, use a number or text column: its timestamps are more precise than the trigger can store, so a timestamp cursor is refused.
- Max rows per check: the most runs one check starts (100 by default, up to 1000). The rest start on the next check. Rows that share one cursor value always start together, even past this limit, up to 1000; more than 1000 rows on one value stops the trigger with an error asking for a column with more distinct values.
- Each check is stopped by the database after 30 seconds. A database that can’t be reached is retried at the chosen interval.
- Editing, importing or re-applying the trigger keeps its place unless the query or cursor column changed, or its connection now reaches a different database. If the new connection’s database can’t be confirmed, saving asks whether to continue from the previous position or start watching from now.
Core Capabilities
Schedule-Based Automation - Configure flows to run automatically on specific schedules including hourly, daily, weekly, and monthly intervals. Support for custom timing, timezone handling, and flexible scheduling patterns to match business requirements.Schedule triggers handle timezone conversions, daylight saving transitions,
and business day scheduling automatically, ensuring reliable recurring
automation across different time zones and calendar requirements.
Next Steps
- Learn about Inputs & Outputs
- Explore Flow Design
- Understand Platform Automation
- Check out the Platform