AFI
Webhook
The Webhook integration sends form data from your WordPress site to any external URL. This is the most flexible integration in AFI, allowing you to connect to any system that accepts HTTP requests, including Make, Zapier, n8n, Pipedream, custom APIs, and more.
What you’ll need
- An active Webhook account.
- The Advanced Form Integration plugin installed and activated.
Create the integration
- Go to AFI → Add New.
- Give the integration a name, for example
Form to Webhook. - Under Trigger, pick the form plugin and the specific form.
- Under Action → Platform, select Webhook.
- In Task, choose Send Data to Webhook.
- Pick the saved account.
- Map your form fields onto the fields listed below.
- Optional: open Conditional Logic to limit which submissions are sent.
- Click Save Integration.
Tasks supported
Send Data to Webhook
Sends the mapped form fields to the configured webhook URL as a JSON or form-encoded POST request. In the free version, the request is sent as a JSON POST to the URL specified.
| Field | Field key | Notes |
|---|---|---|
| Webhook URL | webhook_url |
The destination URL to send data to |
| HTTP Method | webhook_method |
POST (default), GET, PUT, PATCH, DELETE |
| Content Type | content_type |
JSON (default) or Form-Encoded |
| Custom Headers | headers |
Key:value pairs, one per line |
| Body fields | mapped fields |
Map form fields to JSON keys or form parameters |
Pro features
The Pro integration extends the free version with additional capabilities. Pro uses the same Webhook connection.
Feature comparison
| Feature | Free | Pro |
|---|---|---|
| Send data to webhook (POST JSON) | ✅ | ✅ |
| Body field mapping | ✅ | ✅ |
| HTTP method selection | No | ✅ |
| Custom headers | No | ✅ |
| Content type (JSON / Form-Encoded) | No | ✅ |
| Inbound webhook triggers | No | ✅ |
Use cases
- Send form data to Make (Integromat), Zapier, n8n, or Pipedream for further processing.
- Sync submissions to a custom API endpoint or microservice.
- Trigger automations in platforms that AFI does not have a native integration for.
- Log submissions to a monitoring service like Datadog or Loggly.
Authentication patterns
Most webhook destinations accept one of these authentication patterns, configured in the Custom Headers field:
- Bearer token:
Authorization: Bearer your_token_here - API key header:
X-API-Key: your_key_here - Basic auth:
Authorization: Basic base64encoded_string - Query parameter: append the token to the URL:
https://example.com/webhook?token=your_token
Conditional logic example
Only send data to Webhook when specific conditions are met. For example, add a condition on a form field to control which submissions are forwarded.
Troubleshooting
Nothing arrives in Webhook
Open AFI → Log and find the most recent entry. AFI stores the request URL, body, and raw response.
API credentials rejected
Verify your credentials in your Webhook account settings. If they were regenerated, update them in AFI → Settings → Webhook.