Using the Start Step Functions Execution action

Use the Start Step Functions Execution action to process Bamboo tasks and notifications, Jira workflow transitions and Jira Service Management automation rule executions with AWS Step Functions to coordinate multiple AWS services into serverless workflows so you can build and update apps quickly:


Using Step Functions, you can design and run workflows that stitch together services such as AWS Lambda and Amazon ECS into feature-rich applications. Workflows are made up of a series of steps, with the output of one step acting as input into the next. Application development is simpler and more intuitive using Step Functions, because it translates your workflow into a state machine diagram that is easy to understand, easy to explain to others, and easy to change. You can monitor each step of execution as it happens, which means you can identify and fix problems quickly. Step Functions automatically triggers and tracks each step, and retries when there are errors, so your application executes in order and as expected.


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:

{ "Version": "2012-10-17", "Statement": [ { "Action": [ "states:ListStateMachines", "states:StartExecution", "states:StartSyncExecution" ], "Effect": "Allow", "Resource": "*", "Sid": "StepFunctionsStartExecutionAndDiscoverStateMachines" }, { "Action": "iam:PassRole", "Effect": "Allow", "Resource": "arn:aws:iam::*:role/service-role/StatesExecutionRole*" "Sid": "StepFunctionsPassRole" } ] }

 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

{     "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

Filter by label

There are no items with the selected labels at this time.

Frequently Asked Questions (FAQ)


Atlassian®, Atlassian Bamboo®, Bitbucket®, Atlassian Crowd®, Confluence®, Jira®, Jira Service Management™, Opsgenie®, and Statuspage™ are registered trademarks of Atlassian.
Amazon Web Services™, AWS™ and the “Powered by Amazon Web Services” logo are trademarks of, Inc. or its affiliates in the United States and/or other countries.

Utoolity® is a registered trademark of Utoolity GmbH.
© 2024 Utoolity GmbH. All rights reserved.