Playbooks overview
Use end-to-end implementation guides that combine Infra One Agents, Automations, and external systems into one verified outcome.
Playbooks are outcome-based guides. They cross product boundaries and include every material prerequisite, configuration value, sender contract, test, production check, and failure mode needed to operate the result.
Use a product how-to when you need to learn one surface. Use a playbook when the desired result spans several:
external event → signed Automation trigger → agent task → external result
What every playbook includes
- the final observable outcome;
- the trust and data-flow model;
- product and third-party prerequisites;
- exact UI labels and configuration;
- secret storage and rotation;
- a test that follows the production path;
- success evidence at every boundary;
- duplicate and ambiguous-failure behavior;
- a maintenance checklist.
Available playbooks
GitHub release notes in Slack
Publish GitHub release notes in Slack builds the canonical flow currently used by Allocator One: a successful production release sends bounded GitHub comparison evidence to a signed Infra One Automation, an agent writes a plain-language body, and Ori posts exactly one framed message in #infra-one-releases.
This is the reference playbook for combining Incoming webhook with Agent message.