How to get a weekly HubSpot pipeline report in Slack

The most reliable way to get a weekly summary of new HubSpot leads and deals in Slack is to have someone, or something, read HubSpot at the same time every week and post a short written report to a channel. HubSpot doesn't do this on its own. Its Slack app sends notifications about single records, such as a deal assigned to you or a change to a record you follow, and on plans that include workflows you can add a step that sends a Slack message when a deal is created or reaches a stage. Those alerts arrive one record at a time, so a busy week becomes a stream of messages instead of a summary. HubSpot can also email a dashboard on a daily, weekly, or monthly schedule, or share a dashboard's reports to a public Slack channel on the same kind of schedule, which gives you charts but no explanation of what changed.

Some teams build the summary themselves with a scheduled Zapier or Make automation that searches HubSpot and posts a message. That works for a simple count, but you have to build the filters, the totals, and the formatting yourself, and the message still can't tell you why the number went up or down.

A good weekly pipeline report answers a few questions in a minute of reading:

• How many new leads and new deals came in this week, compared with last week?
• How much pipeline did the new deals add, and which deals moved forward, closed, or were lost?
• Where did the new leads and deals come from?
• Which marketing work produced them, and what should the team do next?

The hard part is consistency. "New lead" has to mean the same thing every week, the week has to be a complete week, and every figure has to trace back to records in HubSpot. If any of that drifts, the team stops trusting the report and goes back to opening HubSpot.

Kite does this work for you. It reads HubSpot, checks the numbers, connects the results to the marketing that shipped, and posts the report to Slack on the schedule you set.

Start by asking Kite for the report in plain language:

"Every Monday at 9, post a summary of last week's new HubSpot leads and deals in #pipeline, and tell us what drove them."

Kite is an AI marketer. It researches your business, builds a growth strategy, and ships the work that brings you new customers. Because it already knows your goals, your channels, and the work it has shipped, it can propose what the report should cover without a long brief. It reads your HubSpot pipelines and lifecycle stages, then suggests which pipeline to report on, how to count a new lead, and which figures to lead with. Confirm the plan or adjust it, and Kite sets up the report.

You'll need to connect your HubSpot account through OAuth so Kite can read your contacts, deals, and campaigns. You can work with Kite in your browser or in Slack, and to receive the report in a Slack channel, add Kite to Slack. Kite joins a public channel on its own, but someone needs to invite it to a private one first.

The report only reads your HubSpot data and posts to your own channel, so it just runs once you've agreed on it. Kite tells you the schedule it set and when the first report will arrive.

Kite settles the definitions once, before the first report, and then holds them steady so every week is comparable. It reads your contact properties and your lifecycle stages to see how your team actually uses HubSpot.

For leads, Kite usually counts contacts whose "Became a Lead date" falls inside the week, rather than every contact created that week. A contact created by an import or a newsletter signup isn't necessarily a lead, and counting by create date can make a quiet week look busy. If your team uses lead status or a custom property to mark real leads, Kite counts those instead. For deals, it counts deals in the pipeline you chose whose create date falls inside the week. It reads that pipeline's stages so it knows which ones mean open, closed won, and closed lost.

Kite also sets the reporting window in your team's timezone. A Monday report covers the previous Monday through Sunday, so it always compares one complete week with the complete week before it.

Kite searches HubSpot for the contacts and deals that fall inside the week and the week before, and it reads only the properties the report needs. For each new lead, that includes the name, company, job title, lifecycle stage, lead status, owner, create date, and the "Last contacted" date. It also reads the Original Source and its drill-down fields, along with the first and most recent conversion, which name the form or page where the person converted.

For each deal, Kite reads the deal name, amount, deal stage, pipeline, close date, create date, and deal owner, plus the contacts and company associated with it. It also reads which deals entered a new stage during the week and which closed, so the report can show movement as well as new arrivals. It reads your list of HubSpot owners so it can name the person behind each record rather than an ID.

Kite looks for the ordinary reasons a pipeline number might be wrong before it reports a change. It confirms that both weeks are complete and measured the same way. It checks whether a jump in leads came from a single CSV import, and whether a drop lines up with a form that stopped sending submissions to HubSpot.

It also notices the record problems that distort a pipeline total, such as these:

• Open deals with no amount
• Open deals whose close date has already passed
• Two deals for the same company and the same opportunity
• New leads with no owner, or with no contact since they arrived

Kite reports these as a short list in the report instead of quietly leaving them out, so you can see exactly what the totals include. When you ask, it can fix what it can confirm, such as assigning an owner, or it can create a HubSpot task for the deal owner to fill in a missing amount.

The most useful part of the report is the connection between new pipeline and the marketing work behind it, and that's where Kite spends the most effort. It groups new leads by Original Source, such as organic search, paid search, email, social, or referrals, and it uses the conversion fields to name the exact form or page. For deals, it follows each deal to its associated contacts to find where the buyer came from.

Then Kite matches those sources to the work that shipped. It knows the pages, emails, and campaigns it delivered for you, and it reads your HubSpot campaigns, including the sessions, new contacts, and influenced contacts HubSpot attributes to each one. It also reads the sends, opens, and clicks on your HubSpot marketing emails. That lets the report say something like "six of this week's eleven new leads converted on the pricing comparison page that went live on Tuesday" instead of just "leads up 40 percent."

Kite keeps what the data shows separate from what it infers. When a cause is likely but not certain, the report presents it as a likely explanation.

Kite writes the report to be read in a minute, with the headline numbers first and the detail underneath. It posts the report to the Slack channel you chose, as a recurring workflow on your schedule and in your timezone. Each week's run starts fresh, reads the new week's data, and posts a new report.

The report ends with a few specific next steps, such as following up on a high-value lead nobody has contacted or putting more effort behind the source that produced this week's best deals. The following week, Kite reports whether those steps moved anything. If you want to dig into something, @mention Kite in the report's thread and ask, for example, which deals came from paid search this quarter. When the analysis needs more room than a Slack message, Kite can publish a hosted dashboard with live charts and link to it from the report.

Each week, your Slack channel gets one report that the whole team can read in a minute, built from records in your HubSpot account.