Slack
messagingSend form submissions to a Slack channel — instantly.
Pipe form submissions into the tools your team already uses. Native Slack and Discord formatting, generic outbound webhooks for everything else, and Zapier or Make as the universal glue. Free on the 1,000/mo plan — no credit card.
Free plan covers 1,000 submissions/month. Pro is $5/mo. There's also a $59 4-year plan (48 months of access).
Send form submissions to a Slack channel — instantly.
Drop submissions straight into a Discord channel.
Get form submissions as Telegram bot messages.
Pipe submissions into a Microsoft Teams channel.
Auto-append every form submission as a row in Google Sheets.
Send form submissions straight into an Airtable table.
Append submissions as pages in a Notion database.
Create HubSpot contacts and leads from form submissions.
Trigger any Zapier workflow from a form submission.
Trigger Make.com (Integromat) scenarios from form submissions.
Two delivery modes, deliberately small surface area. We'd rather ship two reliable mechanisms than ten flaky “native” integrations that break every six months.
Slack and Discord webhook URLs are auto-detected by host. splitforms switches the payload to that platform's native format — Slack Block Kit or Discord rich embed — with field labels and values laid out for the message UI. Zapier and Make webhooks fall in this same bucket because their generic catch-hooks accept splitforms' default payload as-is.
For Sheets, Notion, Airtable, HubSpot, and Telegram, splitforms POSTs the submission to a small HTTP endpoint you control (a Cloudflare Worker, Vercel function, or any small service). That relay shapes the payload into the destination's API. The relays in our deep-dive guides are typically 15-25 lines each.
Regardless of which webhooks fire (or fail), the submission also lands in the email recipients you configured plus the splitforms dashboard. No webhook outage costs you the lead. Failed webhooks retry with exponential backoff, and you can replay them from the dashboard once the destination is healthy.
<form action="https://splitforms.com/api/submit" method="POST"> <input type="hidden" name="access_key" value="YOUR_KEY" /> <input type="email" name="email" required /> <textarea name="message" required></textarea> <button type="submit">Send</button> </form>
Configure webhooks per-form in the splitforms dashboard. The form markup itself stays exactly the same regardless of which destinations you wire up.
splitforms ships outbound webhooks: every form submission can POST to one or more URLs you configure. For Slack and Discord, splitforms detects the host and switches to that platform's native message format automatically. For other destinations (Sheets, Notion, Airtable, HubSpot), you either point the webhook at a small relay (a Cloudflare Worker, Vercel function, or any HTTP endpoint) or wire it through Zapier or Make. Email delivery happens regardless, so submissions are never lost if a webhook fails.
No. Outbound webhooks — and the native Slack and Discord formatting — are part of the splitforms free plan, which includes 1,000 submissions per month. Pro ($5/mo, 5,000 submissions) and the $59 4-year plan (15,000 submissions per month) raise the volume but don't gate any integration behind a paywall. Zapier and Make have their own pricing on top.
Native (auto-detected and formatted by splitforms): Slack, Discord, Zapier (Webhooks by Zapier), Make (Custom webhook). Webhook-based (you point a webhook at the destination's API or at a tiny relay): Google Sheets, Airtable, Notion, HubSpot, Microsoft Teams, Telegram. Each integration page below is honest about which category it falls into.
Yes. Each form in splitforms supports multiple webhook URLs. Add a Slack URL and a Sheets relay and a Zapier URL — they're POSTed independently, so a problem with one does not affect the others. Email delivery still happens in parallel.
splitforms retries failed webhook deliveries with exponential backoff (up to four attempts). Email delivery happens regardless of webhook outcome, so the submission lands in your inbox and the splitforms dashboard even if every webhook fails. You can replay failed webhooks from the dashboard once the destination is back up.
Today, no — splitforms reaches HubSpot and Salesforce via outbound webhooks plus a small relay (or via Zapier or Make). One-click OAuth connectors for the major CRMs are on the roadmap; the webhook-relay route is reliable in production today and works on the free plan.
Yes. Webhook URLs (which can contain bot tokens or auth secrets) are encrypted at rest in the splitforms database and are not displayed in full in the dashboard after configuration. Each request is also signed with an HMAC header so your relay can verify the request actually came from splitforms.
Formspree gates Slack and webhooks behind paid tiers (Slack starts at $10/mo). Web3Forms ships fewer destinations and slower delivery. splitforms includes Slack, Discord, Zapier, and Make-compatible webhooks on the free plan — and the integration pages on this site are honest about which destinations are native versus webhook-based.
Free for 1,000 submissions per month. Add Slack, Sheets, Notion, Zapier, and more from the dashboard — no code changes to your form markup. No credit card.