Slack alerts for new leads: five ways to do it, from free to paid, and how to make sure none are missed

By Ranjit Bhinge, founder of Blur Studio · Updated · 9 min read

Short answer: Slack is a team chat app, and a Slack lead alert is a message that appears in a channel the moment someone sends your website form. The cheapest route is a Slack incoming webhook, a private web address that posts a message into one channel, fed by a small automation. The easier routes use an automation tool such as Zapier or Make, your CRM, or a website platform with a Slack connection. Whatever you pick, test it with a real submission and keep a second copy of every lead outside Slack.

Ranjit Bhinge

You want every new website lead to show up in Slack in seconds, without paying for more tools than you need.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

There are five practical routes, and which one is right depends on where your form lives and how many tools you already pay for. In short: if your form tool has its own Slack connection, use it. If not, a free automation plan is usually enough for a small business. If you already use a CRM, start with its workflow. A custom build only makes sense when you need routing rules the others cannot express.

Two terms first. A webhook is a web address that receives a message when something happens, such as a form being sent. A CRM (customer relationship management system) is the tool where you keep contacts and deals. Prices and limits below are as of November 2026, so check each vendor's page before you buy.

This page may contain affiliate links from which Blur Studio earns commissions.

The options, from least to most effort

OptionCostGood forWeak point
No tool: a shared inbox that people watchFree (your time)Under 5 leads a monthDepends on people noticing
Form tool with its own Slack connectionCheck the form tool's pageThe simplest setupNot every form tool has one
Slack incoming webhook plus a small automationSlack side: check the plan rules (see below)Low cost, one channelSomeone must reshape the data
Zapier or Make, automation tools that connect apps without codeFree tiers exist; Zapier Pro is about $19.99 a month billed annuallyMost small businessesFree tier limits
A CRM workflow, such as HubSpotCheck the vendor pageTeams that already use the CRMPlan limits on workflows
A website platform with a Slack connection, such as PloySlack connection needs Ploy Starter ($50 a month, or $480 billed yearly) or aboveSites built and run on that platformTied to the platform

The Slack side is cheap in every option. Slack's pricing page lists a Free plan at $0 (with 90 days of message history and up to 10 apps), Pro at $7.25 per user per month billed annually or $8.75 billed monthly, and Business+ at $15 billed annually or $18 monthly. Enterprise+ lists $45 per user per month billed annually and a sales contact. The part that costs money is usually the middle layer, not Slack.

Option A: the free route with a Slack incoming webhook

Slack's own developer page describes the idea. You create an app in Slack's app settings, turn on incoming webhooks, and Slack gives you a webhook URL. Anything that sends a JSON message to that URL posts into the channel you chose. JSON is a plain-text format for sending named values. Only a field called text is required, and Slack's documentation states you cannot override the channel, username or icon in the request.

Three facts to respect:

  • The URL is a secret. Slack's page says the webhook URL contains a secret and warns against sharing it online, including in public code repositories. Slack actively looks for leaked ones and revokes them. Store it in your automation tool's secure settings, not in a public page's code.
  • The format matters. A form tool sends its own JSON, and Slack expects a message with a text field, so something has to turn one into the other. That is the job of an automation tool or a small script.
  • Limits are not stated on that page. Slack's webhook page does not state a rate limit or which plans may use incoming webhooks. Check Slack's current documentation if you expect many messages per minute.

If you do not have a developer, the webhook route still works through an automation tool, described next, and the tool manages the plumbing.

Option B: Zapier or Make

Zapier is an automation service where you build a Zap: a trigger (form sent) and an action (post to Slack). Its pricing page shows a Free plan with 100 tasks a month and two-step Zaps only, Pro at about $19.99 a month billed annually or $29.99 billed monthly for 750 tasks, and a Team plan with more tasks. Webhook connections start at Pro, so on the Free plan the trigger has to be a form app that Zapier already supports, not a generic webhook. Make is a similar tool that uses a visual canvas. Its pricing page lists a Free plan with 1,000 credits a month; check its page for current paid prices. For a detailed comparison, see Zapier versus Make.

