Form integrations: send submissions where your team works
Every Formboost form can deliver each submission to email, Slack, Discord, Telegram, Google Sheets, Zapier, n8n or an HTTP webhook of your own — configured in the dashboard, no code. Email, Slack, Discord and Telegram are on the Free plan, one destination per form; Google Sheets, Zapier, n8n and custom webhooks start on Starter, where a form can have five destinations, and Pro removes the limit.
Each destination below has a landing page explaining what it delivers and a setup guide in the docs. Make and IFTTT are reached through a webhook rather than a native connection, and Google Sheets is the one destination that connects a Google account — Formboost only reaches the spreadsheets it created.
Webhooks
POST every submission as JSON to any public HTTPS endpoint you control — your API, a serverless function, a CRM — with the headers it needs and a log of every delivery.
Slack
Get form submissions in your Slack channel
Discord
Form submissions to your Discord server
Telegram
Form submissions delivered to a Telegram chat
Email Notifications
Every submission in your inbox, with the fields laid out
Google Sheets
Write every submission to a Google Sheet
n8n
Trigger an n8n workflow on every submission
Zapier
Start a Zap on every submission and reach Zapier's app catalogue
Why Choose Formboost
No Code Required
Set up integrations directly from the dashboard. No API keys or configuration files to manage.
Real-Time Delivery
Form submissions are delivered to your tools instantly. Never miss a submission.
Multiple Integrations
Connect to multiple tools at once. Send each submission to email, Slack, Discord, and more simultaneously.
Never Costs You a Submission
Every submission is stored before any destination is called, and a slow or failing destination is logged with its status code rather than retried — so you can see exactly what reached Slack, your sheet or your endpoint.
Popular Workflows
Email + Slack
Receive form submissions by email and get instant notifications in Slack
Webhooks + Database
Send form data to your backend via webhooks and store it in your database
Automation Platforms
Connect Zapier or n8n directly, or point a webhook at Make, to reach the apps they connect to
Testing and combining destinations
Test before you rely on it
Every destination has a Send test button in the form's Integrations tab. A test delivery goes through the same path as a real submission and is written to the delivery log with its status code, so a wrong Slack URL or a 401 from your own API shows up before a visitor's submission does.
For a webhook, point it at a capture tool such as webhook.site first to see the exact JSON envelope — the same one Zapier and n8n receive.
Destinations add up, per plan
Destinations are additive: the same submission can go to email for the record, Slack for the team channel, and a webhook that creates the CRM contact — each delivered independently, so one failing never holds up another. How many a single form can have is set by the plan: one on Free, five on Starter, and no limit on Pro and Business.
Every submission is stored and visible in the dashboard whether or not a destination succeeds; the delivery log records each attempt. See pricing for the full table.
Get started with Formboost integrations
Pick an integration above to learn more. Set up takes just a few minutes.