Webhooks

Send each completed response as JSON to your backend, CRM or automation tool with a webhook. Responses stay saved in Floov if delivery fails.

Form integrations directory grouped by developer, analytics, data, and notifications

Set Up a Webhook

  1. Open Settings > Integrations > Webhook in the form editor.
  2. Paste your Webhook URL. A valid URL turns delivery on; clear it to turn delivery off.
  3. Publish the form. For an already published form, close the panel and choose Apply to live form to update integrations without publishing other draft changes.

Use a public https:// endpoint. Floov rejects http://, localhost, private addresses and URLs containing login credentials. See Publishing Forms before applying settings to a live form.

Integrations settings showing the webhook toggle and URL input

Understand the Payload

Floov sends a POST request with an application/json body. These IDs, field keys and answers are examples:

{
  "form_response_id": 123,
  "published_form_id": 45,
  "submitted_at": "2026-11-20T09:30:00+00:00",
  "responses": {
    "email_question": {
      "name": "Email",
      "type": "EmailInput",
      "value": "[email protected]"
    },
    "consent_question": {
      "name": "Keep me updated",
      "type": "CheckboxInput",
      "value": true
    }
  }
}

form_response_id identifies the saved response; published_form_id identifies its form version. submitted_at is the response’s saved timestamp in ISO 8601 format. Each entry in responses has a name, type and value. Map by field ID, as question labels can repeat.

Values can be text, numbers, booleans, lists, objects or null, depending on the field. Hidden fields use the same structure. Calculated results are included even when not displayed, as decimal strings or null for no result. Publish new fields and calculations before using their values.

Files and signatures use download links that expire after six days. Retrieve them promptly; anyone holding a valid link can open it until expiry.

Prepare Your Endpoint

Accept JSON and return a 2xx response within 10 seconds. Process longer tasks in the background. Redirects are not followed, so a 3xx response fails. Use form_response_id to avoid processing a repeated delivery twice.

The editor webhook has no settings for custom authorization headers or request signing. If your destination requires them, receive the request in a service you control and forward it with the required authentication. Native Make and Zapier connections use their own payload format.

Test and Troubleshoot

Complete a new response through the public form, then check your endpoint’s JSON and the form’s Deliveries page. Preview does not send webhooks. Check the recorded error if nothing arrives; failed deliveries are not automatically retried. Editing a saved response does not send another webhook.

In Deliveries, Webhook is the editor’s configured URL. Make and Zapier identify recognized connected apps. API webhook is a subscription whose app could not be identified; check its status to see whether it succeeded.

A slow or failed webhook does not block email notifications or other integrations. Deliveries can arrive out of order.

Related Guides

Use the native Make, Zapier, Slack, Discord, Google Sheets, Airtable or Notion connection when it fits your destination. Slack’s incoming webhook needs a different JSON format; use the native integration or transform the payload before forwarding it.

See Email Notifications, Viewing Responses, Exporting Data or Analytics & Tracking for related tasks.