The primitives
playbook.yaml (excerpt)
On the spine
An action is part of the interaction that ran it. An in-call tool’s result is recorded on the interaction, and the outcome that reaches your webhook is the same outcome the Context Engine keeps.What stays hidden
Delivery mechanics: webhook retries and redelivery, Sheets polling, and SMS carrier routing.Status
Production: HTTP tools, the post-call webhook, two-way Google Sheets sync, and in-call SMS. In build: a helpdesk connector for messaging journeys. Not yet: ready-made CRM, payment and booking connectors.Go deeper
Tools
Declare HTTP tools in a playbook.
Post-call data
The payload your webhook receives.
Agent Harness
Retries and fallbacks around every tool call.
Flows & Journeys
Workflows that decide which action comes next.