If you’re tired of meetings being a black hole and want your team to actually see the good stuff that comes out of them—without digging through call recordings—this guide is for you. Maybe you’re using Slack as your team HQ, and you’re trying out Avoma for meeting recording, notes, and action items. Good news: when these two tools play nice, you get less “Wait, what happened in that call?” and more real-time momentum.
This guide walks through connecting Avoma and Slack, explains what you’ll actually get (and what you won’t), and calls out the areas where it’s worth tweaking things or just ignoring the noise.
Why Bother Connecting Avoma to Slack?
Here’s the honest pitch: Integrating Avoma with Slack means your team can get meeting insights where they already hang out. That means:
- Automatic meeting summaries in relevant channels.
- Action items and follow-ups delivered to the right people.
- Less context switching between apps.
- Fewer “Did anyone take notes?” moments.
But, it’s not a magic bullet. If your team already ignores Slack notifications, this isn’t going to fix that. And if your Slack is a firehose, you’ll need to set up filters, or it’s just more noise.
Who this helps:
Sales teams tracking deals, customer success teams following up on calls, product teams keeping tabs on feature requests, or anyone who wants to actually use meeting notes.
Step 1: What You Need Before You Start
Before you dive in, make sure you’ve got:
- An Avoma account (admin or with integration permissions).
- Slack workspace admin access (or at least permission to add apps).
- A sense of which meetings and channels matter. Don’t just blast every meeting summary into #general—unless you hate your coworkers.
Pro tip:
If you’re just testing, create a private Slack channel first. You can always set up more granular notifications later.
Step 2: Connecting Avoma to Slack
1. Log in to Avoma:
Head to your Avoma dashboard.
2. Go to Integrations:
Look for “Integrations” in the sidebar or under your account settings.
3. Find the Slack integration:
Click “Connect” or "Add to Slack." This will kick off the Slack auth process.
4. Authorize Avoma in Slack:
You’ll be redirected to Slack. Choose the right workspace and approve the permissions. Avoma asks for access to view channels, post messages, and see basic info. (Yes, this is necessary if you want meeting summaries piped in. No, it can’t read all your DMs.)
5. Pick your channels:
Depending on Avoma’s latest UI, you’ll either pick which channels to post in now, or you can do it later in settings. Start simple: pick one channel for testing.
6. Save and confirm:
You should get a success message. If not, double-check your permissions—Slack workspaces sometimes block new apps by default.
Heads up:
Some orgs lock down app installs. If you hit a wall, ask your Slack admin, and be ready to explain why Avoma needs access.
Step 3: Setting Up What (and Where) Avoma Shares
This is where most people either get value—or get flooded. Avoma can push a lot of stuff into Slack:
- Meeting summaries:
Short recaps, often with key topics, speakers, and action items. - Action items:
Tasks pulled from meetings, sent to relevant folks. - Recordings/Transcripts:
Links to the full call or transcript for reference. - Reminders:
Nudges about upcoming meetings or follow-ups.
How to configure:
- In Avoma, look for Slack settings under Integrations.
- You can usually choose:
- Which meeting types trigger notifications (e.g., external calls, only sales meetings, etc.).
- Which channels get which notifications.
- Whether to @mention participants.
Honest advice:
Start minimal. Too many notifications and people will mute the channel or, worse, start ignoring anything Avoma posts. For most teams, meeting summaries and action items are the only things worth pushing to Slack.
Step 4: Testing the Integration
Don’t assume it works—test it.
- Schedule a dummy meeting or use a real one.
- Make sure Avoma records and processes it.
- Check your chosen Slack channel: Did a summary or action item get posted? Does it make sense or is it messy?
If you get crickets:
- Double-check channel permissions (Avoma needs to be in the channel).
- Make sure the meeting fits the notification rules you set.
- Check Avoma’s status page or help docs—sometimes integrations hiccup.
Step 5: Training Your Team (Without Overdoing It)
You don’t need a big rollout. Just tell your team:
- What to expect in Slack (summaries, action items, etc.).
- Where to look for meeting recaps.
- Who owns following up on action items.
Pro tip:
Pin a message in the relevant Slack channel explaining what Avoma does and how to use the info. Otherwise, people will just see bots posting and tune out.
Step 6: Tweaking Notifications and Settings
Give it a week or two, then check:
- Is your Slack channel useful, or just more noise?
- Are people acting on action items, or ignoring them?
- Is anyone complaining about missed info?
How to adjust:
- In Avoma’s Slack integration settings, dial up or down what gets sent.
- Consider posting only for certain meeting types (sales, customer calls).
- If you’re getting too much, reduce notifications to just summaries or just action items.
Don’t bother:
Don’t bother piping every transcript or recording link into Slack unless your team really reviews them. Most people won’t click.
Step 7: Best Practices for Real Collaboration
Here’s what actually helps:
- Reply to summaries:
Treat Avoma posts like real messages—use Slack threads to ask follow-up questions or clarify action items. - Assign action items:
If you want things to get done, make sure action items have an owner in Slack (not just in Avoma). - Review regularly:
Once a week, skim the Avoma channel. Archive old summaries so the channel stays clean.
What doesn’t help:
- Flooding Slack with every calendar event.
- Posting meeting recaps in channels where nobody cares.
- Relying on bots to replace human follow-up.
What to Watch Out For
- Notification Fatigue:
The biggest risk is that people get too many automated messages and start ignoring them all. Less is more. - Privacy Gotchas:
Remember, Avoma can post recordings and transcripts. Make sure you’re not sharing sensitive calls in public channels. - Integration Drift:
Both Slack and Avoma update their APIs and permissions. Check every few months to make sure nothing’s broken.
Wrapping Up: Keep It Simple—Iterate as You Go
Avoma and Slack can work well together, but only if you keep things focused and lightweight. Start with just the essentials—meeting summaries and action items in one or two channels. Watch how your team uses it, tweak as needed, and don’t be afraid to dial it back if it gets noisy.
Real-time collaboration isn’t about more bots or more messages. It’s about surfacing the right info, at the right time, for the right people—and then getting out of the way. If you keep it simple, your team will actually use what you set up. If you try to automate everything, you’ll just create more digital clutter. So start small, pay attention, and adjust as you go. That’s the real secret.