Slack Connector
5 min read
Connect your Slack workspace to build alert routers, incident response tools, metric digests, and notification workflows that post to the right channels.
Who can do this: Owners, Admins, and Editors can add and manage project connectors. See Roles and Permissions for details.
Connect your Slack workspace and build tools that work where your team already communicates. Alert routers, incident response panels, daily digests, and notification workflows that land in the right channels.
What you can do
Access your workspace data:
- Read public channels and their message history
- Browse users and their profiles
- Access channel membership and metadata
- Search conversations and threads
Build operational tools:
- Alert routers that send events to the right channels
- Incident response panels with severity selection and timestamps
- Morning metrics digests delivered on schedule
- Support ticket notifications with formatted cards
Post structured messages:
- Rich embeds with fields, colors, and actions
- Formatted alerts with context and links
- Daily summaries with metrics and highlights
- Status updates that keep teams informed
How to connect
Slack uses a single connection through the connector. Once connected, Sticklight can read your workspace data and post messages to channels you authorize.
Connect the connector
You can connect from chat or from your project settings.
From chat:
“Connect my Slack workspace”
From project settings: Open Settings, go to Connectors, and select Slack.
When you start the connection:
- Click Connect Account.
- Log in to Slack when the authorization window opens.
- Select the workspace you want to connect.
- Review the permissions Sticklight is requesting.
- Click Allow to authorize Sticklight.
Once connected, Sticklight can access your Slack workspace while you build and your published app can post messages to authorized channels.
Available data
Once connected, your project can access:
| Data | What you get |
|---|---|
| Channels | Public channels, names, topics, member counts |
| Users | Names, profiles, status, timezone |
| Messages | Channel history, threads, reactions, timestamps |
| Workspace | Team info, custom emoji, channel list |
Common use cases
Incident response panel
A single interface for declaring incidents. Select severity, enter a title, and post a timestamped alert to your incidents channel. Track status changes and resolution time in one place.
“Build an incident response tool with severity selection, incident title, and a button that posts a formatted alert to our #incidents channel with timestamp and status.”
Connection needed: Connector
Morning metrics digest
A daily summary that lands in Slack before your team’s morning standup. Choose which metrics to include, preview the card format, and schedule delivery to the right channel.
“Create a daily metrics digest that posts to #team-updates every morning at 9am with our key numbers in a formatted Slack card.”
Connection needed: Connector
Alert router
A routing panel that maps different event types to different Slack channels. Production alerts go to engineering, sales notifications go to revenue, support tickets go to the help desk. Test each route before going live.
“Build an alert routing panel where I can map event types to Slack channels. Include a test button for each route and a log of recent alerts sent.”
Connection needed: Connector
Customer notification workflow
Route important customer events to the right teams. New signups notify sales, subscription changes notify billing, support requests notify the help desk. Each message formatted with relevant context.
“Create a notification router that sends new customer signups to #sales, subscription changes to #billing, and support tickets to #support with customer details in each message.”
Connection needed: Connector
Channel access
Sticklight can post to channels based on the permissions granted during connection:
- Public channels: Accessible by default after connection
- Private channels: Require the Sticklight app to be added to the channel
- Direct messages: Not supported for automated posting
To add Sticklight to a private channel:
- Open the private channel in Slack
- Click the channel name to open settings
- Go to the Integrations tab
- Click Add apps and search for Sticklight
- Add the app to the channel
What visitors see
When you publish your app, it can post messages to Slack on behalf of your connected account. The messages appear as coming from the Sticklight app in your workspace.
Consider who will trigger these messages. An internal incident tool used by your team is different from a public form that posts to Slack. Build with your use case in mind and test thoroughly before sharing.
Limitations
- Workspace-level access. The connector accesses one Slack workspace per connection. For multiple workspaces, create separate projects.
- Private channels require setup. Add the Sticklight app to any private channel you want to post to.
- Rate limits apply. Slack limits how frequently apps can post messages. High-volume workflows may be throttled.
- No direct messages. Automated DMs are not supported to prevent spam.
FAQ
Does connecting Slack cost anything?
No. Connecting is free. You only spend credits when you build something.
Will this post anything to Slack automatically?
No. Nothing posts until you build something that sends messages and explicitly trigger it. You control what gets sent and when.
Can Sticklight read my private channels?
Only if you add the Sticklight app to those channels. By default, only public channels are accessible.
Do I need to know how to code?
No. Describe what you want in plain language and Sticklight builds it. If you do write code, the files are there to open and edit.
Can I control which channels receive messages?
Yes. You define the channel targets when you build your tool. You can hardcode specific channels or build a selector that lets users choose.
What do the Slack messages look like?
Messages appear as coming from the Sticklight app. You can format them with rich embeds, fields, colors, and structured layouts.
Can I build something that reads Slack but doesn’t post?
Yes. You can build read-only dashboards that display channel activity, search results, or conversation summaries without posting anything.
Can I connect multiple Slack workspaces?
Each project connects to one Slack workspace. For multiple workspaces, create separate projects.
Last updated: August 2, 2026