Button clicked

Start a workflow when a user clicks a Run automation button on an interface page or record.

Available on NocoDB Cloud (all plans) and licensed on-premise deployments. The button itself is configured in Interfaces.

The When a button is clicked trigger starts a workflow when someone clicks a Run automation button in an interface. On a record sheet, record pane, or field group the clicked record is passed to the workflow, so you can build one-click actions such as "Send contract", "Escalate ticket", or "Generate invoice" that run against exactly the record the user is looking at. On a table page header, record review toolbar, or dashboard group the button runs the workflow without a record, for actions such as "Generate weekly report".

When a button is clicked trigger node

Configuration

This trigger has no settings of its own. It is bound from the interface side:

  1. In the interface builder, open the button settings of the placement you want: Page › Record › User actions › Buttons on a record detail page, record pane, or field group, or User actions › Buttons on a table page, record review list, or dashboard group.
  2. Add a button and choose Run automation as its Action.
  3. Under Automations, pick this workflow. Workflows that cannot be connected are greyed out; hover one to see why.

Alternatively, choose Create new automation from the same list. Give it a name and NocoDB creates a workflow with this trigger already bound; click Continue in Workflows to finish building it, or Finish later.

The trigger panel in the workflow editor shows which table, interface page, and button it is connected to, and warns when the button is not yet configured in the published version of the interface.

A workflow can be bound to one button. The workflow must be enabled, and the interface published, before the button runs it.

How it works

  • A user clicks the Run automation button on a record or page. The button is available to users with the Editor role or above.
  • The workflow starts once per click and shows an Automation started toast.
  • For record buttons, the trigger outputs the clicked record (record.id and record.fields), plus the table, page, button, and the user who clicked. For page-level buttons it outputs the page, button, user, and time only.
  • Each click counts as one workflow run against your plan's run limit.

Use cases

  • Send a document or email for the record on demand
  • Escalate or hand off a ticket to another team
  • Kick off a multi-step process, such as onboarding, from a single button