n8n workflows
Install the official trigger, subscribe to events and recover webhook delivery safely.
The official community package is n8n-nodes-factuarea, version 0.1.2 in the September 2026 release baseline. It requires Node.js 22+. It provides a Factuarea credential and an event trigger; use n8n’s HTTP Request node for other REST operations.
Install and subscribe
Install the package through Community Nodes in your n8n instance. Create a Factuarea credential with an API key containing events:read, webhooks:read, webhooks:write and webhooks:delete. Add the Factuarea Trigger, select the credential and choose event types from the catalog. Activating the workflow creates its webhook endpoint; deactivating it removes the endpoint owned by that trigger.
Expose the n8n webhook through public HTTPS. Private addresses and local-only destinations are rejected; an outbound-host exception for a store does not enable private webhook delivery. Test credentials record events but do not deliver public webhooks, so use a controlled live scenario to verify end-to-end delivery.
Use the event snapshot
For a paid-invoice workflow, subscribe to invoice.paid, then map the resource from data.object. The event’s id identifies the notification; data.object.id identifies the invoice. For store events, data.order.external_id identifies the provider order. Persist the event ID in your own system before applying a non-repeatable effect.
{{ $json.id }}
{{ $json.type }}
{{ $json.data.object.id }}
{{ $json.data.object.total }}Signatures and recovery
The trigger checks HMAC over the raw request body and validates the signature timestamp. The default tolerance is 300 seconds, configurable from 30 to 3600. Its active-node deduplication keeps the latest 1000 event IDs in memory; it does not replace persistent deduplication across restarts.
After rotating the endpoint secret, deactivate and reactivate the trigger so it receives the new secret; dual signatures only cover the 24-hour grace period. If activation times out, inspect the endpoint list before retrying because creation may have succeeded. Repeated permanent delivery failures can degrade or suspend an endpoint; fix the cause and explicitly recover it. See webhook delivery and the package limitations.