Workflows are defined by one Transposit Dev Platform application and implement a functionality end-to-end (E.g. merge a change on Jenkins). You may also need to set up authorization and some configuration in order for the application to run.
A workflow application can be triggered with authentication and configurations (called environment variables in the Transposit Dev Platform) by workflows created in Mission Control. When a user creates a workflow, they are configuring the application to be ready to be used. A runbook step can contain various workflows.
## Investigate. Click the Add workflow button at the top. Select the workflow you just created and save.
curl [endpoint_url]). A message will be posted in the channel you previously setup and you can create your incident. In the incident Slack channel, open the runbook you created, click your workflow button, and hopefully you see your input operation being run!
Runbooks and workflows are re-loaded at every step, meaning if you make a change to a workflow or runbook you can return to the Browse Runbooks page and re-select it and it should show the updates (or even page to the next step and come back). Use /transposit to open the last runbook page you were on before you closed it.
If you want to better understand the operations that workflows use, learn error handling best practices, learn more about authentication, and more workflow concepts, see our Workflow concepts & best practices doc.