What is a webhook?
A webhook is a way for one system (like Fillout) to send real-time data to another system (like the 3rd party tools you use) as soon as an event occurs. Under the hood, a webhook is an HTTP callback and can be either of these requests:- GET - fetch something
- POST - create something new
Connect your form to a webhook
1
Link your Fillout form to a webhook
Click Integrate at the top of your form, then click Webhook.
Enter your Webhook URL and click Test. When you’re happy with it, click Finish setup.


2
Publish and share
You have all you need to configure a webhook when the form submits. Publish it and share the link.Test (called Test fetch in Advanced) sends a request with the webhook settings in the editor right now, even if you haven’t published them. Real submissions and Retry integration use the version of the form you last published. So after you change the webhook URL, headers or body, publish the form again. Otherwise a test can work while real submissions still send the old settings.
What the webhook sends
By default, Fillout sends the full submission to your webhook URL as JSON, in a POST request. A few things aren’t included:- Browser, operating system and network ID. These show on your form’s Results page but aren’t sent to the webhook.
- The edit submission link. To get it, request the submission from the Fillout REST API with the
includeEditLinkquery parameter. - When the respondent started the form, the email from a login page, and enriched company details. These aren’t in the default payload either.
- Questions on pages the respondent didn’t reach. If your form skips pages with logic, only the questions the respondent saw are sent.
submissionTime in the payload is the time the webhook was sent. For a retried webhook, that’s the time of the retry, not when the form was submitted.
To choose exactly what gets sent, use the Advanced options below.
Available webhook options
Switch from Simple to Advanced at the top to set up your webhook with any of the parameters or arguments you need.
Nested JSON isn’t supported
Each row in Body becomes one top-level field in the JSON Fillout sends. The webhook can’t build nested JSON, like an object inside another object or a list of objects:- A key with a dot, like person.firstName, is sent as one field with that exact name.
- JSON you type into a value is sent as a piece of text, not as JSON.
- Choose whether Fillout sends a POST or a GET request to your URL.
- Body only shows when the HTTP method is POST. Most of the time, services like Zapier and Make accept either GET or POST, so you can send information in the body of the message if you prefer.
- If using fields in the body of the message, make sure to process these correctly in Zapier/Make to make sure that they’re coming in the body and not the URL.
- These get added to the URL at the end.
- The left-hand side is the key, and the right-hand side is the value from your form or from anything else you can reference in Fillout.
- For example, if you add, on the left-hand side, source, and then on the right-hand side, reference the field or question about this in your form, then your webhook will send:
- https://hooks.zapier.com/hooks/catch/12475312/abc/?source=answer to the short answer
- So if someone answered Facebook in the form, you will send: https://hooks.zapier.com/hooks/catch/12475312/abc/?source=facebook
- Most users will not need to use this section. This is typically if you have an advanced webhook setup which requires sending extra headers.
- The most typical use case for headers is if your endpoint needs verification and you have a special key to send. For example, enter Authorization as the key and Bearer followed by your secret token as the value.
- Fillout sends Content-Type and Accept headers set to application/json unless you add your own.
- Similar to headers, most users will not need to send any here.
Common webhook errors
These errors show next to the submission on your form’s Results page. The same errors can come up in a webhook step in a workflow.- Invalid webhook URL - Fillout can’t send to this address. Check that:
- The URL starts with https://. Newer forms don’t accept http:// URLs.
- The address is on the public internet. Fillout doesn’t send to private or local network addresses, like localhost or an internal IP address, even if they worked before.
- The domain exists and is spelled correctly.
- The destination server attempted to redirect the request to another location - Fillout doesn’t follow redirects. Use the final URL your service gives you instead.
- The destination server took too long to respond to the webhook request - your server didn’t accept the connection within about 10 seconds, or didn’t respond within 60 seconds. Check that it’s online, then retry.
- Request failed with status followed by a number and a message - your server received the webhook but answered with an error. The number is the status code it sent back, and the message is what it said. Check the endpoint’s settings, or ask the service you’re sending to what the error means.
Retry a failed webhook
When a webhook fails, your form’s Results page shows an error next to that submission. Open the submission to read the error message.
Webhook or Make’s Fillout app
If you use Make, you can receive submissions in two ways:- A Webhook integration sent to Make’s Custom webhook module. Fillout sends the full payload described above, with each question’s name. If Make doesn’t accept it, the error shows in your form’s Results and in the integration error email.
- Make’s Fillout app (Watch new responses). You connect your Fillout account in Make, and it needs edit access to the form. It’s also instant, but each answer is labeled with the question’s ID instead of its name, and it doesn’t include quiz scores, payments, documents or the edit link. If a delivery fails, nothing shows in Results and no error email is sent.
Webhooks on scheduling forms
A webhook on a scheduling form sends these fields by default:fullNameemailphone(if available)timezoneeventStartTimeeventEndTimeeventIdeventUrlrescheduleOrCancelUrlscheduledUserEmailscheduledUserName
A webhook added under Integrate only runs when the form is submitted, which is the original booking. To send a webhook when an event is canceled or rescheduled, use a workflow.
FAQs
Can I send a record ID created by another integration to my webhook?
Can I send a record ID created by another integration to my webhook?
No. If your form also creates a record through a native integration, such as a new Airtable record, that record’s ID can’t be passed to your webhook. Both run when the form is submitted, so the ID doesn’t exist yet when the webhook is sent.The same applies in general: a record ID created on submission can’t be returned to the form or used by other integrations that run on submission.
Does the webhook fire for unpaid submissions on payment forms?
Does the webhook fire for unpaid submissions on payment forms?
No. A form with a payment page can’t be submitted until Stripe confirms the payment, so abandoned or declined payments don’t trigger the webhook. Some submissions still come through without a completed charge, like $0 checkouts, free trials, and US bank account payments that are still processing. See when a submission is recorded for the exceptions and how to check the payment status.
Why don't webhooks created with the API show in my dashboard?
Why don't webhooks created with the API show in my dashboard?
Webhooks created through the Fillout API don’t appear in the Fillout dashboard. To remove one, use the API’s remove a webhook endpoint.
Related articles
Automate with Zapier
Connect your Fillout form to hundreds of apps.
Populate dropdowns with a webhook
Load options from a REST API.