Fires when a record meets the defined conditions.

NOTE: This trigger fires when a record begins to match the conditions. Existing records that match the conditions specified will not fire the trigger when saved; instead, records must be saved with a change that causes the conditions to be true. Automations fire only when there is a state change in the condition from False to True while the automation is active. For example, if a record already meets the condition (True) before the automation is saved, it will not trigger. The trigger must occur when the record transitions from not meeting the condition (False) to meeting it (True) after the automation is saved. Switching from "When a record is updated" to "When a record matches a condition" can help prevent duplicate actions. This ensures the trigger fires only on state changes (False → True) rather than on every save.

Fires both on record creations or record update.

Example: A trigger can fire when the Status field in a project task table changes from “In Progress” to “Complete.”. Formula fields like WEEKDAY(TODAY()) or Yes/No weekday formulas won't reliably trigger daily emails because they update visually but don't cause a state change event. To ensure reliable triggers, use editable fields such as Single Select, Yes/No, or Text instead of formula fields.

Fires every time a new record is added that matches the conditions.

Example: Trigger an automation when a new task is created in the project task table.

Fires whenever a record in the selected table is updated.
​NOTE: This trigger re-evaluates its conditions every time a record is saved. If a record is saved multiple times in quick succession, the automation may fire multiple times before a status field updates to indicate the action has already occurred.

Example: Trigger an action when a task in the project table is updated.

Fires each time a form response is received.

Example: Automate record creation when a new client submits a feedback form.

Automates actions at a defined interval or specific time.

Example: Trigger a daily task summary email every morning.

Users can see the next 10 scheduled runs- Use the "Find Records" action combined with conditions to filter records before looping through them for actions.

Fires when an HTTP request reaches the automation's unique SmartSuite-generated URL. The trigger accepts GET query parameters or POST JSON bodies, maps the payload fields to outputs for later steps, and shows up to 10 recent requests so you can test before enabling the automation.

Example: a payment service calls the URL when an invoice is paid and the automation updates the record.

Setup and payload mapping are in Automation Trigger: Webhook.

Fires when a member with edit rights clicks a Button field whose action is set to Execute an automation. Each button triggers one automation and each automation of this type is tied to one button.

Example: an Approve button on a request record starts the approval actions.

Setup is in Automation Trigger: Button Click.

Monitors your Gmail or Outlook inbox for new messages that meet specified criteria.

Example: Trigger an action when a client sends an email with the subject “Urgent.”

Choose the Right Trigger: Ensure your automation starts at the correct event for your workflow.

Combine Triggers and Conditions: Pair triggers with specific conditions for precision; see Automation Conditions.

Test Before Activating: Run tests to verify triggers and ensure desired outcomes.

Include an Exit Condition: Specify criteria such as "Status = Tasks incomplete" to ensure the loop stops after processing relevant records. For instance, if only three records meet the condition, the loop will terminate after processing those three records.

Use Date or Toggle Fields: Incorporate a date field or a toggle field (e.g., Yes/No) in your criteria. This ensures that reminders or updates are sent only for tasks that meet specific, relevant conditions.

Use Control Fields to Prevent Duplicates: Add a Yes/No field (e.g., "Automation Fired") to gate automations and prevent duplicate actions.

Avoid Triggers That Evaluate on Every Save: Prefer state-change triggers like "When a record matches a condition" to avoid unintended duplicate actions.

Plan Your Workflow: Clearly define the desired outcome and identify the fields and triggers required.

Use Scheduled Automations for Complex Scenarios: When triggers depend on calculated fields or other dynamic data, scheduled automations can provide a reliable alternative.

Use Conditional Logic with Find Records and Repeating Action Loops: Use Conditional Logic with Find Records and Repeating Action loops to handle complex branching scenarios. Use Editable Fields for Triggers: Avoid using calculated fields as triggers. Instead, use editable fields like Single Select, Yes/No, or Text to ensure reliable automation triggers.

Avoid System Metadata Fields: Do not use system metadata fields, such as "First Created On," in automations or AI prompts. Stick to supported field types like Title, Text, Number, SmartDoc, Text Area, Single Select, Multiple Select, Status, Link, Address, and Date.