n8n Integration

Send every form submission to one or more n8n workflow webhooks, so you can build custom automations — Slack alerts, CRM updates, data syncing, anything n8n can do — triggered by your Contactum forms. Requires Contactum Pro with the n8n module enabled.

Unlike most integrations, n8n has no global connection screen — everything is configured per form, and you can send to multiple workflows from the same form.

---

Requirements #

• Contactum Pro, with the n8n module active (Contactum → Modules)
• An n8n instance (self-hosted or cloud) with a Webhook node already set up in a workflow, so you have a URL to send to

---

1. Enable n8n on a Specific Form #

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

---

2. Add a Workflow #

Click Add Workflow and fill in:

Field	Required	Description
Workflow name	No	A label for your own reference, e.g. “Slack notify” — not sent to n8n
URL	Yes	Your n8n Webhook node’s URL
Header name	No	An optional custom HTTP header, e.g. Authorization — useful if your n8n Webhook node is protected with Header Auth
Header value	No	The value for that header

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

Click Send Test next to a workflow to fire a one-off test payload to that URL immediately, without waiting for a real form submission. You’ll see the actual HTTP result (success or the error returned).

---

3. How It Works #

When a visitor submits the form:

1. Contactum checks the form has at least one workflow configured. If there are none, nothing happens.
2. For each configured workflow, 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. If you set a custom header name and value for that workflow, it’s included on the request.
2. The request is sent in the background — Contactum doesn’t wait for n8n 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 (fixed sample name/email/message) and won’t exactly match your form’s real field labels — use it to confirm the URL and headers work, not to preview real data shape.

---

Troubleshooting #

My workflow isn’t receiving anything #

1. Confirm at least one workflow 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. Check the API Log (Contactum → Tools → API Log, if available) — every real dispatch is recorded there, including ones n8n silently rejected.
4. If your n8n Webhook node uses Header Auth, confirm the header name and value here match exactly what n8n expects.

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.

---

Notes #

• Requires Contactum Pro with the n8n module active — not available in the free plugin.
• No global settings — this integration is entirely configured per form, and supports multiple workflows per form (unlike the free plugin’s single-URL Webhook feature).
• Auth: optional custom HTTP header per workflow — there’s no account-level connection to n8n itself.
• Storage: workflows 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.
• Header values are stored so they can be resent automatically if you use the API Log’s Retry button — avoid pasting highly sensitive long-lived secrets here if that’s a concern for your setup.