WordPress & site builders
WordPress form plugins all speak 'webhook', but each one formats the request differently — here is what reliably works with Atlas, from most to least robust.
{token} as a placeholder; your real URL never appears on this public site.The one requirement#
Atlas expects JSON (Content-Type: application/json). Any plugin or builder that can POST JSON to a URL works directly. If a plugin only sends form-encoded data, put a connector in between or use the snippet below — don't fight the plugin.
Option A — a form plugin with JSON webhooks#
Plugins like WPForms (Webhooks addon), Fluent Forms, Gravity Forms (Webhooks) and Forminator let you add a webhook action per form. Configure: request URL = your webhook URL, method =POST, format = JSON, then map your form fields to the keys from the field reference —name, phone, email,destination, message. Add a static fieldsource = website.
Option B — through Zapier / Make / Pabbly#
Universal and format-proof: your form plugin triggers the connector (all major WP form plugins have native triggers there), and the connector's webhook step POSTs clean JSON to Atlas. Follow the connector recipes — this also works for Elementor forms, whose built-in webhook action does not send JSON.
Option C — a tiny script (Contact Form 7 example)#
If you'd rather not add plugins, hook the form's submit event and forward the fields yourself. Example for Contact Form 7, pasted via your theme or a code-snippets plugin:
<script>
document.addEventListener('wpcf7mailsent', function (event) {
var fields = {}
event.detail.inputs.forEach(function (i) { fields[i.name] = i.value })
fields.source = 'website'
fetch('https://adwixatlas.com/api/webhooks/leads/{token}', {
method: 'POST',
headers: { 'Content-Type': 'application/json' },
body: JSON.stringify(fields),
})
}, false)
</script>