LeadRails
Docs navigation

Slack Webhook

Send leads to a Slack channel as a formatted message via an incoming webhook URL. The webhook URL itself is your authentication — keep it private.

What this is

Slack incoming webhooks accept JSON payloads at a unique URL per channel. LeadRails formats each lead event as a Slack message with the lead's name, contact info, and any UTM context, then POSTs it to the webhook URL. No two-way conversation — Slack receives, doesn't respond.

Where to find your webhook URL

  1. Sign in to your Slack workspace as an admin.
  2. Visit https://api.slack.com/apps → "Create New App" (or pick an existing one).
  3. Pick "From scratch", give the app a name (e.g. "LeadRails"), select your workspace.
  4. From the app's settings, click "Incoming Webhooks" in the left nav.
  5. Toggle "Activate Incoming Webhooks" to ON.
  6. Click "Add New Webhook to Workspace" at the bottom.
  7. Pick the channel where leads should land (you'll need permission to post in it).
  8. Slack returns a URL like https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXX — copy this exactly.

Security note

Treat this URL like a password. Anyone with it can post to your channel. Slack lets you regenerate the URL if it leaks.

In LeadRails

  1. Sign in → Destinations → New.
  2. Adapter type: Slack Webhook.
  3. Webhook URL: paste the URL from step 8 above.
  4. Mention (optional): @channel, @here, @username, or leave blank for no mention.
  5. Click Create.

Test it

  1. Go to Sources → click your source → Settings tab.
  2. Wire a route from this source to your new Slack destination (if you haven't already).
  3. Click "Send test event" in the SourceTestEvent card.
  4. Slack message arrives in your channel within seconds.

Message shape

  • Default Slack message contains: lead name (bold), email, phone, source URL, UTM tags.
  • LeadRails uses Slack's Block Kit format for clean rendering.
  • Future: per-route mapping lets you customize what fields end up in the message (use the Routes page → mapping editor).

Common issues

invalid_payload
The Slack workspace deactivated the webhook (admin disabled it, or the channel was archived). Regenerate the URL.
channel_not_found
The channel was deleted. Pick a new one in Slack and add a new webhook.
action_prohibited
The webhook was created without permission. Talk to a workspace admin.
No message arrives but no error
Check the Jobs page in LeadRails for the actual delivery status. The "Send test event" result panel will deep-link.

Compliance

  • Slack webhooks are best-effort delivery. No SLAs from Slack itself for incoming webhooks.
  • Slack retains your messages per your workspace's data retention settings — review with your IT team.
  • No PII restrictions from LeadRails's side, but check your own org's policy before piping leads to a public channel.
← All destination guides