Plan Availability | All plan types |
Permissions | Solution Managers – Can create, modify, and manage automations in Solutions where they have Solution Manager access. |
Related Reading |
Overview
The "When a Button is Clicked" trigger allows automations to run in response to user interaction with a button. Whether part of a workflow or an interface action, this trigger enables manual control over automation execution—perfect for approvals, escalations, or custom updates.
How to Connect a Button to an Automation
Field-Based Button Setup
Connecting a button to an automation is handled entirely in the Button field’s settings, making setup straightforward:
Open the field settings for your Button field in a Solution table.
Under Actions, enable “Execute an automation.”
A dropdown will appear showing available automations that use the "When a button is clicked" trigger.
Select the appropriate automation from the list.
Once selected, the button becomes locked to that automation and displays as a read-only label in the automation’s trigger configuration. This design ensures clarity about which button is linked and prevents misconfiguration.
✅ Each button triggers only one automation.
🔁 One automation can be triggered by multiple buttons.
Note: If required fields like Button Name or Label aren’t filled, SmartSuite will prompt you with validation before continuing.
Trigger Configuration in Automation Builder
When building from the Automation UI:
The trigger type will be SmartSuite: When a Button is Clicked
You must define:
The target table (where the button exists)
The button name
Optional conditions, like "Status = Complete"
Note: You can’t change the trigger type once the automation is saved. This avoids errors from unlinking the button unexpectedly.
Once a Button is Clicked
The button enters a processing state so others can’t click it again prematurely.
A toast message informs the user of the result:
✅ “Automation ran successfully”
❌ “Automation failed”
⚠️ “Conditions did not match” (if trigger conditions weren’t met)
Activity History logs the action with timestamp and result. It will say something like:
“Isaac Gutierrez clicked ‘Submit Review’ button. Automation ran successfully.”
Note: A red dot will appear on the button if the automation failed, with a tooltip showing details on hover (e.g., error type, timestamp).
Important Behavior from the Button Action
What you need to know about button-automation interactions:
Action | Effect |
Change the action type | Prompts a warning: “Changing the action type will overwrite/delete the current automation.” |
Delete the button | Deletes the linked automation |
Delete the automation | Deletes the linked button |
Inactivate the automation | Makes the button non-clickable |
Duplicate button or solution | Duplicates the automation and sets up the trigger without actions |
Practical Use Cases
Departmental Collaboration
Scenario: The Marketing team needs a fast way to request content approvals.
Solution: Add a “Request Review” button to the table that triggers an automation to alert editors.
Customer Support Escalation
Scenario: Support agents escalate issues requiring manager review.
Solution: A button labeled "Escalate" triggers an automation that changes the ticket’s status and notifies the support lead.
Task Sign-Off Workflow
Scenario: A project manager approves tasks once verified.
Solution: A “Mark Complete” button in the task table triggers an automation that updates the status and logs who approved it.