Weekly Apollo sequence performance report to Slack

Every Monday at 8am, run an agent that produces a written weekly performance report on our Apollo sequences and ships it to the sales team. The trigger is a cron, Monday at 8am in our company time zone.

What the agent should do:

1. Call Apollo Search Sequences to list every active sequence in our account. Capture sequence id, name, owner, and current status.

2. Call Apollo Search Outreach Emails to pull every email sent in the last 7 days, scoped to those sequences. Group the results by sequence id and by step.

3. For each sequence and each step, call Apollo Check Email Stats to fetch opens, clicks, replies, and bounces. Aggregate to sequence level totals and step level totals.

4. Write a narrative weekly review with these sections: top performing sequences (by reply rate, with sends as a sanity check), bottom performing sequences, steps that stalled (low open or low reply on a specific step), reply rate trend week over week (read prior weeks from the Google Sheet tracker), and concrete recommendations on which sequences to pause, edit, or scale and why.

5. Append one row per sequence to a Google Sheets tracker using Append Values. Columns: week_of, sequence_name, owner, sends, opens, clicks, replies, reply_rate, bounce_rate, recommendation. The spreadsheet id and tab name should be configurable.

6. Post the narrative summary to Slack using Send a Message. The channel should be configurable (default to our revenue channel). Format it as a readable Slack post with a short headline, the top and bottom lists, the trend callout, and the recommendations as a bulleted list. Include a link or reference back to the Google Sheet for the full numbers.

Inputs the workflow should expose as configuration: Slack channel id, Google Sheets spreadsheet id, sheet tab name, lookback window in days (default 7), and an optional list of sequence ids to exclude (for example archived test sequences).

Tone of the narrative: tight, useful for a sales leader skimming on Monday morning. No filler, no em dashes, plain numbers with percentages where relevant. The goal is that VPs of Sales get a real review of outbound performance every Monday without ever logging into Apollo.

Additional information

What does this prompt do?

Pulls every active Apollo sequence and last week's outreach emails, then collects opens, clicks, replies, and bounces at the sequence and step level.
Writes a narrative weekly review covering top and bottom performing sequences, stalled steps, reply-rate trends week over week, and which sequences to pause, edit, or scale.
Appends a row per sequence (name, sends, opens, clicks, replies, reply rate, recommendation) to a Google Sheets tracker for historical trending.
Posts the narrative summary to your revenue Slack channel so sales leaders see the review without ever opening Apollo.

What do I need to use this?

An Apollo account with a master API key (required for sequence and outreach email endpoints).
A Slack workspace and the channel ID where the weekly summary should be posted.
A Google Sheets spreadsheet ID and tab name with columns for sequence name, sends, opens, clicks, replies, reply rate, and recommendation.

How can I customize it?

Change the cron from Monday 8am to a different day or cadence (biweekly, daily, end of quarter).
Swap the Slack channel, add a leadership DM, or fan out to multiple channels per sequence owner.
Tighten the recommendation rules (for example, auto-flag any sequence under a 2% reply rate or with a bounce rate over 5%).
Add columns to the Google Sheet (sequence owner, persona, segment) and have the agent fill them in.

Frequently asked questions

Why is this an agent workflow instead of a coded script?

Sales leaders want a narrative review, not just a table of numbers. An agent can interpret reply-rate movement, call out which steps stalled, and write recommendations in plain English. A code workflow can produce the table but not the judgement.

Do I need a master Apollo API key?

Yes. Search Sequences, Search Outreach Emails, and Check Email Stats all require a master key. When you create the key in Apollo, leave the APIs dropdown empty and keep the master key toggle on.

How does it compare week over week?

The Google Sheet acts as the historical store. Each Monday the agent appends a new row per sequence, so the next run can read prior weeks from the same sheet and call out trends.

Can it actually pause underperforming sequences automatically?

Out of the box it only recommends. If you want it to act, ask the workflow author to also wire in Apollo's Deactivate Sequence operation, gated on rules you define.

What time zone does the schedule use?

You set the time zone when configuring the cron trigger. Most teams pick the company HQ time zone so the report lands first thing Monday morning for the sales org.