Connect HubSpot and Slack
Connect HubSpot to Slack so your team hears about pipeline activity the moment it happens. NoClick can post a Slack message when a HubSpot deal closes, a ticket is created, or a high-value contact appears, and it can pin or react to those messages. It keeps the whole team in the loop without anyone refreshing the CRM.
HubSpot + Slack automations
Pick one to start building it.
About each integration
Templates connecting HubSpot and Slack
Outlook Daily Calendar Brief
Reads today's Outlook calendar at 7am and posts one Slack brief: internal meetings on a line each, every outside meeting carrying the company, open deals and last contact from HubSpot, and the parts of the day that still need moving. In a Microsoft shop the calendar is the org chart, and it is also where a customer meeting hides behind a distribution list and a room booking. This agent reads today's Outlook calendar at 7am, separates the outside meetings from the internal ones, and puts what HubSpot knows about each external attendee under their meeting: the company, the deals in play, the last time anybody spoke to them. It then names the parts of the day that will hurt: the runs with no gap, the meeting nobody has accepted, the call where only optional colleagues were invited. ## What people use it for - **Ready before the commute** - The whole day arrives at 7am on a phone with outside meetings already separated from internal ones. Nothing to open on the train, nothing to cross reference before the first call connects. - **Distribution lists unpacked** - An invite reading all EMEA or hiring panel tells you nothing about who is coming. The brief opens the event and reports the actual people, while never mistaking a room or a mailbox for an attendee. - **The day's pressure named early** - Back to back runs, a customer call nobody has accepted, and two things booked in the same hour all surface while there is still time to move one of them. - **Works from a delegated calendar** - Assistants who run somebody else's diary connect the mailbox they manage, and the brief lands wherever that pair actually talks. Same output, different chair. ## Before you fork **Can it read a shared or delegated mailbox?** Yes, provided the Microsoft account you connect already has access to that calendar, which is how most assistants work anyway. A single workflow covers a single calendar, so a team of five ends up with five copies, each posting into whichever channel or direct message suits that person. **Our channel is not private. What about sensitive meetings?** An event marked private is reduced to its time and its length, with subject, body and attendees left out completely. Everything else is what a colleague would see by opening the invite, plus CRM records anyone with HubSpot access can already read. If a meeting should not appear at all, mark it private in Outlook and the brief respects that. **What does it need from HubSpot, and what does a run cost?** Read access to contacts and deals and nothing beyond it: the CRM is never written to, and no attendee is ever mailed or messaged. A run is one calendar read, a lookup for each external attendee, and one message, so a day holding two customer meetings costs a fraction of a day holding eight.
Zoom Meeting Follow-up Agent
Drafts the after-call email into Gmail and files the HubSpot note minutes after Zoom finishes a transcript, with every next step traced back to a line in the meeting summary. Zoom has been summarising your calls for months and nearly nobody turns those summaries into anything. This agent picks one up the moment the transcript finishes, writes the customer email into your Gmail drafts in your own voice, and files the HubSpot note, then stops so a person can read it before anything leaves the building. Next steps are lifted from the summary line by line, which is how it avoids promising things in your name. ## What people use it for - **Zoom summaries finally used** - The summaries already exist and sit unread in the recordings tab. Each one becomes the email and the note that were going to move the deal along. - **Six calls in one day** - A rep who took six calls has six drafts waiting by 18:00, each addressed and written. Nothing slides to Friday and then gets written from memory. - **Internal calls leave no trace** - The participant check runs before any writing happens, so standups, forecast calls, and interviews produce no draft and no CRM note at all. - **Handover without the replay** - An account changing hands arrives with one note per call already on the record. The new owner reads five minutes instead of scrubbing through 50 minutes of video. ## Before you fork **Does this work if we record to our laptops?** No. It starts from Zoom's transcript completed event, which fires only for cloud recordings with audio transcription switched on in your account settings. Alongside Zoom you connect a HubSpot credential allowed to look up contacts and add notes, a Gmail credential for drafts, and the Slack channel that carries the occasional escalation line. **Could it email a customer by accident?** The one Gmail operation wired into this template creates a draft. There is no send operation on the graph at all. The failure mode is a draft that needs rewriting, sitting unsent in Gmail, and whatever the customer eventually reads went out under a human hand. **What does it cost to run?** You pay per run, and a run happens once per recorded meeting. Internal meetings stop after the participant check and cost almost nothing, so a month with 40 customer calls is 40 real runs and a handful of cheap ones.
Daily Calendar Brief Agent
Sends one Slack brief at 7am with the day laid out: internal meetings compressed to a line each, every customer meeting carrying its company, open deals and last touch from HubSpot, and the attendees no record covers. Most people meet their day at 08:59 and discover on the call that the person opposite is halfway through a renewal. This agent reads the whole calendar at 7am, separates customer meetings from internal ones, and pulls each outside attendee's company, deals, and last contact out of HubSpot into a single Slack brief. It also lists what the CRM does not know, which tends to be the part worth fixing before the first meeting starts. ## What people use it for - **The whole day at 7am** - One message replaces opening six invites and guessing who the attendees are. Before the first call the owner already knows which two meetings need thinking about. - **Never walk into a renewal cold** - A customer meeting arrives with the open deal, its stage and value, and the date somebody last spoke to them sitting directly underneath the time. - **Internal meetings compressed** - Standups, one to ones, and reviews take a single line each. The customer half of the day stays readable rather than drowning in recurring invites. - **A daily list of CRM holes** - Attendees with no record and accounts nobody has touched appear every morning as a short list. Teams tend to repair more of their CRM this way than in any cleanup project. ## Before you fork **Whose calendar does it read?** The calendar belonging to the Google account you connect, which for most people is their own work calendar. If your customer meetings live on a shared team calendar, connect that one instead. A workflow covers a single calendar, so four reps end up with four copies, each posting wherever suits them. **Can I move it off 7am?** Yes, the hour and the days sit on the schedule trigger in the canvas, and it is worth restricting it to weekdays unless you enjoy a Sunday brief listing nothing. Teams spread across regions usually fork it once per region rather than sending everyone one brief at an hour that suits nobody. **Will it touch my calendar or contact anybody?** No. The calendar tools wired in only read events and the HubSpot tools only search and read. It never accepts, declines, or moves a meeting, never mails an attendee, and writes nothing back to the CRM. The cost is one run each morning plus the lookups that day's outside attendees need.
Calendly Meeting Prep Agent
Turns every new Calendly booking into a short Slack brief before the call: what the invitee typed when booking, their history and open deals from HubSpot, and what to say. A Calendly booking already holds the most useful thing anyone knows about a lead, which is what they typed into the booking questions, and it usually goes unread until the call starts. This agent takes each new booking, looks the invitee up in HubSpot, and posts a brief to Slack with their own words at the top, history and open deals underneath, and what to say drawn from your positioning notes. It arrives when the booking does, so there is still time to prepare or hand it to someone else. ## What people use it for - **Inbound demos, prepped** - Someone books from the pricing page and the brief is in Slack before a rep has opened the invite. The call starts from what the invitee wrote rather than from a blank calendar entry. - **Renewals you walk into ready** - The open deal arrives with its stage, amount, and close date attached, alongside any objection the invitee typed while booking. That is the difference between negotiating and finding out live. - **Round-robin calls, still prepped** - When bookings land on whoever is free, the brief is what makes that workable. The rep taking the call gets the same context the account owner would have had. - **Spot the gaps early** - Everything the CRM is missing is listed as missing instead of filled in, and that half is often the more useful one. It tells the rep exactly what to ask on the call. ## Before you fork **What do I need to connect?** The Calendly account your meetings are booked on, a HubSpot credential that can search and read contacts and list deals, and the Slack channel the briefs should land in. You then describe the sections your reps want in a brief and paste in the pitch and objection answers the agent is allowed to use. Nothing is written back to HubSpot, the agent only reads from it. **Does it brief internal bookings too?** No. Bookings from a colleague or from your own email domain are skipped without posting, so one to ones and internal syncs booked through Calendly stay out of the channel. Only external invitees produce a brief, which for most reps is a handful a day. **What if the invitee is not in HubSpot?** The brief still goes out. They are marked as a first-time contact and everything the CRM could not confirm is labelled as not in HubSpot instead of being filled in from their email domain. For inbound bookings that is the normal case, and the unknowns double as the questions worth asking on the call.
Meeting Prep Agent
Turns every new invite with an outside guest into a short Slack brief before the call: who they are, what they bought, what stalled, and what to say. Reps either spend half an hour digging through the CRM before a call or skip it and wing it. This agent watches the calendar, and the moment a meeting with an outside guest is created it pulls that account's history and open deals from HubSpot and posts a short brief to Slack. By the time the call starts, everyone on it has read the same page. ## What people use it for - **End the pre-call scramble** - Gusto's briefing agent took prep from 30 to 45 minutes down to under 5. Here the brief is waiting in Slack before you have even accepted the invite. - **Renewals you do not fumble** - Deal name, stage, amount and close date come straight from HubSpot, so nobody walks into a renewal conversation guessing what is on the table or who last spoke to them. - **Partnership and QBR reviews** - Gusto saw 31% higher win rates and 44% larger deals once every review started from a structured brief. Point this at the invite and it assembles the same shape every time. - **Get new reps up to speed** - A new rep gets the account history alongside your positioning and objection answers in one message, which is the fastest version of learning what the rest of the team already knows. ## Before you fork **What do I need to connect?** The Google Calendar you actually book calls on, a HubSpot credential that can read contacts and deals, and the Slack channel the brief should land in. During setup you write what a good brief looks like for your team and paste in your positioning and objection lines. Nothing is written back to HubSpot. **Does it post for every meeting on my calendar?** No. It only runs when an invite has an attendee outside your company, so internal syncs, one to ones and focus blocks are ignored. That means one short run per new external meeting, which for most reps is a handful a day. **What happens when the contact is not in HubSpot?** It still posts a brief and marks them as new with no record found, and everything it could not verify goes under GAPS rather than being filled in from guesswork. That is deliberate: a brief that quietly invents a job title or a budget is worse than one that says the CRM is empty, because a rep will repeat it on the call.
Email Lead Qualification Agent
Scores every inbound email against your criteria, files the contact and a written note in HubSpot, and pings Slack only for the leads worth a call. Most of what lands in a sales inbox is not a lead, and the few that are get buried under the ones that are not. This agent reads every inbound email, scores it against criteria you write in plain English, and records what it found in HubSpot as a contact plus a note a rep can read before dialing. Slack only hears about the ones that passed, so the channel stays worth opening. ## What people use it for - **Cut a noisy inbox down** - Teams running inbound at scale find that fewer than one in ten emails deserve a rep's time. The agent reads all of them and surfaces only that slice, so nobody scrolls past a real buyer. - **Every lead reaches the CRM** - Contacts are matched or created in HubSpot with a written note attached, on the day the email arrives. No rep has to remember to log anything afterwards. - **Reps open with context** - The note carries what the buyer asked for in their own words, the score, and the reasoning behind it. That is the difference between a cold first call and one that starts halfway in. - **Nights and weekends covered** - An email that arrives at 23:00 on Friday is scored and filed before Monday. The follow-up starts from a full picture instead of an unread inbox. ## Before you fork **What do I need to connect before it runs?** A Gmail account that receives your inbound mail, a HubSpot account with permission to search contacts, create contacts, and write notes, and the Slack channel you want alerts in. Then you write two things in your own words: what a good lead looks like, and what your reps want in a summary. Setup walks you through both, and the test runs let you see a real score before any live email arrives. **Will it email my leads or overwrite my HubSpot data?** No to both. It has no send tool at all, so it can never reply to a prospect on your behalf. In HubSpot it searches by email address first and only creates a contact when there is no match, and it writes notes rather than editing existing properties, deals, or lifecycle stages. **What does it cost to run?** One short agent run per inbound email, so the cost tracks your inbound volume rather than a seat count. If the same inbox also receives newsletters and receipts, point the Gmail trigger at a filtered label so those never start a run. Unqualified mail stops at the HubSpot note, so nothing further is spent on it.
Frequently asked questions
More integration pairings
Connect HubSpot and Slack in minutes
Build it visually with NoClick, or describe what you want and let AI assemble the workflow. No code required.