Webhook Delivery

Eigenn does not offer a general outbound webhook subscription API now. Set up event delivery through a supported marketplace automation app such as Zapier, n8n, or Make.

Before You Start

• Choose the Eigenn team that owns the events.
• Create a dedicated destination for this integration.
• Use a public HTTPS URL.
• Decide which supported event names the destination will accept.
• Make downstream effects safe to repeat.

The Zapier and n8n connection flows reject private, loopback, local, and cloud-metadata destinations.

1. Choose an Automation App

1. Open Apps.
2. Find Zapier, n8n, or Make.
3. Examine its availability badge.
4. Open the app details and confirm the listed events.
5. Install or set up the app for the current team.

Current app event sets include:

• Zapier: invoice.created, invoice.paid, payment.received, customer.updated
• n8n: invoice.created, invoice.paid, payment.received
• Make: invoice.created, invoice.paid, customer.updated

Do not subscribe to an event merely because another app lists it.

2. Check the Receiver

The current Zapier and n8n envelope is:

{
  "type": "invoice.created",
  "organizationId": "00000000-0000-0000-0000-000000000000",
  "occurredAt": "2026-07-11T14:30:00.000Z",
  "data": {}
}

At the receiver:

1. Accept only POST with JSON.
2. Check the top-level fields.
3. Accept only the event names that your workflow supports.
4. Confirm that organizationId matches the expected team.
5. Check the event-specific data before you use it.

The envelope does not promise a universal event ID.

3. Keep the HTTP Response Fast

Persist an accepted event. Return a 2xx response before you start slow downstream work. The current Zapier and n8n connections treat a redirect or any non-2xx response as a failed delivery.

Use a permanent queue for:

• external API calls
• email or messages
• document generation
• finance record updates
• reconciliation that takes a long time

4. Handle Retries Safely

Zapier and n8n now make up to three delivery tries with a 10-second timeout for each try.

These values are app-specific and are not a universal Eigenn webhook guarantee. Make does not publish the same retry behavior.

Before you do a write:

• look for a stable business identifier in data
• combine it with the event type when applicable
• enforce uniqueness at the destination
• return the prior successful result for a repeated logical event

Do not use occurredAt alone as a deduplication key.

5. Apply an Explicit Trust Model

Eigenn does not publish a universal outbound webhook signature header or shared signing-secret scheme for marketplace automation deliveries.

Protect the receiver with these steps:

• use the automation platform's access controls when available
• use an unshared, purpose-specific URL
• check organizationId and event contents
• limit the receiver to a narrow action
• reject unexpected fields or values where practical
• keep high-risk customer, cash, and ledger changes behind one more review

Do not claim that Eigenn confirmed a request unless the specific app documents and supplies a verification method.

6. Test Failure Modes

Test each of these before you turn on production effects:

1. A valid event returns 2xx.
2. An unsupported event returns 4xx.
3. Malformed JSON returns 4xx.
4. A repeated event does not duplicate the business effect.
5. A receiver timeout produces a retry.
6. A receiver 500 produces a retry.
7. The receiver rejects an organizationId mismatch.
8. A queue outage stops the acknowledgement.

After the tests, examine the installed app's activity and the destination logs.

Current Limit

The public REST API has no create, list, update, or delete endpoint for arbitrary outbound webhook subscriptions. The provider callback endpoints in OpenAPI are for supported providers that call Eigenn. Do not use them as custom delivery targets.

Related Pages

• Webhooks
• Webhooks API Status
• Marketplace Integrations