Actions8
Overview
This node integrates with AWS Step Functions, allowing users to manage and interact with state machine executions. Specifically, the "Stop Execution" operation lets you stop a running execution of a state machine by providing its Amazon Resource Name (ARN). This is useful in scenarios where an execution needs to be halted due to errors, changed conditions, or manual intervention.
Practical examples include:
- Stopping a workflow execution that is stuck or running longer than expected.
- Halting an execution when external conditions invalidate the process.
- Programmatically controlling workflow lifecycles from n8n automation.
Properties
| Name | Meaning |
|---|---|
| Execution ARN | The Amazon Resource Name (ARN) of the execution to stop. |
| Error | (Optional) An error code describing the reason for stopping the execution. |
| Cause | (Optional) A more detailed explanation of why the execution was stopped. |
Output
The node outputs a JSON object containing the response from AWS Step Functions after attempting to stop the execution. This typically includes metadata about the stopped execution such as its status and timestamps.
No binary data output is produced by this operation.
Dependencies
- Requires valid AWS credentials with permissions to access and manage AWS Step Functions.
- The node uses the AWS SDK internally; no additional user setup beyond credentials is needed.
- AWS region must be specified in the credentials configuration.
Troubleshooting
Common issues:
- Invalid or missing Execution ARN will cause the operation to fail.
- Insufficient AWS permissions can result in authorization errors.
- Trying to stop an execution that is already completed or does not exist may return errors.
Error messages:
- "Execution does not exist" — Verify the ARN is correct and the execution is active.
- "Access Denied" — Check that the AWS credentials have the necessary Step Functions permissions.
- Timeouts or network errors — Ensure network connectivity to AWS services.
Resolving these usually involves verifying input parameters, checking AWS IAM policies, and ensuring the execution is in a stoppable state.