An action is defined by a Transposit Developer Platform application and implements a functionality end-to-end (E.g. merge a change on Jenkins, get the last 10 git commits, update the StatusPage incident page, etc.) 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 and environment variables in a runbook. When you create an action application, you are creating a action that can be added to any runbook.
input_prompt) and execution operations (named
execute_wrapper). The type should be "Action". You should use the latest tag for ease of development.
...menu, and click Run.
If you make a changes 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 concepts, see our Action concepts & best practices doc.