Automate with Zapier, Make and n8n

Fuzegenai sends campaign events to Zapier, Make and n8n through a webhook URL you paste into the integration. To act on Fuzegenai from your automation, for example to add a lead to a campaign, call the REST API with an API key.

The events you can send

All three integrations offer the same two events:

There is no separate event for replies, opens, clicks or booked meetings in these integrations.

Connect Zapier

1. In Zapier, create a Zap whose trigger is Webhooks by Zapier with the Catch Hook event. Copy the hook URL. It starts with https://hooks.zapier.com/.
2. In Fuzegenai, open Integrations from the sidebar, find Zapier and click Connect.
3. Paste the URL into Webhook URL.
4. Under Send webhook data when, tick the events you want.
5. Click Connect.

Fuzegenai posts a test payload to the hook as part of connecting, so Zapier has a sample to map fields from. If the test fails, the connection is not saved.

Connect Make

1. In your Make scenario, add a Custom Webhook trigger and copy its URL. It looks like https://hook.us1.make.com/....
2. In Fuzegenai, find Make.com on the Integrations page and click Connect.
3. Paste the URL into Webhook URL, tick the events, and click Connect.

Connect n8n

1. In n8n, create an API key under Settings → API. The n8n Public API must be enabled.
2. In Fuzegenai, find n8n and click Connect.
3. Fill in Instance URL, the root URL of your n8n instance, and API key.
4. To receive events, add a Webhook trigger to an n8n workflow, copy its URL into Workflow webhook URL, and tick the events under Send workflow data when. The URL must be a public HTTPS address.
5. Click Connect Instance.

Without a workflow webhook URL, the n8n connection only lets you see your workflows and their execution history.

What a payload looks like

Every event is a JSON POST. This is sequence.ran:

{
  "fuzgen_event": "sequence.ran",
  "eventType": "sequence.ran",
  "eventVersion": "v1",
  "organizationId": 42,
  "occurredAt": "2026-09-20T09:15:00.000Z",
  "timestamp": "2026-09-20T09:15:00.000Z",
  "campaign": { "id": 123, "name": "Q4 outbound" },
  "sequence": { "stepId": 7, "stepRank": 1, "stepName": "Step 1" },
  "delivery": {
    "queueId": 9876,
    "emailAccountId": 5,
    "recipient": "jane@example.com",
    "subject": "Quick question",
    "messageId": "<abc@mail.example.com>"
  },
  "lead": { "id": 555, "email": "jane@example.com" }
}

campaign.status_changed carries the same envelope with campaign.id, campaign.name, campaign.previousStatus and campaign.status, plus actor.userId when a person made the change. Deliveries to n8n also include eventId, deliveryId and idempotencyKey, so a workflow can ignore a duplicate.

Each event is posted once. There is no automatic retry, so make your hook respond quickly and do slow work afterwards. If a delivery fails, the integration's card on the Integrations page shows a status dot; hover it to read the last error.

Acting on Fuzegenai from your automation

Use an HTTP step (Webhooks by Zapier, Make's HTTP module, or n8n's HTTP Request node) with an API key in the Authorization: Bearer header. With a Read & write key you can add leads to a campaign or change a campaign's status. API keys need the Professional plan or above. See API keys and the REST API for the endpoints, and pricing for plans.

To remove a connection, click Manage on the integration's card and delete or disconnect it there.