Zapier

Estimated reading: 3 minutes

Overview

AFI sends form data and event data to Zapier through a Webhook trigger inside your Zap. Once you wire it up, every matching submission on your WordPress site becomes a fresh event in Zapier, and from there you can fan it out to thousands of supported apps.

Supported features

  • Send Data to Webhook — POSTs the mapped fields to a “Catch Hook” / “Catch Raw Hook” trigger in Zapier.
  • Mappable fields: every field exposed by your sender plugin plus all special tags ({{_date}}, {{_user_ip}}, {{_site_url}}, the full utm_* family, etc.).
  • Conditional Logic — fire the Zap only when the submission matches your rules.
  • No API key, no OAuth — only the Catch Hook URL is needed.

How to set it up

Step 1 — Create a Zap with a “Webhooks by Zapier” trigger

  1. In Zapier, click Create > Zap.
  2. For the trigger, search “Webhooks by Zapier” and choose the Catch Hook event.
  3. Zapier shows a unique Custom Webhook URL. Copy it.

Step 2 — Create the integration in AFI

  1. Go to AFI > New Integration.
  2. Pick your sender (e.g. Contact Form 7, WooCommerce, WPForms) and the form/event you want to forward.
  3. Choose Zapier as the receiver and the task Send Data to Webhook.
  4. Paste the Catch Hook URL into the Zapier Webhook URL field.
  5. Map sender fields → Zapier fields. Field names you type here are the keys that will show up in Zapier’s sample data.
  6. Optional: add Conditional Logic so only specific submissions trigger the Zap.
  7. Save.

Step 3 — Send a test and finish the Zap

  1. Submit a real form on your site (or use the sender plugin’s “Preview / Test” button).
  2. Back in Zapier, click Test trigger. Zapier should now display the payload AFI just sent.
  3. Add downstream Zap actions (Google Sheets, Slack, Gmail, HubSpot, Salesforce, etc.).
  4. Turn the Zap on.

Notes & caveats

  • Free version sends JSON POSTs with simple key/value pairs. If you need custom headers, custom HTTP methods (PUT/DELETE), or basic-auth, use the Webhook receiver (AFI Pro) instead.
  • One Zap per integration. Each AFI integration POSTs to one Catch Hook URL. To run multiple Zaps from the same form, either fan out inside Zapier (Paths / Sub-Zaps) or create multiple AFI integrations.
  • Field names are sticky. Zapier remembers the field schema from the first payload it receives. If you add a new mapped field later, you may need to click Test trigger again in Zapier to refresh the schema.
  • Empty fields. Empty values are still sent (as empty strings). Filter them in Zapier if necessary.
  • Debugging. Open AFI > Log to see the exact payload AFI tried to send and the response Zapier returned. A non-200 HTTP code points to the Zap being off, the wrong URL, or the Catch Hook having been disabled.

Related

Receiver Platforms - Previous Woodpecker.co Next - Receiver Platforms Zoho Campaigns