Inputs
Outputs
Later blocks can read these three outputs as variables. Reference the triggering record as
{{ steps.record_command.record }}. Reference the person who ran it as {{ steps.record_command.actor }}. Reference the run time as {{ steps.record_command.timestamp }}.
Behavior
Each click starts one workflow run for the record the person chose. The run carries that record, the actor, and the timestamp into every later block. A block that acts on a record, such as Update record, already knows which record to use. It does not need to search for it first. You can also run the workflow on a batch. Select several records, then choose Run workflow. This starts one separate run for each record. Select 50 records, and you start 50 runs. Each run is billed on its own. The runs do not share data. So a step that counts or takes turns in order, such as a round robin, is not reliable across a batch. The trigger has no automatic component. Nothing fires on record creation, on an attribute change, or on a schedule. That is what makes the button safe to leave in place while you tune the downstream blocks.Gotchas
- A batch quietly multiplies the credit cost. Each selected record becomes its own run. If one run costs 2 credits, a 50-record batch costs 100 credits. Work out the cost of one run on the credit math page before you select all.
- The button shows the workflow name. Anyone who can view the workflow sees the button. Name the workflow for the person clicking it, not for the builder. Call it Enrich and route this lead, not WF-7 v2 final.
- The run sees the record, not its list data. A list entry is a record’s row on a saved list. It can hold extra fields, such as a deal stage or a priority. This trigger cannot read those fields on its own. To reach them, add a Find list entries step. If the workflow needs that list data often, use the List entry command trigger instead.
Examples
Researching an account on demand
An account executive clicks Run workflow on a company just before a call. An AI agent answers three questions about whether the account is a good fit. The answers are then saved to the record.
The run only starts on a click. So you spend on AI only when a rep asks for it. The agent runs on the accounts a rep is about to call, not on every record in the object. The full build is in AI ICP-fit research and routing.
Pushing a single record into outreach
A sales development rep picks one qualified lead and clicks Run workflow. The workflow adds that lead to an outreach sequence. This lets the rep start a lead by hand instead of waiting for the automatic intake path to pick it up.
The lead
jane@acme.com enters the sequence. A follow-up task then lands on the rep who ran it. It all happens from one click on the record page.