Many form tools connect to both. For example, Tally, a free-to-start form builder, lists Zapier, Make and webhooks among its free integrations on its pricing page. For ways to get leads out of an email inbox and into the tool you follow, see getting website leads out of email. If your build or site updates also need Slack alerts, see Slack alerts when your website updates or a build fails.

Build the Zap in this order: choose the form as the trigger, choose Slack's "send channel message" as the action, map the fields into a message (template below), send a test and fix the mapping. Then turn it on.

Option C: a CRM workflow

If your leads already flow into a CRM, let the CRM do the alerting. HubSpot, a CRM and marketing platform, shows one per-seat pricing page with a Free plan for up to 2 users and paid plans above it, and its workflow tools and Slack actions depend on the plan, so check HubSpot's page for which plan includes what you need. The advantage is that the alert comes from the same record your team already works in, so you never have a lead in Slack that is missing from the CRM. See how to get website visitors into HubSpot for the first half of that pipeline.

Option D: a website platform that connects to Slack, such as Ploy

Ploy is an AI platform that builds, hosts and improves a business website through a chat with an AI agent. Its docs list Slack among the integrations, described as posting automated digests, alerts and deal celebrations to channels and routing notifications to the right team. One example prompt in the docs is asking the agent to post a daily traffic digest to a marketing channel. Ploy's integration plan table puts Slack on Starter and above, and the Starter plan is $50 a month ($480 a year) on Ploy's pricing page as of November 2026. Free does not include Slack.

Forms built into a Ploy site capture each submission and keep it in a Submissions view, and you can add notification emails. The docs say the agent can also forward a copy of submissions to another tool. Whether Ploy posts a single new submission to Slack the moment it arrives, rather than in a digest, is something to test on a real form before you rely on it. Separately, Ploy has a "Ploy in Slack" feature that lets you chat with its agent from Slack, which the docs say is rolling out and is not available for organizations that require single sign-on. That is a different thing from lead alerts.

Ploy fits when the site already runs on it and you want one place for pages, forms and alerts. If your site is elsewhere, it is not worth moving only for Slack alerts. For the wider list of what Ploy connects to, see Ploy's integrations. If you want to test the Slack connection, start a Ploy workspace, build one form and check what the alert looks like before you commit.

A lead alert message you can copy

A good alert tells someone what to do, not only that something happened. Keep personal data to the minimum, because Slack channels are visible to every member.

  • Line 1: New lead: [name], [service they asked about]
  • Line 2: Contact: [phone or email]
  • Line 3: Page they came from, and the time
  • Line 4: Link to the full record in your CRM or sheet
  • Line 5: Owner: reply "mine" in the thread to claim it

The claim rule is the cheapest fix for the usual failure, where five people see an alert and each assumes someone else will answer. Pair it with a response target: for how fast to answer, see a speed-to-lead system for a small service business.

Reliability checks that matter more than the tool

  1. Keep a second copy. Slack's Free plan keeps 90 days of message history, so Slack is an alert, not a record. Store every lead in a sheet or CRM as well.
  2. Keep the email notification for the first weeks. Retire it only after a month of clean tests.
  3. Add a failure alert. Most automation tools can email you when a run fails. Turn that on.
  4. Watch for spam. One bot can flood the channel. See how to stop spam on your contact form.
  5. Test the edge cases. A form with a missing phone number, a very long message, and an apostrophe in a name.
  6. Protect the secret. If a webhook URL ever leaks, revoke it in Slack and create a new one.
  7. Name one owner for the automation, so someone notices when it stops.

If forms are not reaching you at all, start with the form-not-sending fix checklist.

Worked example with made-up numbers

A three-person renovation company gets about 40 form leads a month. It chooses a form tool with a Zapier connection, Zapier's Free plan (100 tasks a month, two-step Zaps) and Slack Free. If each alert counts as one task, which you should confirm on Zapier's page, 40 leads use 40 of 100 tasks. The monthly cost is $0. The company adds a quote-request follow-up task later and sees it would hit the 100 task limit, so it plans a move to a paid plan at the point it nears the limit. The alert, a claim thread and a CRM copy make up the whole system. The risk it accepts: if the Zap fails, an email alert tells the owner.

