---
title: "Migrating from a Zapier-based Slack setup to the native Slack integration"
slug: "migrating-from-zapier-to-native-slack-integration"
updated: 2026-07-27T15:16:51Z
published: 2026-07-27T15:16:51Z
canonical: "help.userflow.com/migrating-from-zapier-to-native-slack-integration"
---

> ## 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.

# Migrating from a Zapier-based Slack setup to the native Slack integration

If you've been sending Userflow activity to Slack through Zapier — for example, a Zap that posts to a channel when a user completes a flow or answers an NPS question — you can now switch to Userflow's native Slack integration. It does the same job through Notification Center, with no Zapier, webhooks, or custom code. This guide walks you through moving over without double-posting to your channels.

## Why switch

|  | Zapier-based setup | Native Slack integration |
| --- | --- | --- |
| **Setup** | Build and maintain a Zap per event | Connect once, then build no-code workflows in Notification Center |
| **Filtering** | Zap filter steps | Built-in event, user, and company attribute conditions |
| **Message content** | Manual field mapping | Message template with `{{variables}}` for user and company attributes |
| **Destinations** | One Slack action per Zap | One workflow can post to multiple Slack channels, email, or both |
| **Maintenance** | Counts against your Zapier task quota | Managed in Userflow under Settings → Integrations and Notification Center |
| **Testing** | Run the Zap | Built-in Test button with sample data before activating |

## Before you start

- You'll need to be an **Owner or Admin** in Userflow to connect Slack. Owners, Admins, and Editors can build and manage workflows (Editors can't delete them).
- You'll need permission to install apps in your Slack workspace.
- Each Userflow account connects to **one Slack workspace** at a time.
- Notifications post to **public channels** in your connected workspace.
- Don't delete your Slack Zaps yet — keep them running until your native workflows are tested and active, then turn them off (Step 3).

## Step 1: Connect the native Slack integration

1. Sign in to Userflow and go to **Settings → Integrations**, then click **Add integration**.
2. Find and select **Slack**, then click **Add Slack**.
3. Click **Connect with Slack**. In the pop-up, choose your Slack workspace (if you belong to more than one).
4. Review the permissions Userflow requests — viewing and posting to public channels — then click **Allow**.
5. You'll return to Userflow with the connection showing as **Connected**, along with your workspace name and options to Reconnect, Disconnect, or view Logs.

## Step 2: Rebuild each Slack Zap as a Notification Center workflow

For each Zap that posts Userflow activity to Slack, build the equivalent workflow.

1. Go to **Settings → Notification Center** and click **Create a workflow**.
2. Give it a descriptive name (for example, "NPS Detractor Alert → CS Team") and an optional description.
3. **Select the event** that triggers it — the same Userflow event your Zap used as its trigger (for example, *Flow Completed* or *Question Answered*). Only events Userflow is actually receiving appear in the list; if your Zap relied on a custom event, make sure that event is genuinely being sent to Userflow first.
4. **Add conditions** (optional) to match your Zap's filters — for example, `flow_name` equals `Onboarding Flow`, or `number_answer` is less than or equal to `6`. All conditions must be true for the notification to send.
5. Under **destinations**, click **Add destination → Slack** and select the channel. You can add multiple channels, and you can mix in email destinations if your Zap also sent email.
6. **Customize the message.** Recreate your Zap's message text and insert dynamic values by typing `{{` and choosing an attribute — for example `{{user_email}}`, `{{company_name}}`, or `{{company_plan}}`. For survey and NPS responses, **Question Answered** is the trigger event you select in Step 1 above — it is not a message field. The answer itself comes through dedicated fields you insert here: **Number Answer** (`{{number_answer}}`) for NPS, scale, and star-rating questions, **Text Answer** (`{{text_answer}}`) for single- and multi-line text questions, and **List Answer** (`{{list_answer}}`) for multiple-choice questions. Each Question Answered event carries one question's answer, so a single workflow can't combine a score and a separate comment — build one workflow per question (for example, one using Number Answer for the score and another using Text Answer for the follow-up comment). For more detail, see [Including survey / NPS results in a Slack notification](https://help.userflow.com/docs/en/building-notification-workflows-notification-center#including-survey-nps-results-in-a-slack-notification).
7. Click **Test** to send a sample notification (it uses placeholder data) and confirm it lands in the right channel and looks right.
8. Click **Save**, then toggle the workflow to **Active**.

## Step 3: Turn off your Slack Zaps

Once your native workflows are active and tested:

1. Open Zapier and find the Zaps that post Userflow activity to Slack.
2. **Turn those Zaps off** — toggle them off rather than deleting them, so you can fall back if needed.
3. Leave any Zaps that do more than post to Slack — see the FAQ below.

## Step 4: Verify everything is flowing

1. Trigger one of the events in your product (or use a workflow's **Test** button) and confirm the message arrives in the right Slack channel.
2. Open **Settings → Integrations → Slack → Logs** to review recent deliveries and catch any errors.
3. Confirm every `{{variable}}` in your message resolves to a real value — an empty placeholder means the attribute isn't set on that user.

## Frequently asked questions

### Will I get double notifications?

Only if both a Zap and a native workflow are firing for the same event. Keep your Zaps on until your workflows are tested and active, then turn the Slack Zaps off so each event posts once.

### Can I keep using Zapier for other things?

Yes. The native Slack integration only replaces Userflow → Slack notifications. Any Zap that does something else — multi-step automations, posting to other tools, or acting on data — keeps working. Turn off only the Slack-posting Zaps the native workflows now cover.

### Which channels can I post to?

Notifications post to public channels in your connected Slack workspace.

### What happens if I disconnect Slack?

Disconnecting stops all active workflows that send to Slack. Any email destinations in those same workflows keep working.