Holded Trigger
AI-generatedSummary
Receives Holded webhook POSTs and starts the workflow for matching events, returning either the raw event body or a wrapper with event metadata. Add the node’s Production URL in Holded → Settings → Webhooks and subscribe to the events you want; optionally configure a Holded Webhook credential with a signing secret to verify signatures.
Inputs
- Events — Select event types to trigger on, such as Invoice - Created or Contact - Updated. Leave empty to accept every event sent to this URL.
- Payload Only — When enabled, output the raw webhook body. When disabled (default), include the body under
dataalong withevent,eventId,accountId,date, andversionfrom the request headers. - Holded Webhook credential — Optionally set a signing secret to verify the
x-holded-webhook-signature; requests with an invalid signature receive HTTP 401 and do not start the workflow.
Output shape
A single n8n item for each accepted webhook, containing either the raw request body or a metadata wrapper with the body in data.
Selected events are filtered by the
x-holded-webhook-eventheader; unmatched events returnOKwithout workflow data. Events include create, update, delete, and where available approve actions for the listed Holded document, contact, product, stock, and warehouse types.