Documentation Index

Fetch the complete documentation index at: https://help.userflow.com/llms.txt

Use this file to discover all available pages before exploring further.

Connecting Slack to Userflow

Prev Next

Connecting Slack to Userflow

The Slack integration allows you to send Userflow product signals, user activity notifications, and event-driven alerts directly to Slack channels where your team already works—without Zapier, webhooks, or custom code.

💡 Switching from Zapier? If you've been sending Userflow activity to Slack through a Zap, see Migrating from a Zapier-based Slack setup to the native Slack integration to move over without double-posting.

What you can do with the Slack integration

Once connected, you can build notification workflows in Userflow's Notification Center that automatically send messages to Slack when specific Userflow events occur. For example:

  • Route flow completions to your product team's channel

  • Send NPS detractor responses to your customer success channel

  • Notify specific channels when users complete key activation milestones

  • Stream custom Userflow events to channels for real-time visibility

This integration works alongside Notification Center's email destinations, giving you the flexibility to send notifications via Slack, email, or both.

Note: This integration currently supports public Slack channels only. Private channels are not supported.

Prerequisites

To connect Slack to Userflow, you need:

  • Userflow account role: Owner or Admin

  • Slack workspace permissions: Ability to authorize and install apps in your Slack workspace

  • Plan availability: Available on Startup plans and above

Connect Slack to Userflow

Step 1: Navigate to Integrations

  1. Sign in to Userflow

  2. Select Settings > Integrations from the sidebar

  3. Click Add integration

  4. Find and select Slack from the list

  5. Click Add Slack

Step 2: Authorize the connection

  1. Click Connect with Slack

  2. In the popup window that opens, select your Slack workspace from the dropdown (if you belong to multiple workspaces)

  3. Review the permissions Userflow is requesting:

    • View information about public channels

    • Post messages to public channels

    • View public channel names

  4. Click Allow to authorize Userflow

The popup will close and you'll return to Userflow. Your Slack integration is now connected.

Step 3: Verify the connection

After connecting, you'll see:

  • Connection status: Connected

  • Workspace name: The name of your connected Slack workspace

  • Options to:

    • Reconnect - Refresh your connection or switch to a different workspace

    • Disconnect - Remove the integration entirely

    • Logs - View a history of all notifications sent to Slack

Important: One Slack workspace per Userflow account

Each Userflow account can connect to one Slack workspace at a time. If you reconnect to a different workspace, all existing notification workflows pointing to channels in the previous workspace will stop working until you reconfigure them.

Viewing integration logs

The Logs section shows all event streaming activity between Userflow and Slack, similar to other Userflow integrations (like HubSpot or Mixpanel).

To view logs:

  1. Go to Settings > Integrations > Slack

  2. Click the Logs tab

  3. Review recent notification deliveries, timestamps, and any errors

Logs help you confirm that notifications are being sent successfully and troubleshoot any delivery issues.

Reconnecting Slack

If your connection expires, stops working, or you need to switch to a different Slack workspace:

  1. Go to Settings > Integrations > Slack

  2. Click Reconnect

  3. Authorize the connection again (follow Step 2 above)

Note: If you reconnect to a different workspace, you'll need to update any existing notification workflows to point to channels in the new workspace.

Disconnecting Slack

To remove the Slack integration:

  1. Go to Settings > Integrations > Slack

  2. Click Disconnect

  3. Confirm the action

Warning: Disconnecting will stop all active notification workflows that send messages to Slack. Email notifications in those same workflows will continue to work.

Troubleshooting

Connection fails during authorization

Symptom: The OAuth popup closes without connecting, or you see an error message.

Common causes:

  • You don't have permission to install apps in your Slack workspace

  • Your browser blocked the popup window

  • Your Slack session expired

Fix:

  1. Make sure you have permission to install apps in your Slack workspace (check with your Slack admin)

  2. Allow popups from Userflow in your browser

  3. Sign out of Slack and sign back in, then try connecting again

Notifications aren't appearing in Slack

Symptom: Workflows show as active in Notification Center, but messages aren't showing up in Slack channels.

Possible causes:

  • The channel you selected no longer exists or was renamed

  • The Slack connection expired

  • The workflow hasn't been triggered yet (check your workflow conditions)

Fix:

  1. Go to Settings > Integrations > Slack and verify the connection status shows "Connected"

  2. Check the Logs tab for any delivery errors

  3. Open the workflow in Notification Center and verify the channel selection is correct

  4. Test the workflow using the "Test" button to send a sample notification

My notifications stopped after working for weeks

The most common cause is a workspace-side change. Check:

  • Was the Userflow Slack app removed from the workspace by a Slack admin? Reconnect under Settings > Notification Center.

  • Was the destination channel deleted, archived, or renamed? Edit the workflow to reselect the channel.

  • Did the Userflow account that authorized the integration lose Owner/Admin access? The integration auth is tied to the connecting account. If they were demoted or removed, reconnect with a current Owner/Admin.

The Slack channel list is empty or slow to load when setting up a notification

When you add a Slack destination to a notification workflow, Userflow fetches the list of channels from your connected workspace. In workspaces with hundreds of channels this can take a few moments, and there isn't always a clear loading indicator—so an empty or still-loading dropdown is usually a sign the list hasn't finished loading rather than a sign that something is broken.

If the channel list is empty, incomplete, or slow to load, try these steps in order:

  1. Give it a few seconds. Large workspaces take longer to load the full channel list—wait briefly and let the dropdown finish populating before assuming it's empty.

  2. Reconnect the integration. Go to Settings > Integrations > Slack, click Reconnect, and approve the permissions again. This refreshes the channel list.

  3. Check the granted permissions. Userflow needs permission to view public channels in order to list them. If those permissions were declined or changed, reconnect as a Slack admin and approve all requested permissions.

  4. For private channels, invite the Userflow app. Private channels only appear once the Userflow app has been added to them. In the channel in Slack, run /invite @Userflow, then return to the workflow and refresh the channel list.

  5. Still empty? Contact support with your workspace name and whether you're a Slack admin, and we'll help track down what's blocking the channel list.

What's next?

Now that Slack is connected, you can build notification workflows in Notification Center.

Learn how to create workflows that send notifications when specific events occur in your product.

Role permissions

Who can connect/disconnect Slack:

  • Owner

  • Admin

Who can create and manage workflows:

  • Owner

  • Admin

  • Editor (can enable/disable and update workflows, but cannot delete them)