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
Triggers require a saved flow version to function. You must save a version of your flow before creating or connecting a trigger. Each trigger is associated with a specific flow version, ensuring consistent execution behavior.
Google Drive File Changed
Starts a flow when a file changes in Google Drive. Choose what to watch:- A folder and its subfolders
- A whole drive: My Drive, or a shared drive the connected account is a member of
- A single file
Each run receives the event, the file ID, name and MIME type, the watched folder ID, the file’s parent folder ID, the drive ID, the modified time, the change time and a link to the file.
The trigger checks for changes every minute. Files already in place when the
trigger is saved are not reported, and folders themselves never start a flow.
A file moved into a watched folder is reported from its next edit. When
watching a folder or My Drive, a file deleted forever or no longer accessible
is reported only if the trigger saw it change since it was saved, because
Google Drive no longer says where it was.
Gmail Email Received
Starts a flow for each new email in the connected Gmail mailbox. It watches the whole mailbox, not only the inbox, and only emails that arrive after the trigger is saved.
Separate several values with commas. An email must pass every filter you set, and it starts the flow at most once, even if it later gains a chosen label. Sender filters match the real address, never the display name. Mark as read applies only to emails that pass every filter.
Each run receives the Gmail message ID, the thread ID, the received date, the sender, subject, body, label names and IDs, attachments, and the email as JSON.
An email that keeps failing is retried on later checks, and skipped with a
notice in the trigger’s events once it has failed 5 times over 30 minutes. If
the Gmail login is revoked the trigger shows a failure and keeps its place, so
it resumes once you reconnect Gmail.
Microsoft Teams triggers
When Teams Message Received listens to private messages, the Chat select limits it to one chat; leave it empty to match every chat. Its runs receive the message text, the Message ID, the Sender email and the Message URL. Sender email and Message URL are empty when Teams does not provide them.
Chat Joined, Team Joined, Channel Discovered and Team Member Joined fire once per chat, team, channel or member, even if it leaves and comes back, and never for ones that existed when the trigger was saved. Each check starts at most 25 runs; the rest start on later checks. Shared channels may not appear. A service principal connection needs a user set for Team Joined.
If the connection is later signed in as a different account, Chat Joined and
Team Joined stop with an error instead of firing that account’s existing chats
and teams as new. Save the trigger again to start watching from then.
Google Sheets Row Added
Starts a flow once for each new row in a sheet. Pick the Spreadsheet and the Sheet, then set Key Column to the header of the column that holds each row’s unique ID. The first row, or the first row of Filter Range if you set one, is the header row. A row starts the flow the first time its ID appears. Editing, sorting, moving or deleting rows never starts a run, and an ID that is deleted and added again does not start another. A row with an empty ID waits until its ID is filled in. A row whose ID another row already has does not start a run and is listed in the trigger’s events with the reason. Each run receives the row, its row number, the spreadsheet ID and the sheet name. The sheet is checked every minute, with at most 100 runs per check; a larger paste goes out over the following checks.Rows present when the trigger is saved never start a run. Renaming the sheet
or the Key Column header keeps the trigger working. A sheet over 10,000 rows
is watched by its newest 10,000 rows.
Jira and Confluence triggers
These triggers check a saved Jira or Confluence connection every minute. Each new item, new version or comment starts one run, never two, and content that existed before the trigger was switched on never does.
A Jira run receives the work item’s key, link, summary, description, status, type, priority, assignee, reporter, labels and dates, plus the comment’s text, author and date for a comment. A Confluence run receives the page’s ID, title, link, space, content, version, author and dates, or for a comment its text, author and date with the page’s ID, title and link.
Creating an item does not count as an update. In Jira, adding a comment also counts as an update, so it starts a Work Item Updated run as well as a Comment Added run. Several edits in the same minute become one run.
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.
Outlook email triggers
Choose the Outlook connection whose mailbox the trigger should monitor. The folder list, saved-folder validation and polling use that same connection. For a shared mailbox, use the Outlook Shared Mailboxes integration, enter the shared mailbox address, and ensure the connected account has access to it. Select Inbox to monitor only the inbox. This choice remains valid when a flow is promoted to an environment with a different mailbox. Clearing Folder monitors all mailbox folders, preserving the behavior of existing triggers with no folder selected. When you change an existing connection or the shared mailbox address, select a folder from the refreshed list. Custom folder IDs belong to their mailbox, so do not copy an opaque PRE folder ID into a different PRO mailbox. Folder choices are unavailable while they refresh; you can continue editing the other fields without losing focus or closing Advanced options. Connection pickers in node and trigger configuration preserve an existing selection when another connection is added. Older triggers without an explicit connection keep their valid saved folder when the picker first initializes. If an explicitly selected connection becomes unavailable, it stays selected and is flagged: choose an available connection explicitly. Create and update refuse a folder that the selected mailbox cannot access. Imports also validate folders after remapping connections: valid bindings remain usable, while a trigger carrying an unavailable folder ID is skipped under the existing import rules. Configure its target folder before creating it in the new environment; custom folders are not guessed by their display names. Outlook Email Received and its Shared Mailbox variant can filter which emails start the flow. Recipient matches an email with a To or CC address containing the text, Subject matches a subject containing the text, and Categories matches an email carrying any of the listed Outlook categories. All three ignore case, and an email must pass every filter you set. Keyword searches the subject and the whole email body, so a word far down a long email still matches; text inside HTML markup does not. If an email fails to process, the trigger retries it on the next polls and does not move past it. Once it has failed at least 3 times over at least 30 minutes, the email is skipped, listed in the trigger’s events with the reason, and the trigger reports a failure so you are notified. Missing folders, expired authentication and denied permissions appear as polling failures. Check the selected connection, mailbox permissions and folder, then retry. Failed polls preserve the email cursor and processed-message IDs; the next successful poll clears the failure. Existing broken triggers need their target connection/mailbox and folder selected again after the fix is deployed.Next Steps
- Learn about Inputs & Outputs
- Explore Flow Design
- Set up flow Deployments
- Check out the Platform