intermediate1 hour3 min read

How to send a weekly Slack report on HubSpot sequence performance

Report HubSpot sequence open rates, reply rates, and meetings booked to Slack weekly. Compare n8n, Make, code, and Claude Code setups.

How to send a weekly Slack report on HubSpot sequence performance

This recipe includes a downloadable n8n template and Claude Code skill.

Workflow

Weekly schedule
Pull sequence metrics
Calculate performance
Post report to Slack

Why report on sequence performance?

Your outbound sequences are a core revenue driver, but most teams only check performance when something feels off — by then, a bad sequence has been running for weeks. A 2-point drop in reply rate across 500 weekly enrollments means 10 fewer conversations per week. Over a month, that's 40 missed opportunities.

The typical check involves logging into HubSpot, clicking into each sequence, and mentally comparing numbers. With 5-10 active sequences, that's 15-20 minutes of clicking and no easy way to compare week-over-week. A weekly Slack report surfaces underperforming sequences before they waste another week of outbound effort.

How it works

Every approach in this guide follows the same pattern:

  1. Trigger on a weekly schedule (usually Monday morning)
  2. Fetch all sequences from HubSpot via the CRM v3 objects API
  3. Pull enrollment data per sequence, filtered to the last 7 days by hs_enrollment_start_date
  4. Calculate metrics — open rate, reply rate, and meeting booked rate per sequence
  5. Post a formatted report to Slack with per-sequence breakdown and aggregate totals
What you'll get
#sales-ops
Sequence Botapp9:41 AM

📧 Weekly Sequence Performance Report

Period: Feb 24 – Mar 2 | 3 active sequences

Outbound — Enterprise — 68% open, 12% reply, 4% booked

Outbound — Mid-Market — 54% open, 8% reply, 2% booked

Re-engagement — Churned — 41% open, 5% reply, 1% booked

⚠️ Mid-Market reply rate down 3pts vs. last week

View sequences in HubSpot →

What you'll need

Prerequisites
  • HubSpot Sales Hub Professional or Enterprise (for sequences API access)
  • HubSpot API access with sequences scopes
  • Slack workspace with bot access
  • At least one active sequence in HubSpot

Which approach should I use?

  • Code + Cron if you want zero ongoing cost and full control over the API calls. Best for teams with a developer who can maintain the script. The Sequences API requires Sales Hub Professional+.
  • n8n if you want a visual workflow with loop-based enrollment fetching. Free self-hosted or $24/mo cloud. The Split In Batches node handles per-sequence iteration cleanly.
  • Make if your team already uses Make. Requires Core plan ($29/mo) for the Code module. Credit cost scales with the number of active sequences (~15 credits/run for 10 sequences).
  • Claude Code if you want conversational flexibility — compare specific sequences, adjust the lookback window, or ask which sequence has the best reply rate. Best for on-demand analysis during sales standups.

Select an approach below to see the full step-by-step guide.

Compare approaches

n8n

high
Cost: $0-24/mo
Latency: polling
Code: low
Reliability: 24/7 cloud

Make

high
Cost: $10-29/mo
Latency: polling
Code: none
Reliability: 24/7 cloud

Code + Cron

medium
Cost: $0
Latency: real-time
Code: high
Reliability: Self-hosted

Claude Code

low
Cost: Usage-based
Latency: on-demand
Code: none
Reliability: On demand

n8n

high

Schedule → HubSpot Sequences API → Code to calculate metrics → Slack

Downloadable templateView guide

Make

high

Scheduler → HubSpot HTTP calls → Aggregators → Slack message

Cost: $10-29/moView guide

Code + Cron

medium

Python script to pull sequence analytics and post summary to Slack

Cost: $0View guide

Claude Code

low

Guided Claude Code skill — ask Claude to analyze sequence performance or compare sequences conversationally

Downloadable skillView guide

Related Recipes

Frequently Asked Questions

Looking to scale your AI operations?

We build and optimize automation systems for mid-market businesses. Let's discuss the right approach for your team.