HTTP Webhook
Send submission data to any URL the moment a form is submitted. Use this to trigger backend workflows, update a CRM, write to a database, or connect to services not natively supported.
Setup
- In Formboost, open your form → Integrations tab → Webhook
- Enter your endpoint URL
- Choose the HTTP method:
POST,GET,PUT, orPATCH - Optionally add custom headers (JSON format — see below)
- Save
Custom Headers
Add headers as a JSON object. Useful for authentication or content-type requirements:
1{
2 "Authorization": "Bearer YOUR_TOKEN",
3 "X-API-Key": "YOUR_API_KEY"
4}Example Payload
Formboost sends submission data as a JSON body (for POST, PUT, PATCH) or as query parameters (for GET):
1{
2 "name": "John Doe",
3 "email": "[email protected]",
4 "message": "Hello, I'd like to learn more.",
5 "fb_formId": "ep_abc123",
6 "fb_formName": "My Contact Form",
7 "fb_dashboardUrl": "https://formboost.app/dashboard/submissions/sub_xyz789"
8}Reserved Keys
The following keys are always included automatically. Avoid using these names in your form fields to prevent conflicts:
| Key | Value |
|---|---|
fb_formId | The unique ID of the form endpoint |
fb_formName | The display name of the form |
fb_dashboardUrl | Direct link to the submission in your dashboard |
Testing
Use a service like webhook.site to inspect the exact payload Formboost sends before wiring it to your production endpoint:
- Open webhook.site and copy the unique URL
- Paste it into the webhook URL field in Formboost and save
- Submit your form (or click Send Test in the Integrations tab)
- Inspect the full request — headers, body, and all field values — on webhook.site
Retry Behavior
If your endpoint returns a non-2xx status code or times out, Formboost retries the delivery up to 3 times with exponential backoff. After all retries fail, the event is logged in your dashboard under Integrations → Delivery Logs.
Troubleshooting
| Problem | Fix |
|---|---|
| No request received | Confirm the URL is publicly accessible (not localhost) |
| 401 / 403 errors | Check the Authorization header value in your custom headers |
| Payload missing fields | Ensure field name attributes in your HTML form are set correctly |
| Timeout | Your endpoint must respond within 10 seconds; offload heavy work asynchronously |
| Reserved key conflict | Rename your form field to avoid fb_formId, fb_formName, or fb_dashboardUrl |
Notes
- Webhook URLs must be publicly accessible. Local development servers (
localhost,127.0.0.1) will not work. - Formboost sends
Content-Type: application/jsonfor all non-GET requests. - Delivery logs showing all attempts and response codes are available in your dashboard under Integrations → Delivery Logs.