Zapier Integration

Send every form submission to one or more Zapier catch hooks, so you can trigger Zaps — anything Zapier connects to — from your Contactum forms. Requires Contactum Pro with the Zapier module enabled.

Like n8n, Zapier has no global connection screen — everything is configured per form, and you can send to multiple Zaps from the same form.

---

Requirements #

• Contactum Pro, with the Zapier module active (Contactum → Modules)
• A Zapier account with a Zap already set up using a Webhooks by Zapier → Catch Hook trigger, so you have a URL to send to

---

1. Enable Zapier on a Specific Form #

1. Open the form in the builder.
2. Go to Form Settings → Zapier.

---

2. Add a Zap #

Click Add Zap and fill in:

Field	Required	Description
Zap name	No	A label for your own reference, e.g. “Send to Slack” — not sent to Zapier
URL	Yes	Your Zap’s catch hook URL, e.g. https://hooks.zapier.com/hooks/catch/...

You can add as many Zaps as you like with Add Zap — every one of them receives the same submission. Use the × icon to remove a row.

Click Send Test next to a Zap to fire a one-off test payload to that URL immediately, without waiting for a real form submission.

---

3. How It Works #

When a visitor submits the form:

1. Contactum checks the form has at least one Zap configured. If there are none, nothing happens.
2. For each configured Zap, Contactum sends the full entry as JSON:

{
  "entry_id": 42,
  "form_id": 7,
  "form_name": "Contact Us",
  "submitted_at": "2026-05-22 10:00:00",
  "fields": {
    "Name": "Jane Doe",
    "Email": "jane@example.com",
    "Message": "Hello!"
  }
}

The fields object uses each field’s label as the key (not its internal name/slug).

1. The request is sent in the background — Contactum doesn’t wait for Zapier to respond before finishing the visitor’s submission, so this never slows down or blocks form submission.

Because delivery isn’t confirmed at submission time, every dispatch is recorded in Contactum’s API Log as “pending, delivery not confirmed.” You can check there to see what was actually sent, and retry a specific submission’s delivery — which does wait for a real response and updates the log to success or failed accordingly.

Note: the payload sent by Send Test is a synthetic example and won’t exactly match your form’s real field labels — use it to confirm the URL works, not to preview real data shape.

---

Troubleshooting #

My Zap isn’t triggering #

1. Confirm at least one Zap row has a URL filled in and the form was saved.
2. Use Send Test on that row to check for an immediate pass/fail.
3. Confirm the Zap is actually turned on in Zapier — a paused/off Zap won’t fire even if the webhook was received.
4. Check the API Log (Contactum → Tools → API Log, if available) — every real dispatch is recorded there.

The log shows “pending” and never updates #

• This just means delivery wasn’t confirmed at submission time (by design, so it never slows down your visitors). Use the Retry button on that log entry to resend it and get a confirmed result.

I need to send a custom auth header #

• Zapier catch hooks are secured by the uniqueness of the URL itself and don’t support custom headers here. If you need header-based auth, consider the n8n module instead, which supports one custom header per feed.

---

Notes #

• Requires Contactum Pro with the Zapier module active — not available in the free plugin.
• No global settings — this integration is entirely configured per form, and supports multiple Zaps per form (unlike the free plugin’s single-URL Webhook feature).
• Storage: Zaps are stored directly on the form (in its settings), not in a separate global option.
• A failed or unconfirmed delivery never blocks the form — the visitor’s experience is unaffected either way.