Integrations
Connect Slack lead notifications
Post a message to a Slack channel for each new lead, using a Slack incoming webhook you create.
On this page
Slack is a managed destination: Snapbar formats the message, delivers it, retries on failure, and records the result in Activity. Connect the channel once at the team level, then attach it only to the experiences that should post there. You need integrations enabled and owner or admin access.
Create an incoming webhook in Slack
Open Slack’s app settings and create or select an app for your workspace. Turn on Incoming Webhooks, select Add New Webhook to Workspace, choose a channel, and authorize it. The Slack setup guide below walks through these screens.
Open Slack’s webhook setup guideCopy the webhook address. It starts with
https://hooks.slack.com/services/. Treat it as a secret: anyone who has it can post to that channel.
Connect the channel in Snapbar
Open Integrations > Destinations and select Connect destination, then choose Slack.
Paste the incoming webhook address, add a channel name such as
#leadsso teammates recognize it, and select Connect Slack.Snapbar posts a Snapbar connected message to the channel right away. If the connection saves but that message does not arrive, check the webhook address and contact Snapbar to replace the connection.
Next: attach Slack to an experience. Confirm the destination shows Active, then follow Send leads to a connected destination. The connection message alone does not enable guest notifications.
What to know
- What the message contains.A header reading New lead at followed by the experience name, the guest name (or Not provided), a company when the lead form captured one, a View media button that opens the first finished photo when media is ready, and a footer noting whether it was sent at submission or at completion. Guest email addresses are not posted. Slack ignores the Advanced field mappings on the experience: the message layout is fixed, so leave that panel closed.
- Test leads post to the real channel.Send test lead posts a sample guest named Test Lead to the connected channel as a normal New lead at message. The sample email is not displayed in Slack, and the test creates no Activity record. Confirm the message in Slack; use a real guest-flow rehearsal to verify Activity.
- Connections belong to the team.Connecting posts a confirmation message. Guest notifications start only after you attach the channel to an experience and save its timing and consent settings.
- Status meanings.Active is healthy. Reconnect required means Slack rejected the webhook and sending has stopped; contact Snapbar to replace the connection with a fresh address. Action needed means the connection test or a recent send failed; deliveries wait until the connection is healthy again, so contact Snapbar to replace the connection with a working address.
- Volume and retries.Snapbar sends at most three messages to one connection at a time and up to 20,000 per day. Beyond that, deliveries wait and resume automatically. A Slack rate limit response or outage is retried on the schedule in the delivery retry ladder in Partner API errors and limits, and the current delivery status and attempt count show in Activity; see Fix failed deliveries.
- Removing a connection.Destination actions are not available in the dashboard yet. To remove or replace a Slack connection, detach it from every experience and contact ops@thesnapbar.com.
Tips
- Use a dedicated test channel for rehearsal. To switch channels, create the new Slack webhook, detach the old destination from each experience, and ask Snapbar to replace the connection before attaching and testing it again.
- If the Slack webhook address was exposed, revoke it in Slack and contact Snapbar to replace the connection.