Skip to content

Integration guide

HubSpot and Slack, with AI doing the reading

Post the leads worth a call, a handoff brief when a deal moves stage, and a Friday pipeline summary, instead of a Slack message for every HubSpot change.

In short

Fluxo Flow connects HubSpot and Slack (both live) so a new contact, a new deal or a deal entering a stage can start a workflow that has AI score or summarize the record, optionally waits for a person's approval, and posts the result to a Slack channel or thread.

What you can build

HubSpot + Slack: 3 workflows.

Every step is a real node or connector action in the app.

Deal entered a stage → AI handoff brief → Slack

5 steps

When a deal reaches Closed Won (or any stage you pick), AI writes the handoff for the delivery team.

  1. Step 1: App event triggerHubSpot: Deal entered a stage
  2. Step 2: IntegrationHubSpot: Find records (the deal's contact)
  3. Step 3: AI GenerateHandoff brief: what was sold, who, open questions
  4. Step 4: IntegrationHubSpot: Add a note (the brief, on the deal)
  5. Step 5: Slack PostPost the brief to #delivery

Result: Delivery starts from a brief, and the same brief lives on the deal timeline.

New contact → AI score → Slack for hot leads only

5 steps

Every new contact is scored; only the ones above your threshold reach the sales channel, with a task for the owner.

  1. Step 1: App event triggerHubSpot: New contact
  2. Step 2: AI GenerateScore fit and intent 0-100 with a reason (JSON)
  3. Step 3: RouterScore 70 or more?
  4. Step 4: IntegrationHubSpot: Create a task for the owner
  5. Step 5: Slack PostPost to #sales with the reason

Result: A quiet sales channel where every message is worth reading.

Friday pipeline summary

4 steps

A scheduled run pulls the week's deals and posts a written summary to Slack and email.

  1. Step 1: Scheduled triggerFridays at 3pm
  2. Step 2: HTTP RequestFetch this week's HubSpot deals
  3. Step 3: AI GeneratePipeline, wins, stalled deals, next week
  4. Step 4: Slack PostPost to #sales

Result: The Friday report writes itself; people discuss it instead of building it.

Under the hood

The triggers and actions these use.

  • HubSpot: New contacttrigger, checked on your plan's interval

    Starts a run for each contact created in HubSpot (checked on your plan's schedule interval).

  • HubSpot: Deal entered a stagetrigger, checked on your plan's interval

    Starts a run when a deal moves into the stage you pick (uses HubSpot's “date entered stage” property).

  • HubSpot: Create or update a contactaction

    Creates a contact, or updates the one with the same email.

  • HubSpot: Create a taskaction

    Creates a to-do for a HubSpot user, linked to a contact, company, deal or ticket.

  • HubSpot: Add a noteaction

    Logs a note on a contact, company, deal or ticket timeline.

  • Slack: Post a messageaction

    Posts a message (plain text or Block Kit blocks) to a channel as the Fluxo Flow app.

  • Slack: Reply in a threadaction

    Replies under an existing message, optionally also sending the reply to the channel.

Set it up

Connect HubSpot + Slack in 4 steps.

  1. Connect both apps

    In Settings → Integrations, connect HubSpot (pick the account and approve the permissions) and Slack, then invite the Fluxo Flow app to the channel: /invite @Fluxo Flow.

  2. Connect an AI provider

    In Settings → AI Providers, add a key from any supported provider. Your provider bills the tokens; there's no markup.

  3. Start from a template or a trigger

    Open the AI lead qualification template, or add an App event trigger, choose HubSpot and pick New contact, New deal or Deal entered a stage.

  4. Dry Run, then activate

    Dry Run with a sample record: AI and Slack are simulated. When the trace looks right, activate the trigger.

When HubSpot's own Slack integration is enough

HubSpot has its own Slack integration for notifications from HubSpot workflows. If you just want "tell #sales when a deal closes", use it. Fluxo Flow earns its place when something has to happen between the two apps: AI scoring or summarizing the record, a Human Review before a message goes out, routing to different channels by score or segment, or writing results back to HubSpot (a note, a task, an updated contact) in the same run.

How fast it reacts

HubSpot triggers check HubSpot on your plan's schedule interval, so a new contact shows up in Slack within one interval (faster plans check more often). HubSpot's search index can take a few seconds to include brand-new records. Slack posts go out the moment the run reaches that step.

Avoiding duplicate contacts and noisy channels

Use "Create or update a contact" rather than a plain create: it matches on email, so a returning lead updates the existing contact. Keep the Router threshold high at first and lower it once the channel stays useful. Our guide to HubSpot lead routing covers round-robin and territory rules, and speed to lead covers response times.

FAQ

HubSpot + Slack: questions.

Which HubSpot permissions does it ask for?

Read and write access to contacts, companies, deals and tickets, plus owners for the owner pickers, approved when you connect. What you can store (custom properties, pipelines) still depends on your HubSpot plan.

Can it post to a private Slack channel?

Yes, once you invite the Fluxo Flow app to that channel.

Will it create duplicate contacts?

Not with "Create or update a contact": it matches on email and updates the existing contact.

Can a person approve before the Slack message goes out?

Yes. Add a Human Review step before the Slack step; the run waits in the Review Queue until someone approves, edits or rejects it.

Can I use it on the Free plan?

You can build and Dry Run this on the Free plan. Running it live (schedules, app triggers, webhooks) needs a paid plan.

All integrations

Build your HubSpot + Slack workflow.

Build and Dry Run on the Free plan, no credit card. Run live on a paid plan, on your own AI key at cost.

Free to explore · No credit card · 30-day money-back guarantee on paid plans