Automation Templates

Ready-made automation workflows

Clone these templates into n8n, Zapier, or Make and connect them to your ChatBakers account in minutes. All templates use the ChatBakers REST API or MCP Server — the same endpoints available in the app.

n8n n8n Notion Notion ChatBakers ChatBakers

Notion brief to ChatBakers prompt batch

Download JSON

Watch a Notion database for rows marked "Brief approved". For each row, pull the content brief and use the ChatBakers MCP to generate a batch of prompts matched to the topic. New prompts are tracked in ChatBakers from the moment they are created.

Workflow steps

  1. 1 Notion trigger: row status changes to "Brief approved"
  2. 2 Fetch brief body from Notion page
  3. 3 Call ChatBakers MCP: create_prompts_batch with generated prompt variants
  4. 4 Update Notion row status to "In tracking"

API call

POST /api/v1/prompts
Authorization: Bearer cbk_live_...
Idempotency-Key: {notionPageId}

{
  "websiteId": "ws_abc",
  "topicId": "tp_xyz",
  "prompts": [
    { "text": "best email warmup tool 2025", "intent": "commercial" },
    { "text": "email warmup tool comparison", "intent": "informational" }
  ]
}
Zapier Zapier ChatBakers ChatBakers Slack Slack

Weekly citation export to Slack

Download JSON

Every Monday morning, post the previous week's citation summary to a Slack channel. Polls the citations endpoint with a date range, aggregates by domain, and posts a formatted rich message to your team.

Workflow steps

  1. 1 Schedule trigger: Monday 09:00 in org timezone
  2. 2 ChatBakers API: GET /api/v1/citations with last-week date filter
  3. 3 Formatter: aggregate citations by source domain
  4. 4 Slack: post rich message to #client-updates

API call

GET /api/v1/citations
  ?websiteId=ws_abc
  &from=2025-06-16
  &to=2025-06-22
  &page=1
  &limit=100
n8n n8n Linear Linear ChatBakers ChatBakers

Linear ticket to ChatBakers topic generation

Download JSON

When a Linear ticket labelled "chatbakers" is created, trigger asynchronous topic generation using the ticket title as the seed. Poll for job completion and post the generated topic list back as a Linear comment.

Workflow steps

  1. 1 Linear webhook: issue created with label "chatbakers"
  2. 2 ChatBakers API: POST /api/v1/topics/generate with website ID from ticket body
  3. 3 Poll GET /api/v1/jobs/{jobId} until status is completed
  4. 4 Linear: POST comment with generated topics as markdown

API call

POST /api/v1/topics/generate
{ "websiteId": "ws_abc", "seed": "email warmup tools" }

→ { "jobId": "job_xyz" }

GET /api/v1/jobs/job_xyz
→ { "status": "completed", "result": { "topics": [...] } }

Best practices

Use idempotency keys: Send an Idempotency-Key on every POST, PATCH, and DELETE. Re-runs in your automation tool will not duplicate work.
Agency master key: Use one cbk_agency_live_* key with the X-Client-Org-Slug header instead of a separate key per client. Rotation stays centralized.
Handle 429 gracefully: When you see a 429, read Retry-After (seconds) and back off. Most automation platforms have a built-in retry step.
Prefer webhooks over polling: prompt.scrape_completed, site_audit.completed, sentiment.completed, and competitor.discovered events are available under Settings → Webhooks.

Contribute a template

Built a workflow worth sharing? Open a pull request on the templates repo. Include the JSON export and a short description of the trigger, steps, and required credentials.

Open the templates repo →