Test plan with pass and fail criteria

  1. Send a real submission from the live form. Pass: a message appears in the channel within about a minute. Fail: nothing, or more than a few minutes.
  2. Check every field in the message against the form. Pass: all fields present and correct. Fail: a blank or swapped field.
  3. Send a second test with special characters. Pass: it posts correctly. Fail: it is cut off or dropped.
  4. Turn the automation off on purpose and send a test. Pass: you get the failure email or still receive the fallback email. Fail: silence.
  5. Ask a colleague to claim the lead in the thread. Pass: they know the rule without help.

When another route is the better pick

  • Your team does not use Slack. Use email, text or a CRM mobile alert.
  • You get hundreds of leads a day. A channel of alerts becomes noise. Use CRM views and assignment rules instead.
  • You need routing by service, area or availability. A no-code tool gets clumsy. A custom build suits that.
  • Leads contain sensitive details. Keep them in the CRM and post only a link in Slack. Check local law and your privacy policy.
  • Your site is not on Ploy and you are happy elsewhere. Skip Ploy and use a form tool with Zapier or Make.

How I'd approach this

I would start with the cheapest option that has a second copy of each lead, which is usually a form tool plus a free automation plan plus a sheet, and only add a paid tier when a limit actually bites. A message nobody claims is worse than no message, so the claim rule matters more than the tool.

First week plan: on day 1, decide the one channel and who owns the automation. On day 2, set up the form to store each lead in a sheet or CRM. On day 3, build the alert with the template above. On day 4, run the test plan. On day 5, keep the email notification on, write down how many leads arrived against how many alerts, and fix any gap. Review again after 30 days. If your rules outgrow no-code tools, Blur Studio builds the custom version: lead routing, CRM and calendar connections and alerts that match how your team works. See what a custom build includes, and when Zapier automations need custom software.

Related guide: How to Link Meta Ad Results to the Pages People Land On.

Questions people ask

How do I send a website form lead to Slack for free?

Create a Slack incoming webhook, which gives you a private URL that posts into one channel, and connect your form to it through a free automation plan or a form tool with a Slack connection. Slack's Free plan costs $0 but keeps only 90 days of message history, so store each lead elsewhere too.

Does the Slack Free plan allow incoming webhooks?

Slack's webhook documentation page does not state a plan requirement, so check Slack's current pricing and help pages before you build. Its Free plan allows up to 10 apps, so check whether your automation counts toward that.

What is the rate limit for Slack webhooks?

Slack's webhook page does not state one. If you expect bursts of messages, check Slack's current documentation, and consider sending one summary message instead of many.

Can Zapier's Free plan send form leads to Slack?

Yes if the form tool has a Zapier connection, because a two-step Zap (form trigger, Slack action) fits the Free plan's limits of 100 tasks a month and two-step Zaps. Generic webhook connections start on Pro, per Zapier's pricing page. Check how Zapier counts a task. See Zapier versus Make.

Should the alert include the lead's phone number and email?

Include the minimum needed to act, such as name, service and a link to the full record, and keep sensitive details in your CRM. Everyone in the channel can read the message. Check local law and your privacy policy on how you handle personal data.

Does Ploy send Slack alerts for form leads?

Ploy's docs list Slack as an integration that posts digests and alerts, and it needs the Starter plan or above. Whether a single new submission posts to Slack instantly is something to test on a real form. See Ploy's integrations.

Why do leads still get missed with a Slack alert?

Usually because nobody owns the response. Several people see the alert and each assumes someone else will reply. Add a claim rule, a response time target and a failure alert for the automation. See speed to lead.

When should I build a custom lead alert instead?

When you need rules a no-code tool handles badly: routing by area or service, availability checks, duplicate detection, or alerts that depend on data from several systems. A custom build costs more up front and gives you full control.

More in this topic: Websites: agency billing, partners and team workflows (6 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…