Introduction to Playbooks
How to use Draft & Goal Playbooks — ready-made workflow patterns for SEO, Marketing, and Data teams
What are Playbooks?
Playbooks are end-to-end workflow patterns built for real marketing, SEO, and data jobs. Each playbook shows which nodes to combine, how data flows, and what you get when the App runs — so you can reproduce a proven setup instead of starting from a blank canvas.
They sit between product fundamentals and a finished App:
| You need… | Go to… |
|---|---|
| Studio basics, nodes, teams, runs | Guides |
| A specific node’s settings | Nodes |
| A ready-made workflow pattern for your job | Playbooks (this section) |
A playbook is a recipe, not a locked template. Adapt inputs, models, and destinations to your stack (Sheets, Search Console, HubSpot, CMS…).
Who they are for
Playbooks are written for builders and operators who already know the Studio interface and want to ship a recurring process faster:
- SEO and content teams automating audits, keywords, and linking
- Marketing teams enriching leads and running personalized outreach
- Data and ops teams syncing systems and generating recurring reports
If you are new to Draft & Goal, complete the Quickstart first, then come back here.
How to use a playbook
Pick the domain that matches your job
Start from SEO, Marketing, or Data in the sidebar. Open the domain overview for the full map, then choose one concrete playbook.
Reproduce the node chain
Follow the documented flow (inputs → fetch or AI → transforms → write or notify). Prefer the same node families; swap a provider only when your stack requires it.
Wire your connections and inputs
Connect accounts under Builder → Integrations, then map App inputs (URL, property, sheet, CRM list) so each run can be launched without editing the graph.
Run once, then schedule
Validate on a small sample in Run mode. When the output looks right, schedule the App or expose it to runners.
Playbook domains
SEO
Automate content audits, keyword research, and internal linking with scrapers, SEO APIs, and LLM analysis.
Map of SEO playbooks and common node stacks
Analyze site content at scale and export findings
Discover and track keywords with SEO tools and AI
Map links, find orphans, and suggest new opportunities
Marketing
Connect CRM, enrichment, and messaging so repetitive campaign work runs as governed Apps.
Map of marketing playbooks and integrations
Personalize and send email campaigns from workflow data
Enrich leads with site context and AI, then update the CRM
Data
Build no-code pipelines for reporting and keeping systems in sync.
Map of reporting and sync playbooks
Pull sources, analyze with AI, deliver slides or email
Keep Sheets, CRM, and warehouses aligned on a schedule
Choosing the right playbook
Use this quick filter:
- Is the job SEO / content quality? → start under SEO.
- Is the job leads, CRM, or campaigns? → start under Marketing.
- Is the job reports or moving data between tools? → start under Data.
- None of the above? → sketch the flow with Workflow Generator, then reuse patterns from the closest playbook.
Prefer a dedicated Integration node over a generic Code Block when one exists — clearer credentials, less maintenance, easier handoff to teammates.
What a solid playbook App looks like
Most production Apps follow the same shape:
graph LR
In[Inputs / pickers] --> Fetch[Integrations fetch]
Fetch --> AI[AI or Tools]
AI --> Out[Write / notify]
Out --> Guard[Conditional / Stop / HITL]- Inputs collect what changes per run (URL, property, list).
- Integrations read or write external systems.
- AI / Tools analyze, transform, or branch.
- Guards (Conditional, Stop Node, Human in the Loop) keep failures explicit and reviews in the path when needed.
For library orientation, see Introduction to Nodes.