Using the Start Step Functions Execution action


You can use the Start Step Functions Execution action with the following integrations:


The Start Step Functions Execution action requires sufficient IAM permissions - an adequate IAM policy similar to the one provisioned by the Automation with AWS (Core) CloudFormation template might look as follows:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 { "Version": "2012-10-17", "Statement": [ { "Sid": "StepFunctionsServiceActions", "Effect": "Allow", "Action": "states:*", "Resource": "*" }, { "Sid": "StepFunctionsPassRole", "Effect": "Allow", "Action": "iam:PassRole", "Resource": "arn:aws:iam::*:role/service-role/StatesExecutionRole*" } ] }

 Refer to Creating IAM Roles for Use with AWS Step Functions for details on how to create more granular/secure policies.


To configure an Start Step Functions Execution action:

Complete the following settings:



Specify the action parameters according to the following skeleton in JSON format – refer to stepfunctions . start-execution for details:

You typically only specify the stateMachineArn and input parameters, because name must be unique for your AWS account and region and properly defaults to a GUID when absent.

You can inject contextual variables into the remote action payload, refer to Entity Variables for details.

Start Step Functions Execution skeleton

1 2 3 4 5 {     "stateMachineArn": "",     "name": "",     "input": "" }

Entity Variables

You can inject contextual workflow variables with workflow entities into the remote action payload template – currently available entities are:


How-to Articles

Frequently Asked Questions (FAQ)