Collecting feedback in a preview environment is only half the battle. The other half is making sure the right person on your team sees it immediately — not tomorrow morning, not after the client has already sent a follow-up email wondering if you got their notes.

prev's Notifications & Webhooks let you route feedback submissions directly to Slack, Discord, email, or any custom webhook the moment they come in. No polling required.

What Are Notification Profiles?

A notification profile is a named configuration in your Dashboard that maps a project to a set of notification channels. When you deploy a preview with --feedback --notify <name>, any feedback submitted on that environment is routed through the profile's configured channels.

This means you can have:

  • acme-corp → Slack channel #acme-reviews + project manager's email
  • beta-project → Discord channel + Linear webhook
  • internal-qa → Slack channel #qa-team only

Each preview is wired to exactly the channels that make sense for it — no noise, no cross-contamination.

Setting Up Your First Notification Profile

Notifications & Webhooks are a Business plan feature. To create one:

  1. Open the Dashboard and navigate to Notifications & Webhooks
  2. Click + New Profile
  3. Enter a Name — this is the slug you'll use with --notify. Use something short and memorable like acme-corp or project-beta
  4. Optionally add a Display Label for clarity in the Dashboard
  5. Configure one or more notification channels (Slack, Discord, Teams, Google Chat, Email, Webhook)
  6. Click Create Profile

Connecting Slack

The most common setup is routing feedback to a dedicated Slack channel. Here's how:

  1. Go to api.slack.com/apps and open or create an app for your workspace
  2. Enable Incoming Webhooks under Features
  3. Click Add New Webhook to Workspace and select the channel to receive notifications
  4. Copy the webhook URL
  5. Paste it into the Slack Incoming Webhook field when creating or editing a notification profile

Once configured, every feedback submission on environments linked to this client posts a message to your Slack channel — including the reviewer's comment, approval status, which page they were on, and a direct link to the preview.

Connecting Discord

Discord setup is even simpler:

  1. Open your Discord server and go to the channel you want to use for notifications
  2. Click the gear icon (Edit Channel) → Integrations → Webhooks → New Webhook
  3. Give the webhook a name (e.g. "prev Feedback") and copy the URL
  4. Paste it into the Discord Webhook field in your notification profile

Deploying with a Notification Profile

Once a profile exists in your Dashboard, reference it by name when deploying: 

prev --feedback --notify acme-corp .

You can combine this with all other prev flags: 

prev --feedback --notify acme-corp \
     --subdomain acme-march-sprint \
     --ttl 14d \
     --region eu \
     .

CI/CD with Per-Profile Notifications

For teams managing multiple projects through CI/CD, you can parameterize the profile name: 

name: Preview with Notifications

on:
  workflow_dispatch:
    inputs:
      notify:
        description: 'Notification profile name'
        required: true
      subdomain:
        description: 'Preview subdomain'
        required: true

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Install prev
        run: curl -fsSL https://prev.sh/install.sh | sh

      - name: Deploy Preview
        run: |
          prev --feedback \
               --notify ${{ github.event.inputs.notify }} \
               --subdomain ${{ github.event.inputs.subdomain }} \
               --ttl 14d \
               .
        env:
          PREV_API_KEY: ${{ secrets.PREV_API_KEY }}

Trigger the workflow manually from the GitHub Actions UI — specify the client name and subdomain per deployment. Each client's feedback goes to their own Slack channel automatically.

Custom Webhooks for Advanced Integrations

Not using Slack or Discord? The custom webhook option lets you integrate with any system that accepts an HTTP POST. Common use cases:

  • Linear / Jira: Create an issue automatically for each "Changes Requested" submission
  • Basecamp: Post feedback as a to-do item in the relevant project
  • Custom dashboards: Feed feedback into an internal analytics or CRM system
  • Make / Zapier: Chain into any no-code automation

The JSON payload includes the full feedback data — message, approval status, reviewer name, page URL, and environment details. See the webhook payload reference for the exact schema.

Multiple Channels Simultaneously

A single notification profile can have all channels configured at once. If you configure Slack, Teams, and a webhook, prev delivers to all three for each feedback submission. This is useful when:

  • The developer team monitors Slack but the account manager monitors email
  • You need both human-readable notifications (Slack/Discord) and machine-readable ones (webhook)
  • A client insists on email but your team lives in Slack

Filtering in the Feedback Inbox

Even with real-time Slack notifications, the Dashboard Feedback Inbox remains the canonical record of all submissions. You can filter by notification profile to see only feedback for a specific project, which is useful for:

  • Status meetings: "Here's all feedback we've received for Acme Corp this sprint"
  • Approval tracking: Filter by Approved to confirm a client has signed off
  • Audit trails: Every submission is preserved with timestamp and page URL

Getting Started

If you're on the Business plan, create your first notification profile in Dashboard → Notifications & Webhooks and add --notify <name> to your next deployment. Full setup instructions are in the Notifications & Webhooks documentation.

Not on the Business plan yet? The Feedback & Review Workflow (without notification routing) is available on all paid plans. Compare plans to see what's included.