Weekly Reply.io sequence performance report to Slack

Every Monday at 9am in my timezone, run an agent that produces a weekly performance report across all my active Reply.io sequences and ships it to the team. The trigger should be a cron schedule.

What the agent should do:

1) Pull the data from Reply.io. Call List Sequences and filter to sequences with status Active. For each Active sequence, call Get Sequence Contacts (Extended) and include engagement details so the agent can see per-contact send, open, reply, bounce, opt-out, and meeting-booked signals. Window the analysis to activity in the last 7 days (the week that just ended).

2) Compute per-sequence metrics for the past 7 days: contacts in flight, messages sent, replies, meetings booked, opt-outs, bounces, reply rate, and open rate. Be defensive about pagination on both endpoints (the contacts-extended endpoint caps page size at 100), and tolerate sequences with zero activity (skip them or mark them as quiet).

3) Write a short narrative report (not just a number dump). The report should include: a one-line headline for the week (total sends, total replies, blended reply rate, meetings booked), the top 3 sequences by reply rate, sequences flagged for review (low open rate, high bounce rate, or no replies in the last 14 days), and a one-paragraph recommendation on what to test next week based on what is and isn't working. Keep it concise and skimmable, formatted in Slack mrkdwn.

4) Post the narrative to Slack using Send a Message. The channel should be configurable; default to a channel named #outbound-weekly. Use Slack mrkdwn formatting (single asterisks for bold, backticks for inline code, angle-bracket links). If the message is long, break it into a primary message plus a threaded reply with the per-sequence breakdown so the channel stays clean.

5) Append a historical log row to Google Sheets so we can chart trends independently of Reply.io's UI. Use Append Values against a spreadsheet I'll provide, on a tab called "Sequence Weekly Stats". Append one row per Active sequence with these columns in order: week_start_date (the Monday of the week being reported, ISO format), sequence_name, sent_count, reply_count, reply_rate (as a decimal, e.g. 0.084), meetings_booked. Use valueInputOption USER_ENTERED so the date and numbers parse correctly. If the tab is empty, write a header row first.

Inputs the workflow should expect at setup time:

- Reply.io API key (the agent reads sequences and sequence contacts).

- Slack workspace connection and the destination channel name or ID.

- Google Sheets connection, the target spreadsheet ID, and the tab name (default "Sequence Weekly Stats").

- Timezone for the 9am Monday trigger and for computing week_start_date.

Quality bar: the narrative should feel like a sales ops lead wrote it, not a metrics dashboard. Call out what changed week over week if prior rows already exist in the sheet. If Reply.io returns no Active sequences, post a short "no active sequences this week" note to Slack and skip the Sheets append.