Slack, Discord, and Microsoft Teams channels
Connect a chat channel once and every captured lead lands as a rich message — Slack via OAuth, Discord and Teams via webhook URL.
Heads up: chat channels now live in Routes
Important
Chat channels have moved into Routes (under Deliver in the sidebar) and the Notifications item was removed from the sidebar. The /notifications URL still works — it now opens with a banner pointing you to Routes, and the email-alert, digest, and channel settings still sit below that banner. For new setups, build a Route with a Slack, Discord, or Microsoft Teams destination — you get the same alerts plus conditions like "only if AI score is Hot". See the Destinations & integrations category for the up-to-date setup guides (Connecting Slack, Connecting Discord, Connecting Microsoft Teams).
The instructions below still describe the historical Notifications-page flow and are kept for users on older accounts. The mechanics of the Slack OAuth and Discord/Teams webhook URLs themselves have not changed — only where you configure them in the UI.
Why connect a chat channel
Email alerts are great for individual reviewers; chat channels are where teams actually triage leads in the moment. Connect Slack, Discord, or Microsoft Teams once and every new submission lands as a formatted message with the visible fields, the form name, the page it came from, the source/UTMs, and a link straight to the lead in your dashboard.
Channels run alongside email recipients and digest emails — they don't replace either. Pick any combination of email and chat destinations per site.
Note
Spam submissions are never sent to chat channels. The delivery is skipped automatically, just like email alerts.
Connecting Slack
Slack uses OAuth — no copy-pasting webhook URLs. Once you authorise the LeadToSheet app, every Slack channel in your workspace becomes available in a dropdown.
- 1
Open Notifications
From the sidebar, choose the site you want to receive alerts for, then click Notifications.
- 2
Click Add channel
In the "Connected channels" card, click "Add channel" and pick the Slack tile.
- 3
Click Add to Slack
You'll be redirected to Slack to approve the LeadToSheet app's permissions for your workspace. Approve and Slack sends you back to LeadToSheet.
- 4
Pick a channel
In the dropdown, choose any public channel (or a private channel the bot has been invited to). The label auto-fills with your workspace and channel name — edit it if you'd rather see something else next to the chip in the destinations picker.
- 5
Save and pick destinations
Click Connect. The new channel shows up in the Connected channels list and is now selectable in the Send alerts to / Send digests to chip pickers below.
- 6
Send a test
Click "Test" on the channel row to deliver a sample message. If the test posts in Slack, real lead alerts will too.
Tip
Public channels work without inviting the bot. For private channels, /invite @LeadToSheet in Slack first, then refresh the channel dropdown in LeadToSheet.
Connecting Discord
Discord uses an incoming webhook URL. Each Discord channel can mint its own webhook in seconds.
- 1
Create the Discord webhook
In Discord, open the channel you want lead alerts in. Click the gear icon → Integrations → Webhooks → New Webhook → Copy Webhook URL.
- 2
Add it to LeadToSheet
In LeadToSheet, open Notifications for the site, click Add channel, pick the Discord tile, give it a label (e.g. "Sales (Discord)"), and paste the webhook URL.
- 3
Test it
Click Connect, then click Test on the new row to send a sample message and confirm it lands in your Discord channel.
Note
@everyone and @here pings inside lead text are silently neutralised so a malicious form submission can't trigger a workspace-wide ping.
Connecting Microsoft Teams
Teams supports two webhook formats: the modern Power Automate flow and the legacy Incoming Webhook connector. Either works.
Power Automate (recommended)
- In Teams, open the target channel, click the … menu, choose Workflows.
- Pick the template Post to a channel when a webhook request is received.
- Walk through the prompts — when it ends, copy the HTTP POST URL.
- Paste that URL into the LeadToSheet Add channel dialog with the Teams tile selected.
Legacy Incoming Webhook
- In Teams, open the channel, click … → Manage channel → Connectors.
- Find Incoming Webhook → Configure → name it LeadToSheet → upload an icon → Create → copy the webhook URL.
- Paste into LeadToSheet's Add channel dialog with Teams selected.
Tip
Both URL shapes are accepted: outlook.office.com, *.webhook.office.com (tenant-prefixed), and *.logic.azure.com (Power Automate). Anything else is rejected at validation time.
Routing alerts to specific channels
Once a channel is connected, it appears in the "Send alerts to" and "Send digests to" chip pickers on the same page. Click "+ Add channel" inside a picker to drop in a Slack/Discord/Teams chip alongside any email recipients you already have. Each picked destination receives every captured lead independently.
Tip
Different sites, different channels. Notification settings are per-site, so an agency can send Acme leads to #acme-sales and Beta Corp leads to a Beta Teams channel without crosstalk.
When something goes wrong
- A failed delivery leaves a red "check connection" badge on the channel chip and surfaces the error in the channel row.
- The most common Slack error is account_inactive or token_revoked — reconnect the workspace by removing the channel and clicking Add to Slack again.
- For Discord and Teams, a 404 usually means the webhook was deleted in the source app. Recreate the webhook there and paste the new URL.
- Other deliveries to the same site are unaffected by one channel failing — each delivery is fired independently.
Note
Limits: each site can have up to 25 connected channels, and each alert has a 5-second delivery timeout per channel. For security, LeadToSheet only accepts webhook URLs on the official Slack, Discord, and Microsoft Teams (and Power Automate) domains — pasting any other URL is rejected when you save the channel.