A webhook is an HTTP POST request sent automatically to a specified URL when a particular event occurs, enabling real-time data transfer between services without polling.
Webhooks are the backbone of real-time integrations between web services. Instead of your application repeatedly checking (polling) another service for updates, the other service proactively sends you data the moment something happens.
In the context of form submissions, a webhook fires every time someone fills out your form. The form backend packages the submission data as a JSON payload and sends an HTTP POST request to a URL you configure. Your server receives this payload and can process it however you want — add the data to a CRM, trigger an email sequence, create a task in a project management tool, or store it in your own database.
Webhooks follow a simple pattern: event occurs, data is packaged, POST request is sent. The receiving server should respond with a 200 status code to acknowledge receipt. If the request fails, most webhook senders implement retry logic — they'll attempt delivery again after increasing intervals.
FormsList's webhook integration supports custom headers, retry with exponential backoff, and payload inspection in the dashboard. You can send form submissions to any HTTP endpoint — your own API, a serverless function, or a third-party service that accepts webhooks.
When a lead capture form is submitted, a webhook sends the data to your CRM's API endpoint, automatically creating a new contact record without manual entry.
A webhook sends form submission data to a Slack incoming webhook URL, posting a formatted message to a team channel every time someone fills out a form.
A webhook delivers form data to an AWS Lambda function that validates the submission, enriches it with third-party data, and stores it in DynamoDB.
Set up your form backend in under a minute. No server required, no complex configuration — just a simple endpoint for your forms.