Please note: all trigger setup can be done in AI chat. Tell AI what you want the workflow to do, and it will handle the rest.
This trigger runs when a user clicks a Button field in a table row. The workflow receives that row’s data.
Build with AI
Open the AI Chat in your table’s right sidebar and describe what you want.
AI handles everything: it chooses the right trigger, maps the relevant fields, and sets up all actions automatically.
Describe the goal once, and the workflow is ready — no manual setup needed.
Example: “When I click the Approve button, update the status and notify the team.”
Configuration
| Setting | Required | Description |
|---|
| Table | Yes | The table that contains the button field |
| Watch Fields | Yes | The button field(s) to monitor for clicks |
| Filter | No | Only trigger if the record matches these conditions when the button is clicked |
Before you can use this trigger, you need a Button field in your table:
- Open the table where you want the button.
- Click + to add a new field.
- In the field type menu, go to Advanced and select Button.
- Give the field a name (e.g., “Approve”, “Send Invoice”, “Export”).
- Save the field. A clickable button will now appear in every row of that column.
How to set it up
- Open your automation and add a new trigger.
- Select When button clicked.
- Choose the Table that has the button field.
- In Watch Fields, select the button field you want to monitor. You can select multiple button fields if needed.
- (Optional) Add a Filter to restrict which rows can trigger the automation. For example,
Status not equal to Completed will prevent the button from firing on already-completed records.
- Save and activate the automation.
- Add your action steps. Click + in any action field to insert data from the clicked row.
What data is available to next steps
When a button is clicked, the trigger provides:
- Record ID — the unique identifier of the row where the button was clicked.
- All field values — every field in the clicked row is available as a variable. This includes text, numbers, dates, linked records, attachments, and more.
This means you can use the row’s data to populate emails, update other records, or send data to external APIs — all based on the specific row the user clicked.
When to use
- One-click approval workflows. Add an “Approve” button to each row. When clicked, update the status to “Approved” and send a notification to the requestor.
- Generate a report or document on demand. A “Generate Report” button triggers an AI action or HTTP request to create a PDF or summary for that specific record.
- Push a record to an external system. A “Sync to CRM” button sends the row’s data to Salesforce, HubSpot, or another platform via an HTTP request.
- Send a personalized email. A “Send Reminder” button composes and sends an email using the row’s contact information and relevant details.
- Trigger a manual review step. A “Flag for Review” button marks the record and notifies a manager, giving humans explicit control over which items get escalated.
Tips
- The button field itself does not store data — it is purely a trigger mechanism. You will not see a value in the cell; just a clickable button.
- If you have multiple button fields in a table, you can create separate automations for each one, or use a single automation that watches multiple buttons and uses conditional logic.
- The filter is evaluated at the moment the button is clicked. If the record does not match the filter, the automation simply does not run — the user will not see an error.
- Button triggers are great for workflows where you want human judgment before an action is taken, rather than fully automatic processing.