Thanks for getting in touch! Unfortunately at the moment there’s no built-in deployment step to run a runbook, though this is certainly something we’d like to add in at some stage in the future. For now there are a couple of options to get around this, however.
The easiest would probably be to reverse this, where you execute the deployment from the runbook. This is done by configuring a Deploy a Release step in your runbook process, though this hits on a limitation where you can’t select the same project in this step. You can get around this by binding the project field to a variable that evaluates to the same project name that the runbook is running in.
The second option would be to make an API call in a deployment step to execute the runbook. I’ve found a sample script using the Octopus.client (an open source .NET library) that looks like this:
var endpoint = new OctopusServerEndpoint("http://localhost:8065");
var repository = new OctopusRepository(endpoint);
var runbookRun = new RunbookRunResource();
runbookRun.RunbookId = "Runbooks-1";
runbookRun.RunbookSnapshotId = "RunbookSnapshots-41";
runbookRun.EnvironmentId = "Environments-1";
You can get the runbook and runbook snapshot IDs by visiting /api/runbooksnapshots and the environment ID by visiting /api/environments.
You can reference more details on the API in the following wiki.
I hope that helps! Let me know how you go or if you have any further questions going forward.