ASDK and Slack: new-lead alerts in a channel
Get an alert in a Slack channel when ASDK captures a new website lead, through a Slack incoming webhook: how it works, how to set it up and what to watch.
- Status
- Works with ASDK today, during early access.
- Vendor
- Slack website
Agents that work with Slack
Every agent answers from the same knowledge base about your website. Statuses come from the ASDK catalog: early-access agents work today, coming-soon agents do not yet.
How it works with Slack
On this page
A website lead is worth the most soon after it arrives, and if your team already works in Slack, an alert there is seen sooner than an email in a shared inbox. ASDK can post an alert to a Slack channel whenever an agent captures a new lead, so the right person sees it while the visitor still remembers the conversation. It uses Slack's own incoming webhooks, so there is no app to approve from a directory, just a URL you create in your workspace.
What ASDK and Slack do together
ASDK's agents capture leads in two ways:
- Chat (early access, from the Free plan) answers visitors from your content and, when it cannot help, offers to take their contact details so your team can follow up.
- Sales (early access, from the Pro plan) asks the qualifying questions you write in plain language, scores each lead by your rules and offers a meeting to visitors who fit.
With Slack connected, each new lead also becomes a message in the channel you choose. The person on call reads it in Slack and replies to the visitor by email or phone, or prepares for the meeting the visitor booked.
Slack is for alerts, not for the conversation itself. Visitors keep talking to the agent in the ASDK widget; nobody needs to answer chats from Slack in real time.
How it works: Slack incoming webhooks
An incoming webhook is a unique URL that posts messages into one Slack channel. According to Slack's developer documentation, you create one by making an app in your workspace, switching on Incoming Webhooks and adding a webhook to the workspace for a channel you pick (checked October 2026). The same page notes three things worth knowing:
- The URL contains a secret. Anyone with it can post to your channel. Slack actively looks for leaked webhook URLs and revokes them.
- One URL, one channel. The channel, name and icon come from the app's settings; the sender cannot change them.
- Private channels need you in them. To post to a private channel, you must be a member of it when you create the webhook.
Set up Slack alerts
Create a Slack app for the webhook
In Slack's app settings, create a new app from scratch in your workspace. A name such as "ASDK leads" makes the messages easy to recognize. If your workspace requires approval for new apps, ask a workspace admin.
Switch on incoming webhooks
In the app's settings, open Incoming Webhooks, switch on Activate Incoming Webhooks, then click Add New Webhook to Workspace, choose the channel for lead alerts and click Authorize.
Copy the webhook URL
Slack shows a URL that starts with https://hooks.slack.com/services/. Copy it, and keep it private.
Paste it into ASDK
Add the URL to your site's notification settings in the ASDK dashboard, then test it by leaving a lead on your own site through the chat.
A dedicated channel, such as one for website leads, works better than a busy general channel: alerts stay visible, and you can set channel notifications for the people who follow up.
An example: an alert that leads to a booked call
Picture an agency whose website gets two or three serious inquiries a week, mostly outside office hours. It creates a channel for website leads and points the ASDK webhook at it. On a Saturday, a visitor asks about the agency's rates for a website redesign, answers the Sales agent's questions about budget and timeline, and leaves an email without booking a call.
The alert lands in the channel. The founder, who follows that channel on their phone, sees it and replies by email the same afternoon with two suggested times. The visitor books one. Without the alert, the email would have waited until Monday in a shared inbox.
Routing alerts to different people
One incoming webhook posts to one channel. If different leads should reach different people, for example by region or by company size, use an automation tool in between:
- Send new leads from ASDK to a webhook in Zapier or Make. Webhooks are available in early access from the Starter plan.
- Add a filter or a router on the fields you care about.
- Add a Slack step for each route, posting to the right channel or person.
The same automation can also add the lead to your CRM, so one webhook covers both the alert and the record.
What is available and what is coming soon
| Item | Status |
|---|---|
| New-lead alerts to one Slack channel through an incoming webhook | Available in early access |
| Routing alerts by rules through Zapier or Make | Available in early access |
| Answering visitor chats from Slack | Not offered |
| An ASDK app in Slack's app directory | Not needed for alerts |
ASDK as a whole is in early access: the agents work and you can use them, but they may change while we improve them.
Making alerts useful
An alert nobody acts on is noise. A few habits help:
- Agree who answers. Name one person or a rotation for website leads, so an alert never sits in a channel because everyone assumed someone else would reply.
- Set a response target. Research on lead response time suggests minutes matter more than hours; our guide to speed to lead summarizes it and its limits.
- Use the Sales agent's score. If only some leads need an immediate reply, qualify them first. Our guide to qualifying inbound leads shows how to write the questions.
- Review the questions, not just the leads. Leads that Chat captured after an unanswered question point to gaps in your website. Fixing those pages helps every visitor.
Try the Sales agent in early access
Qualifies visitors, books meetings and sends leads to your CRM through webhooks and Zapier.
Sources
Pages we read for this page, with the date we checked each one.
- Sending messages using incoming webhooks — Slack Developer Docs · checked October 21, 2026
Frequently asked questions
Something else? Write to hello@asdk.com
Do I need to install an ASDK app in Slack?
No. Slack alerts use an incoming webhook: you create a small app in your own Slack workspace, pick a channel and paste the webhook URL into ASDK. There is no ASDK app to install from Slack's directory.
Can visitors chat with my team through Slack?
No. Slack gets alerts about new leads. Conversations with visitors stay in the ASDK widget, where the agents answer them; your team follows up by email, phone or a booked meeting.
Is the webhook URL secret?
Yes. Slack says the URL contains a secret, so treat it like a password: paste it only into ASDK, never into a public page or a shared document. If it leaks, remove it in Slack and create a new one.
Can I send alerts to more than one channel?
Each Slack incoming webhook posts to one channel. To route different leads to different channels, send leads to Zapier or Make with a webhook and add a Slack step for each route.