Start Execution
step_functions.start_execution
ActionAmazon Web Servicesconnection required
Calls the AWS step_functions API (SigV4).
Start a state-machine execution.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- AWS Step Functions
- Secret shape
- {"access_key_id", "secret_access_key"}
- Config it needs
- region
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
region AWS region (overrides the connection). | string | No | — | — | — |
state_machine_arn Id of the state machine to act on, from its Step Functions URL or console — not its name. | string | Yes | — | — | — |
input Execution input (JSON). | object | No | — | — | — |
name Optional execution name (must be unique). | string | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
execution_arn | string | — |
start_date When the execution started, epoch seconds. | number | — |
{
"execution_arn": "",
"start_date": 0
}Related AWS Step Functions nodes
See Start Execution run in a workflow.
In a technical demo we add the AWS Step Functions connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.