An action is defined by an action application and implements functionality end-to-end, such as merging a change on Jenkins, getting the last 10 git commits, or updating the StatusPage incident page.
You may also need to set up authorization and some configuration in order for the application to run.
An action can be triggered with authentication in a runbook. When you create an action application, you are creating a action that can be added to any runbook.
Note: Before creating a new action, be aware that Transposit comes with a wide range of actions built-in, as described in Adding Runbook Actions.
input_prompt) and execution operations (named
execute). The type should be "Action". You should use the latest tag for ease of development.
If you make a change to a runbook, you'll need to start a new runbook run (Step 5) to pick up the changes. In Slack, use /transposit to browse and start runbooks.
If you want to better understand the operations that actions use, learn error handling best practices, learn more about authentication, and more action-related concepts, see Action Concepts & Best Practices.