How to audit your email flows with Claude before BFCM

In under 80 days, BFCM hits.

Before it does, it's worth checking for something that shows up across Klaviyo accounts: a flow is built and tested once, then left sitting in draft.

That's easy to miss. A flow that's off looks the same as a live flow - except for one status toggle. It's a bad problem in any month and a much worse one during the one week your flows are doing the most work and your traffic will be highest.

The brands that go into BFCM clean aren't doing anything complicated. They check two things: which flows are actually live and which ones are still carrying a discount that won't make sense once the sitewide sale goes up.

Assuming you have Claude connected to Klaviyo, this is easy to check. Here’s a prompt I tested on a live store that you can try.

The prompt:

Pull every flow from Klaviyo along with its status, trigger type, and how many emails it's sent in the last 30 days. Flag anything marked live that hasn't actually sent anything in the last 30 days, anything with an unconfigured trigger, and anything that carries its own discount code. Sort the results into three groups: needs a change before BFCM, fine as is, and needs a reminder to change back once BFCM ends.

Run it directly from here → Open in Claude

What comes back:

• Every flow you have, with its live or draft status and how many emails it's actually sent in the last 30 days

• Anything with a trigger that isn't set up correctly - a flow that can't fire even though it looks active

• Anything marked live that hasn't sent anything recently - a flow that stopped working without anyone turning it off

• Which flows carry their own discount code, and whether it needs changing once your BFCM sale goes live

• A short list of what to change back once BFCM ends

Customize for your setup:

If you also run SMS flows, you can change the prompt to check the discount there separately. Texts get read faster and complained about faster, so a text still quoting last month's percentage is a smaller list with a higher cost per mistake.

If you run a subscription or replenishment flow, check its price references specifically. A BFCM price still firing in January is its version of the same problem.

If you'd rather not run this by hand each time, schedule it to run weekly through the first week of December instead - I walked through setting up scheduled tasks with Claude in an earlier issue - read it here.

One Claude Skill for all Shopify operations

This runs on The Agentic Operator, a Claude skill covering catalog, PDP content, segmentation, retention, ads, analytics, merchandising, and more.

The setup is two connections, both from Claude's own directory (Settings → Connectors, then search and add), then the skill file itself.

1. Create a project in Claude for your Shopify operations

2. Add the Shopify connector and authenticate with your store

3. Klaviyo, same way

4. Download the skill file - Get it here

5. Add it under Customize → Skills → Add → Upload a skill

6. Type /the-agentic-operator, then ask anything in plain text

- Ankit