Skip to main content

Slack Notifications

Real-time alerts in Slack for the events that matter: new feedback, campaign launches, budget thresholds, and payout failures.

The integration uses Slack Incoming Webhooks — Slack's standard, non-OAuth mechanism. It's read-only from Slack's side (we can only post, we can't read your channels), no app approval required, and works with the free Slack tier.

What you'll get​

EventWhen it firesWhat's in the message
New feedback receivedA user submits a response that passes AI scoringCampaign name, quality score (0–100), reward amount
High-value feedbackScore ≥ 75Same + "💎" highlight — don't miss the best ones
Budget alertCampaign reward budget passes 80% consumedCampaign name, percentage used
Campaign activatedCampaign transitions from DRAFT to ACTIVE after Stripe paymentCampaign name, budget
Payout failureTremendous returns an error on a reward disbursementResponse ID, error message (actionable)

All notifications are fire-and-forget: if Slack is down, Pay4Feedback's core flow is unaffected. The message is logged and skipped — no retries, no queues.

Prerequisites​

  • A Slack workspace where you have permission to add apps (typically any member unless your admin has restricted it).
  • A channel (or DM) where you want notifications to arrive. Private channels work too.
  • Two minutes.

Step 1 — Create a Slack Incoming Webhook​

  1. Open api.slack.com/apps and click Create New App.

  2. Pick From scratch. Name it "Pay4Feedback" and select your workspace. Click Create App.

  3. In the left sidebar, click Incoming Webhooks. Toggle Activate Incoming Webhooks to On.

  4. Scroll to the bottom and click Add New Webhook to Workspace.

  5. Choose the channel that should receive Pay4Feedback alerts. Click Allow.

  6. Back on the Incoming Webhooks page, copy the URL under Webhook URL. It looks like:

    https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX
Keep this URL secret

Anyone with this URL can post to your channel. Don't paste it into public issue trackers, screenshots, or client-side code. If it leaks, rotate it by deleting the webhook in Slack and creating a new one.

Step 2 — Paste into Pay4Feedback​

  1. In the Pay4Feedback dashboard, go to Settings → Slack Notifications.
  2. Paste the webhook URL into the Webhook URL field.
  3. Flip the Enabled toggle to on.
  4. Click Send test message. A "👋 Test notification from Pay4Feedback" message should appear in your chosen Slack channel within a second or two.
  5. If the test succeeded, click Save Integration.

If the test fails, see Troubleshooting below.

Step 3 — Verify the first real notification​

The simplest live test: open your survey widget in an incognito window and submit a response. Within a second of the response passing AI scoring, you'll see a "⭐ / 👌 / ⚠️ New feedback received" message in Slack, with the quality score and reward amount.

If the test message works but real-event messages don't arrive, double-check the Enabled toggle is on and saved.

Notification examples​

Here's what each notification looks like when it arrives in Slack (rendered by Slack's default Incoming Webhook formatter):

New feedback (high quality):

⭐ New feedback received Campaign: Q2 Pricing Exit Survey Quality: 87/100 Reward: €8.70

High-value feedback:

💎 High-value feedback! (Score: 92/100) Campaign: Q2 Pricing Exit Survey This feedback contains detailed reasoning.

Budget alert:

💰 Budget alert Campaign: Q2 Pricing Exit Survey 82% of budget used. Consider increasing or pausing.

Campaign activated:

🚀 Campaign activated Q2 Pricing Exit Survey is now live and collecting feedback. Budget: EUR 500.00

Payout failure:

❌ Payout failed Response: 7b0f... Error: Tremendous returned: recipient email invalid

Which channel should you use?​

  • Small team / single campaign: use a dedicated channel like #pay4feedback-alerts. Everyone gets the same feed.
  • Multiple campaigns: Slack's Incoming Webhook URLs are per-channel. If you need different campaigns in different channels, create multiple webhooks in Slack — but Pay4Feedback only stores one webhook per tenant today, so all notifications go to one place. Channel routing per campaign is on the roadmap; tell us at sales@pay4feedback.com if you need it.
  • Noisy? Budget alerts and payout failures are low-frequency; the loudest stream is "new feedback received". For teams running 10+ approvals per day, muting the channel's notifications (while keeping the message log visible) is a common pattern.

Troubleshooting​

"URL doesn't look like a Slack Incoming Webhook"​

The test endpoint validates that the URL starts with https://hooks.slack.com/. Most mistakes:

  • You copied your Slack workspace URL instead of the webhook URL. Go back to Incoming Webhooks in your Slack app and copy the URL under Webhook URL specifically.
  • You copied only part of the URL. The full URL is long (>80 characters) and contains three slash-delimited segments after /services/.

"Slack responded with HTTP 404"​

The webhook URL doesn't exist anymore. Reasons:

  • The Slack app was deleted or the webhook was removed.
  • The URL was truncated on copy-paste.

Delete the value in Pay4Feedback, create a new webhook in Slack (Step 1 above), paste, test.

"Slack responded with HTTP 403"​

Slack rejected the request. Usually: the channel the webhook was installed into has been deleted or made private after install. Create a new webhook in Slack and pick a live channel.

Test message succeeds but real notifications don't arrive​

  • Is the Enabled toggle actually on? It's separate from the URL field — both must be set.
  • Did you click Save Integration after enabling? The test endpoint saves automatically; the main "Save" button doesn't auto-enable.
  • For "new feedback" messages specifically: the notification only fires on feedback that passes AI scoring (score ≥ rejection floor, default 30). Completely garbage submissions don't notify — they get silently rejected. Submit a response with a real paragraph of text to trigger it.

Notifications stop firing after working for a while​

Two things to check:

  1. Did Slack rotate or revoke the webhook? Go to api.slack.com/apps → your app → Incoming Webhooks. If it's gone, the URL is dead. Recreate and paste the new one.
  2. Did a workspace admin remove the Pay4Feedback app? Same page — if the app was removed, all its webhooks are invalidated.

The test button is disabled​

The button is disabled until the URL field has text. Paste first, then test.

Disabling notifications​

Toggle Enabled off in Settings → Slack Notifications and click Save Integration. The webhook URL stays saved for easy re-enable later. If you want to permanently remove the URL, clear the field before saving.

To cleanly revoke access from Slack's side as well: api.slack.com/apps → Pay4Feedback app → Manage Distribution → Remove App.

Security notes​

  • The webhook URL is stored in the tenant_settings table at rest, encrypted by AWS RDS (AES-256) along with all other tenant data.
  • Only users with Admin or Owner role on your tenant can view or edit the URL in Settings.
  • All outgoing webhook calls use HTTPS with TLS 1.2+.
  • Pay4Feedback never logs the webhook URL in plain text — only the tenant ID and whether a delivery succeeded.
  • API & Integrations — roadmap for other integration targets (MS Teams, Zapier, Make, webhooks).
  • Contact & Support — if Slack behaves unexpectedly and this guide doesn't cover it.