Actions8
Overview
This node integrates with AWS Step Functions, allowing users to manage and interact with state machine executions within their workflows. Specifically, the Start Execution operation initiates a new execution of a specified state machine by providing its Amazon Resource Name (ARN), an optional unique name for the execution, and input data in JSON format.
Common scenarios where this node is beneficial include:
- Automating complex workflows that require orchestration of multiple AWS services.
- Triggering serverless workflows programmatically from n8n based on external events or data.
- Starting long-running processes that are managed by AWS Step Functions.
For example, you might use this node to start a state machine that processes uploaded files, sends notifications, or manages order fulfillment pipelines.
Properties
| Name | Meaning |
|---|---|
| State Machine ARN | The Amazon Resource Name (ARN) of the AWS Step Functions state machine to start execution on. |
| Name | A unique name for the execution. Must be unique within your AWS account, region, and state machine for 90 days. Optional. |
| Input | JSON string containing the input data for the execution. This data is passed to the state machine when starting the execution. |
Output
The node outputs a JSON object representing the response from AWS Step Functions after starting the execution. This typically includes details such as:
executionArn: The ARN of the newly started execution.startDate: Timestamp indicating when the execution was started.
The output does not include binary data; it solely provides JSON metadata about the execution initiation.
Dependencies
- Requires valid AWS credentials with permissions to start executions on AWS Step Functions.
- The node uses the AWS SDK internally, so no additional manual installation is needed.
- AWS credentials must be configured in n8n with appropriate access keys and region settings.
Troubleshooting
Common issues:
- Invalid or missing State Machine ARN will cause the operation to fail.
- Providing a non-unique execution name may result in errors due to naming conflicts.
- Malformed JSON input can cause the execution start to fail.
Error messages:
- Errors related to authorization usually indicate insufficient IAM permissions or incorrect AWS credentials.
- Validation errors often point to incorrect ARN formats or invalid input JSON.
Resolutions:
- Verify the ARN format and ensure the state machine exists.
- Ensure the execution name is unique or omit it to let AWS generate one automatically.
- Validate JSON input syntax before passing it to the node.
- Confirm AWS credentials have the necessary Step Functions permissions.