Detected country: US
logo
Sign InBook a Demo
GuideRecipesDeveloper

Playbook Recipes

  • Data Ops recipes
    • Recipe: Data sync and ETL to a warehouse
    • Recipe: Scheduled reports and readouts
  • Engineering Ops recipes
    • Recipe: AI code review on pull requests with Cursor
    • Recipe: Incident response and on-call paging
    • Recipe: Triage new errors into tracked issues
  • Finance Ops recipes
    • Recipe: Invoice and expense processing
    • Recipe: Reconcile payments and payouts
  • Introduction
  • Marketing Ops recipes
    • Recipe: Campaign performance report
    • Recipe: Competitor monitoring digest
    • Recipe: Content and marketing operations
    • Recipe: Generate a content brief
  • RevOps recipes
    • Recipe: Automate new customer onboarding
    • Recipe: Enrich new leads automatically
    • Recipe: Route a deal review with an evaluation agent
    • Recipe: Score and route a lead with an evaluation agent
    • Recipe: Score, route, and follow up on leads
  • Support Ops recipes
    • Recipe: Auto-answer and deflect common tickets
    • Recipe: Catch a refund request with an evaluation agent
    • Recipe: Check the work before a reply
    • Recipe: CSAT follow-up after ticket resolution
    • Recipe: Escalate SLA breaches and priority tickets
    • Recipe: Triage a support email with an evaluation agent
    • Recipe: Triage and route support tickets
Loading…
logo

Powered by

Introduction

TL;DR: Ready-made scenarios for building playbooks in Ballet, grouped by department. Each recipe names the trigger, connectors, and steps, and includes a copy-paste prompt for Ask Ballet. Pick the closest recipe, paste the prompt into the Console, then review the plan and run.

Who this is for

Builders and Owners who want a proven starting point for a common automation instead of building from scratch.

How do I use a recipe?

  1. Find the department and scenario closest to your workflow.
  2. Open the recipe and read What you'll need (connectors, secrets, trigger).
  3. Copy the Ask Ballet prompt and paste it into the Console on Home.
  4. Review the proposed plan, confirm, and run the playbook.
  5. Adjust steps and connectors to match your exact process.

Departments

  • Support Ops — triage, deflection, escalations, and CSAT follow-up.
  • RevOps — lead enrichment, routing, and onboarding.
  • Marketing Ops — competitor monitoring, content briefs and pipeline, and campaign reporting.
  • Engineering Ops — incidents, error triage, and code review.
  • Data Ops — scheduled reports and data sync/ETL.
  • Finance Ops — reconciliation and invoice/expense processing.

Related articles

  • How do I build a playbook with the Console?
  • Build your first automation with Ask Ballet
  • What triggers can start a playbook?
  • What is a connector?