Webhooks
Form backend with webhook forwarding built in.
Every submission can trigger a JSON webhook to your endpoint. Available on Starter plans and above. No server code or integration platform required.
How it works
Three steps to production forms.
Enable webhooks
Add a webhook URL in your form settings or as a hidden form field.
Submit a form
When a submission is accepted, FormsFort queues both email and webhook delivery.
Handle the payload
Receive a JSON payload with the submitted fields at your endpoint.
Setup
Form with webhook field
<form action="https://api.formsfort.dev/submit" method="POST">
<input type="hidden" name="access_key" value="YOUR_ACCESS_KEY" />
<input type="hidden" name="webhook" value="https://your-api.com/webhook" />
<input type="text" name="name" required />
<input type="email" name="email" required />
<textarea name="message" required></textarea>
<button type="submit">Send</button>
</form>Migration
Migration checklist.
Move an existing form in minutes without rebuilding markup.
Create a FormsFort form on the Starter plan or above.
Add a webhook hidden field to your form markup.
Set the webhook value to your HTTPS endpoint URL.
Ensure your endpoint accepts POST requests with JSON payloads.
Send a test submission and inspect the webhook delivery.
Add retries and idempotency handling on your endpoint.
FAQ
Common questions.
What does the webhook payload look like?
A JSON object containing the submitted field values, submission metadata, and a unique request id.
Can I send webhooks to Zapier or Make?
Yes. Use a webhook trigger URL from Zapier, Make, or any integration platform as the webhook value.
Is there a retry policy?
Webhook delivery is queued and retried on transient failures. Check your dashboard for delivery status.
Can I have multiple webhooks per form?
Currently one webhook URL per form. Contact us if you need multiple endpoints.
Stop managing form servers.
Create a production form endpoint, migrate your first form free, and scale when you are ready.