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

Engineering Ops recipes

TL;DR: Engineering Ops recipes automate developer and reliability workflows — incident response and on-call paging, error triage into tracked issues, and AI code review on pull requests. They connect Sentry, Datadog, PagerDuty, GitHub, Linear/Jira, Slack, and Cursor.

Who this is for

Engineering and platform teams who want faster incident response and less manual triage.

Recipes in this department

  • Incident response and on-call — turn alerts into PagerDuty incidents and a Slack war-room.
  • Error triage — summarize new error groups and open tracked issues.
  • Code review with Cursor — review pull requests and post feedback.

Related articles

  • How do I edit steps (Code and HTTP)?
  • How do first-party integrations (Cursor, Freshdesk) work?
  • What triggers can start a playbook?