messaging
Discord
Drop submissions straight into a Discord channel.
INTEGRATION · MESSAGING
Send Form Submissions to Slack — splitforms
Send form submissions to a Slack channel — instantly.
Drop a Slack incoming-webhook URL into splitforms and every submission lands in your channel within a second of being submitted. splitforms auto-detects Slack webhooks and formats the payload with rich blocks — no Zapier required.
Delivery mode: Native (auto-detected webhook)
Free for 1,000 submissions/month. No credit card required.
How to set up Slack with splitforms
5 steps. The whole flow typically takes a couple of minutes.
In Slack, create an Incoming Webhook for the channel where you want submissions to land. Copy the webhook URL.
In your splitforms dashboard, open the form's Webhooks tab and paste the Slack URL. splitforms auto-detects the slack.com host and switches to native Slack block formatting.
Send a test submission from the form. The Slack message should arrive within ~1 second with each field rendered as a labelled block.
Optional: customise the channel-level notification using Slack's per-webhook settings. splitforms does not control message routing inside Slack.
Roll the form out. Every future submission will be POSTed to Slack as well as delivered to email — failures are retried with exponential backoff.
example: form markup
<form action="https://splitforms.com/api/submit" method="POST"> <input type="hidden" name="access_key" value="YOUR_SPLITFORMS_KEY" /> <input type="hidden" name="_route" value="slack" /> <input type="email" name="email" placeholder="you@example.com" required /> <textarea name="message" placeholder="Your message" required></textarea> <button type="submit">Send to Slack</button> </form>
The form posts to https://splitforms.com/api/submit. The Slackrouting is configured in the splitforms dashboard against the form's access key — there's no client-side Slack-specific code in your HTML.
Want the long-form walkthrough? Read the deep-dive Slack guide on the blog →
Who uses splitforms + Slack
A handful of patterns we've seen in the wild.
- USE CASE 01Sales teams getting demo requests in #sales-leads as soon as a prospect submits the website contact form.
- USE CASE 02Support inboxes — pipe contact-form submissions into #support so the on-call engineer sees them without checking email.
- USE CASE 03Engineering bug-report forms that drop into #bugs with the reporter's email and reproduction steps pre-formatted.
- USE CASE 04Hiring forms that land in #recruiting so the hiring manager and recruiter both see candidates at the same time.
- USE CASE 05Beta-waitlist signups streaming into a #launch channel so the team can react in real time.
Why splitforms for Slack?
Formspree gates Slack to paid plans; splitforms includes it on the free plan. splitforms is free for 1,000 submissions per month, $5/mo on Pro, or $59 for a 4-year plan (15,000 submissions/month, 48 months of access). No per-integration add-on fees.
Frequently asked questions
Does splitforms have a native Slack integration?
Yes. When you paste a slack.com webhook URL into a form's webhook field, splitforms auto-detects the host and switches the payload from a generic JSON shape to Slack's block-kit format. You don't need Zapier, Make, or any glue code — the splitforms backend handles the Slack-specific formatting itself.
Will Slack messages get delayed if my form is high-traffic?
No. splitforms POSTs to Slack from a queued worker that runs alongside email delivery. The p50 latency from form submit to Slack message delivery is well under one second, and we retry transient failures (5xx, timeouts) with exponential backoff up to four times before failing the webhook.
Can I send the same form to multiple Slack channels?
Yes — add multiple Slack webhook URLs in the form's webhook configuration. Each will be POSTed independently, so a problem with one channel does not block the other. This is useful for piping a single contact form into both #sales-leads and a wider #website-events channel.
Is the Slack webhook URL stored securely?
Yes. Webhook URLs are encrypted at rest in the splitforms database and are only decrypted in-memory at delivery time. The URL is never displayed in full in the dashboard after initial configuration — only the channel name and host prefix.
What does the message in Slack actually look like?
splitforms formats each field as a Slack block with the field label as a bold header and the submitted value beneath it. Long text fields collapse with a 'show more' affordance. The form name and a deep-link back to the splitforms dashboard appear in the message footer for one-click triage.
Can I include only some fields in the Slack message?
Today, splitforms sends every field captured by the form. Field-level redaction is on the roadmap. If you have sensitive fields you don't want broadcast in Slack, capture them in a separate splitforms form that does not have a Slack webhook attached.
Does this work on the free plan?
Yes. Webhook delivery — including the Slack-specific formatting — is available on the free plan, which includes 1,000 submissions per month. You don't need to upgrade to Pro to use Slack notifications.
Connect Slack in 60 seconds.
Free for 1,000 submissions per month. No credit card. Pro is $5/mo. The whole splitforms + Slack setup ships in under five minutes.