Webhook Delivery

Eigenn does not currently offer a general outbound webhook subscription API. Configure 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.

Private, loopback, local, and cloud-metadata destinations are rejected by the Zapier and n8n connection flows.

1. Choose an Automation App

1. Open Apps.
2. Find Zapier, n8n, or Make.
3. Review its availability badge.
4. Open the app details and confirm the listed events.
5. Install or configure 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. Validate 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. require POST with JSON
2. validate the top-level fields
3. allow only the event names your workflow supports
4. confirm organizationId matches the expected team
5. validate the event-specific data before using it

The envelope does not promise a universal event ID.

3. Keep the HTTP Response Fast

Persist an accepted event and return a 2xx response before running slow downstream work. A redirect or any non-2xx response is treated as a failed delivery in the current Zapier and n8n connections.

Use a durable queue for:

• external API calls
• email or messaging
• document generation
• finance record updates
• long-running reconciliation

4. Handle Retries Safely

Zapier and n8n currently make up to three delivery attempts with a 10-second timeout per attempt.

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

Before performing a write:

• look for a stable business identifier in data
• combine it with the event type when appropriate
• 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 by:

• using the automation platform's access controls when available
• using an unshared, purpose-specific URL
• validating organizationId and event contents
• limiting the receiver to a narrow action
• rejecting unexpected fields or values where practical
• keeping high-risk customer, cash, and ledger changes behind an additional review

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

6. Test Failure Modes

Test each of these before enabling production effects:

1. valid event returns 2xx
2. unsupported event returns 4xx
3. malformed JSON returns 4xx
4. repeated event does not duplicate the business effect
5. receiver timeout produces a retry
6. receiver 500 produces a retry
7. organizationId mismatch is rejected
8. queue outage prevents acknowledgement

After testing, review 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. Provider callback endpoints shown in OpenAPI are for supported providers calling Eigenn and should not be used as custom delivery targets.

Related Pages

• Webhooks
• Webhooks API Status
• Marketplace Integrations