Integrations Overview
Every destination a Formboost form can deliver to — email, Slack, Discord, Telegram, Google Sheets, Zapier, n8n, webhooks — with plan availability and setup.
Formboost can notify external services the moment a form is submitted — no code or servers required.
Getting There
- Log in to your dashboard
- Open the form you want to connect
- Click the Integrations tab
- Pick a service and follow the setup guide
Available Integrations
| Integration | What it does | Plan | Connected with |
|---|---|---|---|
| Email notifications | Email every submission to the form's address (a form setting, not on this tab) | Free | An email address |
| Slack | Post a notification to a Slack channel | Free | An Incoming Webhook URL |
| Discord | Post a message to a Discord channel | Free | A channel webhook URL |
| Telegram | Send a message to a user, group, or channel | Free | A bot token and chat ID |
| Google Sheets | Write every submission to a spreadsheet Formboost creates | Starter | A Google sign-in (drive.file scope) |
| Zapier | Start a Zap and reach any app Zapier connects to | Starter | A Webhooks by Zapier catch-hook URL |
| n8n | Trigger an n8n workflow, self-hosted or cloud | Starter | A Webhook node's production URL |
| HTTP Webhook | POST submission data to any custom endpoint | Starter | Any public HTTPS URL, plus optional headers |
How Many Per Form
A form on the Free plan delivers to one destination; Starter allows five per form and Pro removes the limit. Email notifications count as a destination, so a Free-plan form that should post to Slack turns email off, and a Starter form can do both.
What Every Destination Has in Common
- Delivery happens after the submission is stored. A destination that is slow or down never delays the response your visitor sees and never loses the submission.
- One attempt, then a log. Formboost does not retry a failed delivery. Every attempt — real or test — is recorded with its status code under Integrations → Delivery Logs, so a missing Slack message is a log entry, not a mystery.
- Send test is on every integration. It delivers a
form.submission.testpayload without creating a submission, so you can confirm the connection before the form goes live. - Spam and over-limit submissions are not delivered. They are stored and visible in the dashboard, but nothing is posted for them.
- Make and IFTTT have no native connection; point an HTTP Webhook at their webhook triggers instead.
Every integration above tells you about a submission. To email the person who filled in the form instead, see Auto Reply. It is a form setting rather than an integration, so you will find it in Form Settings and not on this tab.
Troubleshooting Submissions and Deliveries
What to check when a submission, email, webhook or chat message does not arrive, a real message is marked spam, or the redirect lands on the wrong page.
Set Up an HTTP Webhook
Deliver every submission as a JSON POST to your own HTTPS endpoint: the payload, custom auth headers, the 15-second timeout, test deliveries and the log.