Skip to main content

Automation Triggers

The automation triggers, what starts each one and how to set it up, from matches a condition to webhooks and email.

Written by Emma Montgomery

A trigger is the event that starts an automation. You pick it under When this happens, then add conditions and actions.

SmartSuite has seven triggers of its own and two email triggers for Gmail and Outlook. A trigger watches one table in the automation's own solution.

Example: a Risk Register table in an Enterprise Risk Management solution. Each risk owner must re-evaluate their risks on time. One automation fires when a risk's evaluation falls due. Another fires when its Risk Response changes to Accept. A third runs once a week and emails a summary.

Plan Availability

All plan types.

Permissions

Administrators, in any solution, and Solution Managers, in the solutions they manage, set up triggers.

Platform

Web

Related Reading


How do I pick a trigger?

  1. Open Automations from the Solution Menu.

  2. Select Add Automation at the bottom of the list. In a solution with no automations, select Create my first Automation.

  3. The trigger list opens on its own. Pick a trigger.

  4. Set it up in Trigger Settings on the right.

The list has two groups. SmartSuite Triggers holds the seven native triggers. Integrations holds Microsoft Outlook and Google Gmail. Point to one to see its trigger.

To switch later, select Change Trigger in Trigger Settings. SmartSuite asks you to confirm, because settings that depend on the old trigger may stop working. Select Yes, Change Trigger or No, Cancel.

The trigger list of a new automation, with SmartSuite Triggers and Integrations.

The trigger list of a new automation, with SmartSuite Triggers and Integrations.


When a record matches a condition

This trigger fires when a record starts to match your conditions. It checks new records and every update.

  1. Select the Table.

  2. Add the Conditions, such as Status is Equal to Complete.

The trigger fires only on a change from not matching to matching while the automation is on. A record that already matched when you turned it on does not fire it.

For the Risk Register, the condition is Risk Evaluation Due Date Is Today + 7 days. Each risk fires once, on the day its evaluation is a week away.

Note: A formula that changes on its own, such as WEEKDAY(TODAY()), does not count as a change. Use an editable field, such as a Single Select or Yes / No, or use At a scheduled time.


When a record is created

This trigger fires each time a new record is added to the table.

  1. Select the Table.

  2. Optional: add Conditions. Only new records that meet them fire the trigger.


When a record is updated

This trigger fires each time a record in the table is saved and meets your conditions.

  1. Select the Table.

  2. Optional: add Conditions.

A new condition row starts as Changes, from Any to Any. Set both values to catch one move. For example: Risk Response Changes from Equal to Mitigate to Equal to Accept. Only this trigger offers Changes.

The trigger checks its conditions on every save. A record saved several times in a row can fire it more than once. See Comparing “Record Matches” and “Record Updated” Triggers.


When a form is submitted

This trigger fires each time someone submits a form.

  1. Select the Table.

  2. Select the Form. The list shows that table's forms.

  3. Optional: add Conditions.


At a scheduled time

This trigger runs on a schedule. It has no conditions and passes no record to the actions.

  1. Select the Table.

  2. Under Repeat Every, enter a number and pick Hours, Days, Weeks, Months or One Time.

  3. Set when it runs. Weeks takes days and a time. Months takes days of the month, or Last day of month, and a time. Days takes a time. Hours and One Time take a time under At.

  4. Set Starting From, the first date.

The settings show the next run. Select Show next 10 runs to see ten. Times use the Automation Time Zone in the builder header.

To work on records, add a Find records action with conditions after this trigger. Then loop through the records it finds. See Automation Action: Looping.

At a scheduled time Trigger Settings set to repeat every 1 week on one day, with Starting From and the next run shown.

At a scheduled time Trigger Settings set to repeat every 1 week on one day, with Starting From and the next run shown.


When a button is clicked

This trigger fires when a member who can edit the record clicks a Button field set to run an automation. One button runs one automation.

  • Table: the table that holds the button.

  • Button Field: the button paired with this automation.

  • Conditions, optional.


When webhook is received

This trigger fires when another system sends a request to the automation's own URL.

  • Request URL, with a Copy button.

  • HTTP Method: GET or POST. A request with the other method is rejected.

  • Request Content, for POST: JSON Object, JSON Array, Text, Boolean or Number.

While the automation is off, the trigger shows up to 10 recent requests. Use them to set up the data structure. Redetermine data structure captures it again. See Automation Trigger: Webhook.


Microsoft Outlook and Google Gmail: When an email is received

Each of these triggers watches one folder of a mailbox. It fires when a new email that meets your conditions arrives there.

  1. In Google Gmail Account or Microsoft Outlook Account, pick a connected account. Or select the option to add a new credential, sign in and grant every permission.

  2. Pick the Folder to watch, such as INBOX. It is required. The trigger does not move emails.

  3. Optional: add conditions, such as From Email, Subject or Attachment Count. Choose AND or OR.

To catch other emails, add a rule in Gmail or Outlook that moves them into the folder. See Automation Trigger: Google Gmail and Automation Trigger: Outlook.


How do I avoid runs I did not want?

  • Prefer a state change. When a record matches a condition fires once per change. When a record is updated can fire on every save.

  • Use a control field. A Yes / No field such as Reminder Sent, set by the automation, stops a second run.

  • Filter before a loop. The Find records conditions decide which records a loop works on. The loop runs once per record, then stops.

  • Test with a record. Triggers have no test button. Turn the automation on, change a test record and read the run in History.


Frequently asked questions

Will records that already match fire the automation?

No. A record fires it only when it changes into the matching state after the automation is on. Save a change that makes the conditions true to run it.

Can the trigger watch a table in another solution?

No. The Table list shows only the tables of the automation's solution. Actions such as Create a record and Find records can use any solution in the workspace.

Can a comment start an automation?

No. Comments on records do not fire the When a record is updated trigger.

Can I see when a scheduled automation runs next?

Yes. Its settings show the next run, and Show next 10 runs lists ten. A One Time schedule shows no preview.

Can a trigger fire every few minutes?

No. The shortest interval of At a scheduled time is Hours.

Need more help? Ask the SmartSuite Community, where builders, administrators and the SmartSuite team answer questions about building on SmartSuite. For your account, billing or data, select the chat button in the lower-right corner of SmartSuite to reach support.

Last verified 1 Nov 2026.

Did this answer your question?