← View All Guides
Zapier logo
Integration Guide

How to Send Referral Notifications to Slack with Zapier + GrowSurf

Use GrowSurf events in Zapier when Slack alerts need channel routing, branching, or message logic beyond the native Slack integration alone.

Want the full setup walkthrough?

Use these docs for exact setup steps, supported fields, and troubleshooting.

GrowSurf already offers native Slack notifications, but Zapier is the better option when those alerts need to branch, filter, or trigger extra steps before the message is posted.

This is especially useful when different referral events should land in different channels, or when only specific reward states should alert the team.

Integration Steps

Choose the GrowSurf event that should create the Slack alert

Selecting a GrowSurf trigger in Zapier for a Slack notification workflow
Pick the GrowSurf trigger that matches the Slack alert you want the team to see.

New Participant Reward is a strong default when Slack is mostly used for reward-earned alerts, but New Participant or Campaign Ended can also work depending on the audience and urgency.

Add a Filter before the Slack step when only some events should post

Adding a Filter step in Zapier before a Slack action
A Filter step keeps the wrong referral events from posting to Slack and gives you cleaner channel-specific alerts.

Use a Filter if you only want alerts for approved rewards, referrers, or one campaign. Use Paths when different events should route to different Slack channels.

Build the Slack action with the fields your team actually needs

Map the GrowSurf details that help the team take action quickly, such as participant email, reward status, referral counts, or the share URL. Keep the message compact so the alert is still easy to scan in-channel.

Test the message in the destination channel

Before publishing, send a real test event through the Zap and confirm the message format, channel destination, and links all look right inside Slack.

Use Zap History to debug noisy or missing alerts

If a message posts when it should not, or never arrives at all, check Zap History first. It will show whether the issue came from the trigger payload, the Filter step, or the Slack action.

Tips

Use the native Slack integration first if simple alerts are enough

Zapier adds value when you need routing, branching, or extra action steps. If the team only needs straightforward notifications, the native Slack integration is usually simpler.

Route by team or workflow, not by every possible event

Slack alerts get noisy fast. Build channels around who needs to act on the event rather than creating a different message for every minor trigger.

Review the first few live posts in Zap History

That is the fastest way to catch a filter that is too broad, a channel mapping mistake, or message text that is missing an important field.

FAQ

When should I use Zapier instead of GrowSurf's native Slack alerts?

Use Zapier when Slack alerts need Filters, Paths, channel routing, or extra actions before or after the message posts. Use the native Slack integration when straightforward notifications are enough.

Do I need separate workflows for referrers and referred participants?

Often yes. GrowSurf's Zapier docs explain that double-sided rewards can generate events for both sides of the referral, so Filters or Paths help keep each alert in the right place.

How quickly do Zapier Slack alerts arrive?

Zapier's current help notes that polling frequency depends on your plan, so some alerts may land a few minutes after the GrowSurf event instead of instantly.

Set up your refer a friend program with customer referral and affiliate program software that lowers your acquisition costs, increases customer loyalty, and saves you gobs of time.

Trusted by marketing and product teams at fast-growing B2C, fintech, and SaaS companies