Adwix AtlasPlatform

Zapier · Make · Pabbly

One webhook step connects thousands of apps to your lead board. The pattern is identical everywhere: trigger on a new form entry, then POST JSON to your Atlas webhook URL.

Your webhook URL (with its secret token) lives in Atlas → Settings → Integrations → Lead Webhook — open it there and use the copy button. Docs pages always show {token} as a placeholder; your real URL never appears on this public site.

Zapier#

1. Trigger: your form app (Typeform, Google Forms, Facebook Lead Ads, JotForm, …) → “New entry”.
2. Action: Webhooks by Zapier → Custom Request (or POST). Method POST, URL = your webhook URL, Data Pass-Through off, data = the JSON below with your trigger's fields inserted, and a headerContent-Type: application/json.
3. Test — the sample lead appears on your board within seconds.

Make (Integromat)#

1. Trigger module:your form app's “Watch responses”.
2. Action module: HTTP → Make a request. Method POST, URL = your webhook URL, Body type Raw, Content type JSON (application/json), request content = the JSON below with mapped fields.

Pabbly Connect#

1. Trigger: your form app.
2. Action: API by Pabbly → POST. URL = your webhook URL, payload type JSON, then add the fields below as key/value rows.

The JSON to send (all three)#

Request body template
{
  "name": "{{name from your trigger}}",
  "phone": "{{phone from your trigger}}",
  "email": "{{email from your trigger}}",
  "destination": "{{destination, if your form asks}}",
  "message": "{{message / comments}}",
  "source": "website"
}
Only oneof name / phone / email is strictly required — map whatever your form collects. Unmapped extras are welcome too: anything Atlas doesn't recognise is preserved in the lead's notes, so map generously rather than dropping answers.
Using a connector for Meta Lead Ads? That works — but the native integration is better: instant sync without a connector subscription, automatic form answers in notes, and ad-level attribution. See Meta Lead Ads.