Form builder with webhooks: send form data to any URL

A form builder with webhook support sends each new submission to a URL you choose as an HTTP POST request with a JSON body, the moment someone submits. That lets you push form data into your own backend, a database, or an automation tool like Zapier, Make or n8n without waiting for an export or polling an API. In FlowyForm, webhooks are included on the free plan: paste an endpoint URL in the Integrate tab and every completed response is posted to it.
Below: how webhooks work, how to set one up and test it, and five workflows teams commonly build.
How form webhooks work
- A respondent completes your form.
- The form builder sends a
POSTrequest to your endpoint URL with the response as JSON: the form, the submission and each question's answer, plus any hidden fields you passed in the link. - Your endpoint (your server, a serverless function, or an automation tool's webhook trigger) receives the data, returns a
200 OK, and does whatever comes next.
Compared with the alternatives:
| Approach | How data arrives | Good for |
|---|---|---|
| CSV export | Manually, when you download | One-off analysis |
| Google Sheets integration | A new row per response | Teams that work in spreadsheets |
| Native app integration | Directly into one specific app | Simple one-app flows, when the builder supports that app |
| Webhook | JSON posted to any URL per response | Your own systems, databases, and any app through an automation tool |
How to set up a webhook in FlowyForm
- Open your form in the builder and go to the Integrate tab.
- Find the Webhook URL section and paste your endpoint. Use an
https://URL so data is encrypted in transit. - Make sure your endpoint accepts JSON and responds with a
200status. - Submit a test response to the live form and check that it arrived.
The help article on using webhooks has screenshots.
Test before you write code
Paste a temporary URL from a request inspector such as webhook.site into the webhook field, submit a test response, and look at the exact JSON you receive. Then build your handler around that real payload instead of guessing field names.
A minimal receiver
If you're handling webhooks in your own app, the receiving side can be this small (Node.js with Express):
import express from 'express';
const app = express();
app.use(express.json());
app.post('/hooks/flowyform', async (req, res) => {
const submission = req.body; // the JSON you inspected in your test
console.log('New response', submission);
// validate, then save to your database or call another service
res.sendStatus(200);
});
app.listen(3000);
Respond quickly and do slow work (sending emails, calling other APIs) after you've returned the 200, for example with a job queue.
5 workflows to build with form webhooks
1. Send leads to your CRM through an automation tool
FlowyForm has no native Salesforce or HubSpot app, so the webhook is the bridge. Create a webhook trigger in Zapier, Make or n8n, paste its URL into FlowyForm, then map fields to "create or update contact" in your CRM. Add a filter step to route only qualified leads, for example by budget or company size. Note that Zapier's webhook trigger is listed for paid Zapier plans, while Make and n8n offer their own webhook triggers. For a full walkthrough, see Salesforce form builder options.
2. Write submissions straight to your database
Point the webhook at an API route in your app and insert each response into your own database. This suits product signups, beta applications and onboarding questionnaires where the answers configure the user's account.
3. Add rows to Notion or Airtable
Use an automation tool between FlowyForm and Notion or Airtable to create a database item for each response. If you only need a spreadsheet, the built-in Google Sheets integration is simpler.
4. Route requests to the right team
Use hidden fields and answers to decide where a submission goes. An IT request marked "urgent" can open a ticket and ping an on-call channel; a sales inquiry from a specific region can go to that region's rep. FlowyForm's own Slack integration posts every response to one channel, so use a webhook when you need routing rules.
5. Hand structured answers to an AI step you control
FlowyForm itself has no AI features, but structured form answers are good input for one. A webhook into n8n or Make can pass a project brief to a language model to draft a summary or first-pass proposal, and then send it to a person to review before anything goes to the client. Keeping a human review step matters: the form collects the facts, and the model only drafts.
Tips for reliable webhook integrations
- Validate what you receive. Check the form and the fields you expect before acting on a payload.
- Make handlers idempotent. If the same submission is delivered twice, your code shouldn't create two records. Use the response's ID as a key.
- Keep your endpoint available. Webhooks are sent in real time, so downtime on your side can mean missed or delayed data. Keep the Google Sheets integration on as a backup record if the data matters.
- Use HTTPS only, and don't put secrets in query strings.
- Log failures. Return a non-200 status when something goes wrong so it shows up, and alert yourself on errors.
Other integrations in FlowyForm
Alongside webhooks, every plan includes Slack (post each response to a channel), Google Sheets (each response becomes a row) and an email notification to you for each response. See integrations, or compare form builders built for spreadsheets in our Google Sheets form builder guide.
FAQ
What is a webhook in a form builder?
A setting that makes the form builder send each new submission to a URL you provide, as an HTTP POST request with JSON, as soon as the form is submitted.
Do I need Zapier to use form webhooks?
No. You can point the webhook at your own server or a serverless function. Automation tools like Zapier, Make or n8n are useful when you want to reach apps without writing code.
Are webhooks free in FlowyForm?
Yes. Webhooks, Slack and Google Sheets are included on the free plan.
How do I test a form webhook?
Paste a temporary URL from a request inspector such as webhook.site, submit a test response, and inspect the JSON. Then switch to your real endpoint.