Skip to main content
Playbooks are stored prompts that run recurringly and deliver results to Slack, email, or other destinations.
Playbooks overview

​
When to Use

  • Daily sales dashboards
  • Weekly performance summaries
  • Monthly financial reports
  • Quarterly business reviews
Example: “Create a playbook that sends daily sales metrics to the sales-team Slack channel every morning at 9am”

How many visitors is my site getting?

​
Saving Your Changes

Edits to a playbook are held in the editor until you save them — nothing is written as you type. The button in the editor header doubles as the indicator: it reads Saved while nothing is pending, becomes Save changes the moment you change something, and shows Saving… while the save is in flight. ⌘S (Ctrl+S on Windows and Linux) saves without reaching for it. The button stays disabled while the playbook is incomplete, and hovering it names the one thing left to fix — an empty prompt, no analysis methodology chosen, or a connector, ontology, or dataset that the chosen methodology still needs. These are the same conditions that block a run, so a playbook you can save is a playbook you can run. Leaving the editor with unsaved edits raises a Discard unsaved changes? prompt, with Stay to return to your work; closing or reloading the tab raises the browser’s own version of that warning. A save that fails leaves your edits in the editor so you can fix the problem and try again, and if someone else changed the playbook while you were editing, nothing is overwritten — the editor tells you and reloads their version.
For a playbook managed as a configuration file, saving files a patch against the Library instead of writing the change directly. The message beside the button reports the patch number and links to it, and the change goes live once an approver merges it.