splitforms.com
13 INTEGRATIONS · 6 CATEGORIES

splitforms Integrations — connect to Slack, Sheets, Notion & 10 more.

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 500/mo plan — no credit card.

Free plan covers 500 submissions/month. Pro is $5/mo. There's also a $59 3-year plan (36 months of access).

CategoriesMessaging5Spreadsheets1Database2CRM1Automation3Email1

How splitforms integrations work

Two delivery modes, deliberately small surface area. We'd rather ship two reliable mechanisms than ten flaky “native” integrations that break every six months.

01
Native (auto-detected)

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.

02
Webhook + relay

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.

03
Email always wins

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.

Frequently asked questions

How do splitforms integrations work?

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.

Do integrations cost extra?

No. Outbound webhooks — and the native Slack and Discord formatting — are part of the splitforms free plan, which includes 500 submissions per month. Pro ($5/mo, 5,000 submissions) and the $59 3-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.

Which integrations are 'native' versus webhook-based?

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.

Can I send the same submission to multiple destinations?

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.

What happens if a webhook destination is down?

splitforms retries failed webhook deliveries with exponential backoff (up to four attempts). Dashboard storage happens regardless of webhook outcome, so the submission remains available even if every webhook fails. Starter notification email is handled separately from webhook delivery. You can replay failed webhooks from the dashboard once the destination is back up.

Is there a native HubSpot or Salesforce CRM integration?

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.

Are webhook URLs stored securely?

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.

How does this compare to Formspree or Web3Forms?

Formspree gates Slack and webhooks behind paid tiers (Slack starts at $10/mo). Web3Forms ships fewer destinations and slower delivery. splitforms starts Slack, Discord, Zapier, and Make-compatible webhooks on Starter at $1/month — and the integration pages on this site are honest about which destinations are native versus webhook-based.

Ship a form, route it anywhere.

Free for 500 submissions per month. Add Slack, Sheets, Notion, Zapier, and more from the dashboard — no code changes to your form markup. No credit card.

Start free See pricing