Loading tutorials…
Loading tutorials…
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.
Who this is forMarketing leads connecting Slack to the rest of their stack (CRM, project management, analytics, ads platforms, design tools). Also useful if you already have integration chaos and need to clean up.
What you'll need
Step 1
Not every tool needs Slack notifications. Pick the tools where 'something happened that someone should know within an hour.'
List your current marketing stack: CRM, project management, analytics, ads platforms, design, email/automation, helpdesk, social schedulers.
For each tool, ask: "Is there an event in this tool where someone needs to know within an hour?" If no, do not integrate it. Slack is for time-sensitive signals; everything else lives in the tool.
Common high-signal integrations for marketing: HubSpot or Salesforce (new high-value lead, deal stage change), Google Drive (shared doc activity), Asana or Monday or ClickUp (task due, mention), Calendly (new booked call), GA4 / Looker Studio (weekly auto-report — not real-time alerts).
Common low-signal integrations to skip: Twitter/X mention firehoses, every Stripe charge, every form submission (use forms with structured intake to a single channel, not a per-form integration).
Step 2
Slack → workspace name → Tools & settings → Manage apps → App Directory. Search for the tool, click Add to Slack, follow the OAuth flow.
Open Slack → click your workspace name (top-left) → Tools & settings → Manage apps.
Click "App Directory" at the top — opens the Slack marketplace in your browser.
Search the tool name. Click the official app (look for the verified checkmark) → "Add to Slack."
Slack will redirect to the tool's OAuth screen. Authorize. You'll be redirected back to Slack with the app installed.
Most integrations let you configure: which channel to post in, which event types trigger posts, which users get DMs. Configure these before you turn the app on.
Step 3
Every integration has settings. Tune which events trigger Slack posts. Default settings are almost always too noisy.
After installing an integration, click its name in Manage Apps → Configuration. Find the notification rules.
For HubSpot: limit to new MQL/SQL events and stage changes on deals over a threshold. Skip every-form-fill notifications.
For Google Drive: limit to comments and mentions, not every edit. Edit notifications create the worst noise-to-signal ratio.
For Asana / Monday / ClickUp: limit to mentions, assignments, and due-date misses. Skip every-status-update.
For CRM tools generally: thresholds matter. New $50K deal is signal. New $200 deal is noise (unless that's your average ACV).
Step 4
Don't fire integration messages into team channels. Create #ops-* channels for integration noise; people opt in.
Create #ops-hubspot for HubSpot events, #ops-asana for Asana, #ops-ga4 for analytics alerts.
Channel members opt in. The team channel (#team-marketing) stays clean. People who need the firehose subscribe; people who don't, don't.
Use Workflow Builder to relay high-signal events from #ops-* to team channels selectively. Example: when HubSpot posts a new SQL in #ops-hubspot, a workflow posts a summary to #team-marketing with a "claim this lead" emoji reaction.
This is the integration-funnel pattern: raw firehose → opt-in ops channel → curated team channel. Three layers, escalating signal-to-noise ratio.
Step 5
Native Slack apps cover the popular tools. For everything else, use Zapier or Make to bridge — and keep the integration architecture consistent.
When the native Slack app for a tool doesn't exist or is limited, use Zapier (zapier.com) or Make (make.com).
Common bridge patterns: Typeform → Slack (new submission posts in #ops-forms), Notion → Slack (page assigned to me → DM), Calendly → Slack (new booking in #ops-bookings).
Zapier has a native Slack app — the Slack action lets you post to a channel or DM with formatted messages.
Keep the bridge integrations under one Zapier or Make account (the marketing-ops account). Don't let individual team members spin up their own Zaps that fire into shared channels.
Step 6
Slack → workspace name → Settings & administration → Manage apps → Permissions. Restrict who can install apps; assign owners.
Open Manage apps → Permissions. Default: any member can install most apps. For workspaces past 25 people, restrict to admins.
For each installed integration, document an owner in the integration's channel description: "Owner: Sarah."
When integrations break (API tokens expire, the tool deprecates a webhook, OAuth scopes change), the owner is on the hook to fix.
Audit installed apps quarterly. Slack → Manage apps → 'View apps.' Remove anything unused.
Step 7
Slack AI ($10/user/mo add-on) can summarize a busy #ops-* channel daily. Saves the channel members from scrolling through 200 messages of integration firehose.
Slack AI is an add-on at $10/user/mo, available on Pro and above. Worth it once you have 3+ high-volume ops channels.
In any channel with Slack AI enabled, click the sparkle icon at the top → "Get a recap" → choose timeframe (last 24 hours, last 7 days).
Slack AI generates a summary of activity. Pin a Workflow Builder workflow that posts a daily Slack AI recap in #team-marketing — captures the integration-firehose signal without subjecting the team to the noise.
Use Slack AI search summaries to answer 'when did [event] last happen?' from integration history. Replaces the manual 'scroll through #ops-hubspot for 10 minutes' tax.
Common mistakes
Installing apps directly into team channels
What goes wrong: Asana fires 80 task-update messages per day into #team-marketing. The team mutes the channel. Real team updates get missed. The cost of channel muting is ~$200/mo per channel in missed-context productivity loss on a 10-person team.
How to avoid: Always install integration apps into a dedicated #ops-* channel. Use Workflow Builder to route the high-signal subset to team channels.
Leaving default notification settings on every integration
What goes wrong: HubSpot defaults post on every contact-property change, every email open, every form fill. After 30 days, #ops-hubspot has 500 messages/day, the actual signal is buried, and nobody trusts the channel.
How to avoid: Configure every integration after install. Default is the upper bound; you want the lower bound. Limit to threshold events only.
No integration owners
What goes wrong: When an integration breaks (OAuth expires, webhook changes), nobody fixes it. The channel goes silent. Three weeks later someone notices and asks 'is HubSpot still firing?' By then, missed leads are lost.
How to avoid: Every integration has a named owner in the channel description. Owner gets the broken-integration alerts. Audit integrations quarterly.
Letting individual users add their own Zaps
What goes wrong: Each team member spins up Zaps under their own Zapier account that post to shared channels. When that person leaves, the Zaps break silently. Knowledge of which-Zap-does-what is scattered across personal accounts.
How to avoid: Centralize Zapier/Make under a marketing-ops account. Individuals can request new bridges via the intake workflow. Pays back in centralized maintainability.
Installing every integration "just in case"
What goes wrong: 30 integrations installed, 18 actively firing, 12 dormant. Each connection is an OAuth scope into your stack — a security surface. Average cost of integration sprawl on Pro: ~$300-500/mo in notification noise productivity loss.
How to avoid: Install integrations on demand only, when a specific person needs a specific signal. Audit quarterly; revoke anything with no active subscribers.
Skipping Slack AI when the channel volume justifies it
What goes wrong: High-volume ops channels with no summary mean team members spend 15-20 min/day scrolling backlogs to catch up. On a 25-person team that is ~125 hours/mo of recoverable time — ~$6,250/mo at $50/hr loaded cost.
How to avoid: Add Slack AI ($10/user/mo) once you have 3+ high-volume ops channels. Set up a daily recap workflow. Saves 5-10x the cost in attention.
Recap
Done — what's next
How to connect Slack to your marketing stack (HubSpot, Salesforce, Asana, Monday)
Read the next tutorial
Hand it off
Picking the right integrations is judgment work — it depends on your specific stack, team size, and pain points. A growth-ops specialist on EverestX will audit your stack, map the integration architecture, configure each integration's scope, and write the runbook. Typically 8-12 hours at $14-16/hr. Cleaner than DIY and saves the audit-cycle that most teams do twice.
See specialist rates
Pro plan has no hard cap, but practically: 10-15 active integrations is healthy on a marketing team. Past 25, you have integration sprawl. Audit quarterly and remove anything not actively used.
Native HubSpot Slack app for standard events (new contact, deal stage change). Zapier for custom logic (e.g., 'only notify if deal is over $50K AND owner is Sarah'). Use both — they complement.
They are the same thing — Slack uses 'app' as the general term in the App Directory. Some apps are first-party Slack apps (Workflow Builder), some are third-party apps in the directory (HubSpot, Asana), and some are custom apps you build yourself (Slack API).
Yes, but the app needs to be explicitly invited to the private channel (type '/invite @AppName' in the channel). Public channels with the integration installed at the workspace level work automatically.
Slack → workspace name → Tools & settings → Manage apps → View apps → click the app → Configuration → Remove App. This revokes the OAuth and stops all incoming events from that integration.
Slack
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.
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.
Slack
The default Slack notification settings are designed to be engaging. That's the opposite of what a focused marketing team needs. This is the configuration that lets people stay reachable without being interrupted.