Slack Trigger

The Slack Trigger allows you to initiate workflows based on specific events that occur in your Slack workspace. It enables seamless automation such as responding to messages, monitoring channel activities, or reacting to mentions.

How It Works

The Slack trigger listens for selected events in your workspace — such as messages, mentions, or bot interactions. When the specified event occurs, the trigger activates and executes the connected workflow.

Supported Events

1. New Message Posted to Channel – Trigger when a message is posted in a specific public channel.
2. New Message Posted to Private Channel – Trigger when a message is posted in a private channel where the Boltic bot or your app is present.
3. Mention in Public Channel – Trigger when a user or keyword is mentioned in a public channel.
4. Mention in Private Channel – Trigger when a user or keyword is mentioned in a private channel.
5. Boltic Bot/App Mention – Trigger when the Boltic bot or your custom Slack app is mentioned.

Configuration

Slack Account

• Description: Credentials to connect your Slack workspace (either Boltic bot or your custom Slack app).
• Required: Yes

Event

• Description: The type of Slack event to monitor (e.g., message, mention, or bot mention).
• Required: Yes

Select Channel

• Description: The channel to monitor for events. Only channels the bot/app is part of will appear.
• Required: Conditional — either a specific channel or workspace-wide listening must be enabled.

Listen for Workspace

• Description: Enable to listen for events across all channels the bot/app can access.
• Required: No
• Default: No

Mentioned User

• Description: (For mention triggers) The specific user to watch for mentions.
• Required: No

Keyword

• Description: (For mention triggers) The keyword to monitor in messages.
• Required: No

Setup Notes

• Ensure the Boltic bot or Slack app is added to all channels you want to monitor.
• Events will trigger only in channels where the bot/app is a member.
• You can also connect your own Slack app by providing a bot token and configuring event subscriptions.

Required Scopes for Triggers

The following scopes are specifically required for Slack triggers to function:

Bot Scopes

Scope	Required For
app_mentions:read	Bot/App Mention trigger - detects when the bot is mentioned
channels:history	Message in Public Channel trigger - reads messages in public channels
groups:history	Message in Private Channel trigger - reads messages in private channels
channels:read	Listing and selecting public channels to monitor

User Scopes

Scope	Required For
channels:read	Listing public channels for selection
groups:read	Listing private channels for selection

note

These are the minimum scopes needed for triggers. When you install the Boltic Slack app, additional scopes are requested to support all features including actions/operations. See the Slack Credentials page for the complete list of all scopes.

Best Practices

• Use specific channels and keywords to avoid unnecessary workflow triggers.
• Avoid enabling workspace-wide listening unless needed to reduce noise and rate-limit usage.
• Always ensure your Slack app includes the required scopes listed above.

Example Use Cases

• Customer Support Automation: Create CRM tickets when a new message appears in #support.
• Team Notifications: Send alerts when specific keywords like 'urgent' are mentioned.
• Code Review Reminders: Trigger actions when messages include 'review needed.'
• Meeting Scheduling: Respond automatically when the bot is mentioned with scheduling commands.