Overview
This node acts as a webhook trigger for receiving enrichment results from the FullEnrich service. It listens for specific events sent via HTTP POST requests and triggers workflows when those events occur. A common use case is to automate processes based on data enrichment results, such as updating customer profiles or triggering notifications once enriched data is available.
For example, when FullEnrich sends an enrichment result callback, this node captures that data and passes it into the workflow for further processing.
Properties
| Name | Meaning |
|---|---|
| Events | The types of events to listen for. Currently supports: "Enrichment Result" event only. |
Output
The node outputs the received enrichment data in the json field. Specifically, it expects the webhook payload to contain a property datas which is an array. Each element of this array is output as a separate JSON item in the workflow data.
Output structure example:
[
{
"json": {
// one enrichment result object from the datas array
}
},
{
"json": {
// another enrichment result object
}
}
]
No binary data output is produced by this node.
Dependencies
- Requires an externally accessible webhook URL configured in n8n to receive POST requests from FullEnrich.
- No additional API keys or credentials are handled by this node itself; authentication with FullEnrich must be managed outside or prior to this trigger.
Troubleshooting
- Invalid webhook payload: If the incoming webhook does not contain a valid body or the
datasproperty is missing or not an array, the node will throw an error indicating an invalid payload. Ensure FullEnrich sends the expected JSON structure. - Webhook not triggering: Verify that the webhook URL is correctly set up in FullEnrich and publicly accessible by FullEnrich servers.
- Empty output: If no data is received or the
datasarray is empty, the node will produce no output items.
Links and References
- FullEnrich official documentation (for webhook setup and payload format)
- n8n Webhook Trigger Documentation