Slack Integration

Connect Agents to Slack to post automated messages, send notifications, and share meeting insights with your team.

Overview

The Slack integration enables workflows to:

• Post messages to public and private channels
• Send direct messages to users
• Share formatted content with rich formatting
• Deliver notifications based on meeting events

Prerequisites

Before connecting Slack:

1. Slack workspace where you have permission to install apps
2. Channel access to channels you want to post to
3. Admin approval (if your workspace requires app approval)

Connecting Slack

Step 1: Navigate to Integrations

1. Go to Workspace Settings
2. Select Integrations
3. Find Slack in the list

Step 2: Authorize Connection

1. Click Connect
2. Review the requested permissions
3. Select the workspace to install to
4. Click Allow

Step 3: Invite Bot to Channels

After installation, the Agents bot needs to be invited to channels:

1. Go to the Slack channel
2. Type /invite @Meetingflow (or your bot's name)
3. The bot can now post to that channel

Required Permissions

The Slack integration requests these OAuth scopes:

Available Actions

Slack Post

Post a message to a Slack channel or direct message.

Configuration:

Options:

Channel Configuration

Channel IDs vs Names

You can specify channels two ways:

Channel ID (recommended):

C0123456789

• Most reliable
• Works even if channel is renamed
• Found in channel details → Copy Link

Channel Name:

#general

• More readable
• May break if channel is renamed
• Include the # prefix

Finding Channel IDs

1. Open Slack
2. Right-click on the channel
3. Select Copy Link
4. The ID is the last part of the URL: https://workspace.slack.com/archives/C0123456789

Private Channels

For private channels:

1. Invite the bot first: /invite @Meetingflow
2. Use the channel ID (not name)
3. Bot must be a member to post

Direct Messages

To send a DM, use the user's Slack ID as the channel:

U0123456789

Or the bot can look up users by email if configured.

Message Formatting

Slack mrkdwn

Slack uses its own markdown syntax called "mrkdwn":

Formatting Examples

Basic formatting:

*Meeting Summary* for {{ json.meeting.title }}

_Key Points:_
• {{ json.summary.point1 }}
• {{ json.summary.point2 }}

> "{{ json.keyQuote }}"

<{{ json.meeting.link }}|View full notes>

With sections:

:clipboard: *Post-Meeting Update*

*Meeting:* {{ json.meeting.title }}
*Date:* {{ json.meeting.startTime | date: "%B %d, %Y" }}
*Attendees:* {{ json.meeting.attendees | map: "name" | join: ", " }}

---

*Summary:*
{{ json.summary }}

*Action Items:*
{% for item in json.actionItems %}
• {{ item }}
{% endfor %}

Emoji

Use emoji shortcodes:

:white_check_mark: Task completed
:warning: Attention needed
:rocket: Launch update
:calendar: Meeting scheduled

Example Workflows

Post-Meeting Summary

[Event: MEETING_ENDED]
        │
        ▼
[Load Meeting]
        │
        ▼
[AI: Summarize meeting]
        │
        ▼
[Slack Post]

Message Template:

:memo: *Meeting Summary*

*{{ json.meeting.title }}*
{{ json.meeting.startTime | date: "%B %d at %I:%M %p" }}

{{ json.summary }}

{% if json.actionItems.size > 0 %}
*Action Items:*
{% for item in json.actionItems %}
• {{ item }}
{% endfor %}
{% endif %}

Deal Alert to Sales Channel

[Event: MEETING_ENDED]
        │
        ▼
[Load Meeting]
        │
        ▼
[AI: Analyze deal urgency]
        │
        ▼
[If: is urgent?]
        │
        ├── Yes ──▶ [Slack Post: #urgent-deals]
        │
        └── No ───▶ [Slack Post: #deal-updates]

Scheduled Pipeline Report

[Scheduled: Every Monday 9 AM]
        │
        ▼
[AI: Generate pipeline summary]
        │
        ▼
[Slack Post: #sales-team]

Message Template:

:chart_with_upwards_trend: *Weekly Pipeline Report*

Good morning team! Here's your pipeline update:

*Active Deals:* {{ json.activeDeals }}
*Total Value:* ${{ json.totalValue | round: 0 }}
*Meetings This Week:* {{ json.meetingsScheduled }}

*Top Opportunities:*
{% for deal in json.topDeals %}
• {{ deal.name }} - ${{ deal.amount }} ({{ deal.stage }})
{% endfor %}

Have a great week! :muscle:

Best Practices

1. Use Channel IDs

Channel IDs are more reliable than names:

• ✅ C0123456789
• ⚠️ #sales-team (may break if renamed)

2. Keep Messages Concise

Slack messages work best when they're scannable:

• Use bullet points for lists
• Bold important information
• Keep summaries to 3-5 sentences
• Use emoji sparingly for visual hierarchy

3. Include Context

Always include enough context for the message to be useful:

*{{ json.meeting.title }}*
{{ json.meeting.startTime | date: "%B %d" }} • {{ json.meeting.attendees.size }} attendees

{{ json.summary }}

4. Handle Missing Data

Check for data before including it:

{% if json.actionItems.size > 0 %}
*Action Items:*
{% for item in json.actionItems %}
• {{ item }}
{% endfor %}
{% else %}
_No action items identified_
{% endif %}

5. Test in a Test Channel

Before posting to production channels:

1. Create a #workflow-testing channel
2. Configure workflow to post there
3. Verify formatting and content
4. Update to production channel

Troubleshooting

Common Errors

Bot Not Posting

If messages aren't appearing:

1. Check bot membership - Is bot in the channel?
2. Check channel ID - Is the ID correct?
3. Check permissions - Does bot have chat:write?
4. Check execution logs - Any error messages?

Formatting Issues

If formatting looks wrong:

1. Verify you're using Slack mrkdwn (not regular markdown)
2. Check for unescaped special characters
3. Test in Slack's message composer first
4. Ensure mrkdwn: true in configuration

Rate Limits

Slack has rate limits:

If you hit limits:

• Add Wait nodes between posts
• Batch messages where possible
• Spread workflows across time

Advanced Features

Link Unfurling

Control how links appear:

unfurl_links: false  # Don't expand links into previews
unfurl_media: false  # Don't expand images/videos

Usually keep these false for cleaner messages.

Threading (Future)

Threading support may be added in future versions to reply to existing messages.

Block Kit (Future)

Support for Slack Block Kit rich formatting may be added for more complex layouts.

Security Considerations

Token Storage

• OAuth tokens are encrypted at rest
• Tokens are scoped to minimal required permissions
• Tokens are refreshed as needed

Channel Access

The bot can only post to:

• Public channels (without being invited)
• Private channels where it's been invited
• DMs to users in the workspace

Message Content

Be careful not to include:

• Sensitive customer data
• Internal-only information in public channels
• PII without appropriate consent

Related

• Slack Post Node
• Email Send Node
• HubSpot Integration