PostHog connects to Slack natively through its Slack destination in Data pipelines. Create the destination, pick the events or person updates that trigger it, connect the PostHog Slack app, add the app to your channel and template the message. You'll need a PostHog Cloud account for it.
What you can send into a channel
The Slack destination sends custom messages into Slack based on PostHog events or actions. Think of a message in #sales every time someone signs up for a trial, a ping in #product when a user hits a key feature for the first time, or a note when a person's properties change, such as moving to a new company size.
Before you start, check three things: you have a PostHog Cloud account, an active Slack account, and permission to add the PostHog bot to the Slack workspace and the channel you want to post in.
Building the destination
- In PostHog, open the Data pipeline tab in the left sidebar, go to Destinations, click + New destination, search for Slack and click + Create.
- Under Source, choose events or person updates, add filters for which ones should trigger a message, and set the Trigger options to send immediately or on a schedule.
- Click Choose Slack connection, then Connect to Slack, and allow the PostHog Slack app's permissions.
- In Slack, open the channel details, go to the Integrations tab, click Add an app and choose PostHog under In your workspace.
- Back in the destination editor, pick the channel and write the message, using Slack's block kit or plain text, with event and person properties inserted in curly brackets.
- Click Create & Enable and watch for the first messages arriving.
Writing a message people will read
A good alert tells the reader what happened and who it happened to without a click. Templating makes that possible: drop in the event name, the person's email or company and a property or two, and the message makes sense on its own. Block kit lets you add structure, such as a bold title and a short list of details; plain text is fine for a quick ping.
Use filters hard. An alert for every page view will be muted by lunchtime. An alert for the five events that signal a hot lead or a stuck customer will get read. If you're working out which events matter in the first place, this guide to using product analytics covers how to pick them.
Channels that won't show in the list
PostHog docs on the Slack destination point out two snags. First, the PostHog Slack app has to be added to each channel separately; connecting it to the workspace isn't enough. Second, the channel dropdown only lists channels the person who connected Slack can already see. So if a private channel is missing, that person either needs to join it or someone needs to add the app.
If your workspace has thousands of channels, the dropdown may fail to load because of Slack's own API rate limiting. The fix is to paste the Slack channel ID into the field by hand. This guide on adding someone to a Slack channel covers the channel details screen where you'll also find the Integrations tab.
Scheduled reports are a different feature
If what you want is a regular dashboard or insight update in Slack, say a weekly signups chart every Monday, the docs point to PostHog's subscriptions feature rather than this destination. The destination is for event-driven messages; subscriptions are for recurring reports.
Connector routes if you already use one
PostHog's destinations list also includes Webhook, Zapier and Make, and the destination code itself is open source. If your team already runs its automations through Zapier or Make, sending PostHog events there and on to Slack keeps everything in one place, though the native destination has fewer moving parts. For wider reading, my guide to data analytics tools covers where PostHog fits.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
My advice for your first alert
Pick one event that someone on the team would act on the moment it happens, such as a trial sign-up from a business email. Filter tightly, send it immediately, and template the message so it names the person and what they did. Add the app to the channel before you set up the destination, and check the first few messages before you build the next one.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
Does PostHog integrate with Slack?
Yes, through the Slack destination in Data pipelines, which sends custom messages based on events or person updates.
Do I need PostHog Cloud?
Yes. The docs list a PostHog Cloud account as a requirement.
Why can't I see my Slack channel?
The dropdown only shows channels the authorising user can access. Add the PostHog app to the channel, or paste the channel ID.
Can I customise the message?
Yes, with Slack block kit or plain text, using event and person properties.
How do I get regular dashboard updates in Slack?
PostHog points to its subscriptions feature for insight or dashboard updates.
