Loading tutorials…
Loading tutorials…
Connecting your CRM, project management, and marketing automation to Slack is a 30-minute task. Connecting them in a way that does not drown your team in notifications is the actual work. Here is the right pattern for each integration.
Who this is forMarketing teams with HubSpot, Salesforce, Asana, or Monday already in production, who want Slack to be the real-time signal layer without becoming a notification firehose.
What you'll need
Step 1
For each tool, list the events that need a response within an hour. That is the only thing that should fire into Slack. Everything else stays in the tool.
For HubSpot: usually new MQL/SQL events, deal stage changes on deals over a threshold, urgent task assignments, mention-in-comment events. NOT every form fill, NOT every email open, NOT every property change.
For Salesforce: new high-value opportunity (over threshold), opportunity stage moved backward, lead assigned to you, account flagged as at-risk. NOT every record edit, NOT every email logged.
For Asana: tasks assigned to you, mentions in comments, due-date misses on your tasks. NOT every status update on every task in projects you watch.
For Monday: items moved to specific status columns (e.g., 'Blocked,' 'Approved'), assignments, due-date warnings. NOT every column edit.
Write the list before configuring. The list is the spec; configuration is mechanical.
Step 2
Slack → workspace name → Tools & settings → Manage apps → App Directory → HubSpot. Install → authenticate → configure notification routing.
Open Slack → workspace name → Tools & settings → Manage apps → App Directory.
Search 'HubSpot' → click the official HubSpot app (with the verified checkmark) → 'Add to Slack.'
Authenticate to HubSpot → grant the OAuth scopes.
In HubSpot: Settings → Integrations → Connected Apps → Slack → Configure. Set: which workflow notifications go to Slack, which channels receive which events, which users get DMs vs. channel posts.
Recommended channel structure: #ops-hubspot (firehose — opt-in only), #sales-leads (high-signal MQLs and SQLs only, broadcast to revenue team).
In HubSpot Workflows, add Slack-notification steps for: new SQL, deal moved to "Closing soon," deal owner unassigned.
Step 3
App Directory → 'Salesforce.' Install → authenticate → configure object-by-object notification rules.
Slack App Directory → search "Salesforce" → install official app.
Authenticate via Salesforce OAuth. Grant scopes for the objects you want to notify on.
In Salesforce Setup → Slack → Configuration: define which objects (Lead, Opportunity, Account) fire notifications, which channels receive each.
Recommended: #ops-salesforce for ops-level events, #revenue-team for high-value opportunity events.
Use Salesforce Flow to route specific events: Opportunity stage moved to "Closed Won" over $50K → post in #wins. Opportunity stage moved backward → DM owner.
Critical: gate notifications by deal size and stage. Most teams notify on every opportunity edit and drown their channels.
Step 4
App Directory → 'Asana' or 'Monday.' Configure project-level notifications and per-user DM rules.
For Asana: Slack App Directory → "Asana" → install → authenticate.
In Asana, link projects to Slack channels: Project Settings → Customize → Apps → Slack → connect channel.
Set notification rules per project: which events fire (created, completed, due, commented, assigned), which channel they fire into.
For Monday: Slack App Directory → "Monday.com" → install → authenticate. In Monday board: integrations → search Slack → configure.
Recommended: dedicated #ops-asana or #ops-monday channels for the firehose. Per-project channels (#project-acme-launch) get only mention and assignment events for project members.
Step 5
Use Slack Workflow Builder or Zapier to route specific events from the firehose channels into team channels with curated formatting.
In Workflow Builder, create: trigger = emoji reaction or scheduled time, step = post to channel.
Example: when HubSpot posts a new SQL in #ops-hubspot, a workflow re-posts a curated version to #sales-leads with "Claim this lead" reaction emoji.
When Asana posts an "overdue task" event in #ops-asana, a Zapier zap pulls the task data, formats it, and posts a digest in #team-marketing every Friday at 4pm.
The pattern: integration firehose → ops channel → curated workflow → team channel. Three layers, increasing signal density.
Step 6
Use Slack AI ($10/user/mo) to generate daily/weekly recaps of high-volume integration channels. Team reads digest instead of firehose.
Slack AI add-on is $10/user/mo on top of Pro and above.
In any high-volume integration channel (e.g., #ops-hubspot, #ops-salesforce), Slack AI can summarize the last 24 hours or last 7 days.
Build a workflow that posts a daily Slack AI recap of #ops-hubspot into #sales-leads at 9am. Now the team gets a curated daily summary instead of scrolling the firehose.
For weekly cadence on lower-volume channels (#ops-asana), a Friday afternoon digest catches blockers and overdue tasks without the daily noise.
Step 7
Pull notification volume per integration channel. Tune thresholds. Kill anything that fires more than 20 events/day without a clear consumer.
In each integration channel, count messages per day over the past 4 weeks (Slack → channel → Analytics, or just scroll the channel).
Target: under 30 messages/day per ops channel. Past 60/day, the team stops reading.
For each integration, ask the team: "Are the events you care about coming through? Are events you do not care about coming through too?"
Tighten thresholds in the source tool (HubSpot Workflows, Salesforce Flow, Asana rules). Send fewer events; ensure each one is high-signal.
Common mistakes
Connecting integrations to team channels directly
What goes wrong: HubSpot fires 200 events/day into #team-marketing. The team mutes the channel. Real team updates get lost. Notification fatigue kills the channel within 30 days. Cost: ~$500-$1,000/mo in lost coordination on a 10-person team.
How to avoid: Always route integrations into #ops-* channels. Use Workflow Builder to curate the high-signal events into team channels.
Default notification settings on every integration
What goes wrong: HubSpot, Salesforce, Asana, Monday all default to firehose. With 4 integrations on default, you get 500-1,000 events/day flowing into Slack. Real signal is invisible. Average team productivity loss: ~$2K-$5K/mo on 25-person team.
How to avoid: Configure every integration after install. Default is the upper bound; tune to the lower bound.
Gating notifications on dollar amount only
What goes wrong: You gate Salesforce notifications by deal size only. Small high-velocity deals never trigger Slack. Sales team finds out about them too late. Lost revenue accumulates silently.
How to avoid: Gate by event type AND value AND owner. Threshold-based filtering only is incomplete. Use multiple gates depending on which segment of the funnel you are watching.
No clear owners for integration-event responses
What goes wrong: HubSpot fires 'new SQL' into #sales-leads. Three people see it. Nobody knows whose job it is. The lead sits for 4 hours before someone reaches out. Lead temperature drops, conversion rate drops.
How to avoid: Each high-signal event has a defined owner or rotation. Use Workflow Builder's 'assign to' step or a Slack List that tracks claim status.
Building Zaps without centralized ownership
What goes wrong: Marketing manager builds a Zap that posts to #sales-leads. Marketing manager leaves the company. The Zap keeps running but errors silently. Lead events stop posting. Sales team thinks the channel is just quiet. ~$10K-$50K of lost pipeline before someone notices.
How to avoid: Centralize Zapier/Make under a marketing-ops shared account. Document every Zap in the team norms Canvas. Audit quarterly.
Not using Slack AI for high-volume channels
What goes wrong: Team members spend 15-20 min/day scrolling #ops-hubspot to catch up. On 25 users at $50/hr, that is ~$6,250/mo in scroll-tax. Slack AI ($10/user/mo) would cost $250/mo and replace the scroll tax entirely.
How to avoid: Enable Slack AI on Pro+ workspaces over 15 users. Build daily and weekly digest workflows for high-volume ops channels.
Recap
Done — what's next
How to set up Slack integrations for a marketing stack
Read the next tutorial
Hand it off
Connecting HubSpot, Salesforce, Asana, and Monday to Slack is mechanical work. Designing the routing architecture so the team gets signal without noise is judgment work — and depends on your stack and team. A growth-ops specialist on EverestX will design the architecture, configure every integration, build the routing workflows, and document the playbook. Typically 12-18 hours at $14-16/hr.
See specialist rates
Use both. Native HubSpot Slack app handles the standard events (new contact, deal stage change). Zapier handles custom logic (e.g., 'only notify if deal is over $50K AND owner is Sarah AND stage moved backward'). They complement each other.
Yes — most integrations (HubSpot, Salesforce, Asana, Monday) support per-user DM rules. Useful for 'task assigned to you' or 'lead assigned to you' events. Configure in each integration's user settings.
Sales Elevate is Salesforce's premium Slack integration (paid add-on, ~$25/user/mo on top of Slack). It includes account-tied channels, deal rooms, and richer Salesforce object embedding. Worth it for sales-heavy orgs. The free Salesforce Slack app covers basic event notifications.
In Asana, link projects to Slack channels selectively. Per-project channel = mentions + assignments only. Firehose events (every task update) go to a dedicated #ops-asana channel. Configure in Asana project settings → Customize → Apps → Slack.
Not directly. Workflow Builder is Slack-internal. To pull data from external tools and post into Slack, use Zapier or Make as the bridge. Workflow Builder can then receive the data and route it inside Slack.
Slack
Slack has 2,600+ integrations in the App Directory. Most teams install 30, get hammered with notifications, and turn most of them off. This is the structured way to pick, install, and govern integrations.
Slack
Slack Workflow Builder is the no-code automation tool that's been in Slack since 2019, and most marketing teams have never opened it. Done well, it replaces a quarter of your meetings and most of your DMs to recurring people.