<aside> 🛡️

+10% Revenue Per Visitor in 90 days. Or we refund the engagement. Book a teardown

</aside>

The rest of this cookbook is on-demand: you ask, Claude does. This page is the part that runs on a schedule. Saved prompts that pull the data, format it, and drop it where the team already looks (usually Slack), plus alerts that fire when a number crosses a line.

Everything else here is reactive. You open Claude, give an instruction, get an output. The last move is putting that same work on a cadence, so the report is sitting in the channel before anyone logs in, and the alert reaches you the hour a winner starts fatiguing instead of at Friday's review.

These run on a scheduler that wakes Claude with a saved prompt. They are as reliable as the trigger you wire and the QA you keep doing on the output. Treat them as a standing appointment that does most of the prep, not as an employee you stop checking on.


The pattern (every recipe is this one loop)

<aside> 🔁

A trigger (a schedule or a threshold) wakes Claude. Claude pulls the data through a connector, formats it, and posts the result to Slack, email, or Notion. Every handoff below is a variation on that loop. Learn it once and the five recipes are just different inputs and destinations.

</aside>

The five recipes use two trigger types. Scheduled ones fire on the clock, like the Monday Slack report and the daily ops digest. Threshold ones fire when a number crosses a line or an event happens, like the Meta spend alerts, the anomaly monitor, and the CRO test-result handoff.


How the trigger actually fires

The prompts below say things like "every Monday at 8am." Something has to wake Claude. Three real ways to do that, simplest to most powerful.

Mechanism What it is Best for The limit
Claude scheduled task Claude saves a prompt and runs it on a recurring schedule, then delivers the result. You set the cadence once. "Every Monday 8am, build and post the report." The two scheduled recipes here. It runs the saved prompt on time. If a connector's auth expires or an API is down, the run can fail quietly. Check the output landed.
n8n / Make / Zapier (cron or webhook) An automation platform that fires on a cron schedule or a webhook, calls the data source, hands the payload to Claude to read and format, then routes the result. n8n can host and speak MCP. Zapier is the easiest. Make sits between. Anything that chains steps across tools, branches on a condition, or fires off an event like a Meta spend spike. The three threshold recipes here. You are running and maintaining a workflow. Polling the Meta API "hourly" means a cron node every hour, not real-time. n8n self-hosted Community is free.
Native platform alerts Triple Whale, Klaviyo, and Shopify can push their own alerts straight to Slack with no AI in the loop. The basic "tell me when X happens" cases. No reasoning, no custom formatting. You get the platform's canned alert, not Claude's plain-English read.

The decision rule. If the job is "run this exact prompt on a clock," use a Claude scheduled task. If the job is "watch a number and act when it moves," use n8n, Make, or Zapier on a cron or webhook. If the platform already ships the alert you need, turn that on and skip the build.

<aside> ✅

Steal this: do not set-and-forget a scheduled agent on day one. A cron job pointed at a stale OAuth token posts nothing and tells no one. For the first two weeks, glance at every scheduled output to confirm it ran and the numbers look sane. Automation removes the manual work, not your judgment.

</aside>

Slack, Notion, Triple Whale, Shopify (@shopify/dev-mcp), Meta Ads, and Convert.com all ship official connectors. Klaviyo's connector reads campaign performance but its flows are read-only, so a Klaviyo-fed digest can report and not build. Gorgias is reached through its own API or a platform like n8n rather than a first-party Claude connector.


Recipe 1: the Monday morning Slack report

The flagship handoff. A scheduled agent assembles last week and posts it to #marketing before anyone is at their desk. The team walks in to a briefing instead of a blank spreadsheet.

Wire it with: a Claude scheduled task (or an n8n cron) plus the Meta Ads, Shopify, Triple Whale, and Slack connectors.