Skip to main content

How to Connect a Form to a Webhook

Form webhooks send submission data from a Form element to an external HTTPS endpoint in real time — alongside storage in Leads.

Configure the webhook on the form in Page Builder. Use Form webhook delivery to monitor and resend — not to add the URL the first time.

Before You Start​

Make sure you have:

  • A page with a Form element (or follow How to add a form to a page first).
  • An HTTPS endpoint ready to accept POST payloads.
  • Permission to publish the page after saving webhook settings.
  • Optional: Webhook API keys if your receiver validates Atomicat signatures.

See Form element — webhook settings and Form webhook delivery.

Step 1: Open the Form in Page Builder​

  1. Go to Pages and click Edit on the target page.
  2. Click the Form element on the canvas.
  3. Open the edit drawer on the right.

Step 2: Add Webhook Settings​

In the form drawer, find Webhook configuration (when available on your workspace):

SettingWhat it does
Webhook nameInternal label for your team and delivery logs.
Webhook URLHTTPS endpoint that receives submission JSON.
DescriptionOptional note about CRM/automation destination.
Send abandoned leadsSends partial data when visitor starts but does not finish.

Fill name and URL before testing. Use descriptive names (Meta lead – VSL page) so delivery screens stay searchable.

Step 3: Optional — Abandoned Leads​

Enable Send abandoned leads only if:

  • Your follow-up process handles incomplete submissions, and
  • Compliance rules allow partial data export.

Abandoned traffic can increase webhook volume — confirm your endpoint dedupes or tags partial leads.

Step 4: Save and Publish the Page​

  1. Click Save in Page Builder.
  2. Publish the page to the live site/domain. See Publish a page.

Webhook configuration on a draft-only page does not send production traffic to your endpoint.

Step 5: Test on the Published URL​

  1. Open the live HTTPS URL in incognito.
  2. Submit the form with realistic test data (all required fields).
  3. Confirm:
    • Lead appears in Form leads
    • Your endpoint logged the payload with expected fields
  4. Test validation failures (empty required fields) to ensure bad submits are not sent incorrectly.

Repeat with abandoned behavior if enabled (partial fill, leave page — behavior depends on product rules).

Step 6: Monitor and Resend Deliveries​

  1. Open Form leads → Webhooks header shortcut (or navigate to Form webhook delivery).
  2. Review summary cards: total, successful, failed, success rate.
  3. Filter by status, form, or search URL text.
  4. Click View details on a row for payload and response body.
  5. Use Resend on failed rows when the destination was temporarily down.

You cannot edit the webhook URL on this screen — return to Form element settings in Page Builder to change URL, then republish.

Optional: Webhook History on the Form​

Some workspaces expose Webhook history on the Form element drawer (delivery status, attempts, retry state). Use it for quick checks while editing the same page.

Best Practices​

  • Test every field mapping implicitly — your endpoint should expect Atomicat field keys.
  • Use API keys on the receiver when security policy requires it.
  • Republish after URL changes before running paid traffic again.
  • Keep one webhook per destination when payloads differ; use clear names.

Troubleshooting​

ProblemWhat to try
No webhook receivedPage published? Test live URL not builder preview.
4xx/5xx on receiverInspect delivery details; validate auth and schema.
Duplicate payloadsAbandoned + submit may fire separately — handle server-side.
URL change not liveSave form, republish page, clear CDN/cache if applicable.
Cannot find webhook settingsPlan/workspace may hide webhooks — check Form element reference.

Outcome​

Your form sends submissions to your HTTPS endpoint on the live page while Atomicat stores leads in Form leads — with monitoring and resend available in Form webhook delivery.

FAQ​

Where do I set the webhook URL?

On the Form element in Page Builder — not on the Form webhook delivery monitoring screen.

Do submissions still appear in Leads?

Yes when the form is configured correctly. Webhooks are an additional real-time delivery channel.

Must I publish after changing the webhook URL?

Yes. Live visitors use the published page configuration.

HTTP vs HTTPS?

Use HTTPS endpoints your stack trusts. Follow validation messages in the form drawer.

Can one form have multiple webhooks?

Depends on workspace UI — if only one row is shown, use middleware to fan out or contact support for multi-destination patterns.