Overview
This node acts as a trigger for workflows based on events sent from the Parseur service, which is used for parsing emails and documents. It listens to specific Parseur webhook events such as document processing status changes or table extraction completions. When one of these events occurs, the node activates the workflow with the event data.
Common scenarios include:
- Automatically processing parsed document data once a document is successfully processed.
- Handling errors when document export or processing fails.
- Triggering workflows when tables are extracted from documents, enabling further automation like data insertion into databases or spreadsheets.
Practical example:
- A user configures this node to trigger when a "Document Processed" event occurs for a specific mailbox. Once triggered, the workflow can extract relevant data fields and update a CRM system automatically.
Properties
| Name | Meaning |
|---|---|
| Event | The type of Parseur event to listen for. Options include: • Document Export Failed • Document Processed • Document Processed (Flattened) • Document Processing Failed • Table Processed • Table Processed (Flattened) |
| Mailbox Name or ID | Select the mailbox (parser) from which to receive events. This list depends on the selected event type. You can also specify an ID using an expression. |
| Table Name or ID | For table-related events only ("Table Processed" or "Table Processed (Flattened)"), select the specific table field to monitor. This list depends on the selected mailbox and event. Can be specified via expression. |
Output
The node outputs the JSON payload received from the Parseur webhook event in the json field of the output data. This payload contains detailed information about the document or table processed, including metadata and extracted data.
If the event relates to tables, the output includes structured table data. For document events, it includes document status and content details.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Parseur API.
- Needs proper configuration of webhooks in Parseur to send events to the n8n webhook URL.
- Uses internal methods to dynamically load available mailboxes and table fields from Parseur for property selection.
Troubleshooting
- Unauthorized webhook: token mismatch: Occurs if the incoming webhook request does not contain the expected authentication token. Ensure the Parseur webhook is configured with the correct token matching the node's credentials.
- Unauthorized webhook: event mismatch: Happens if the event type in the webhook does not match the configured event in the node. Verify that the event selected in the node matches the event sent by Parseur.
- Select a Mailbox before: If you try to load table fields without selecting a mailbox, the node will throw this error. Always select a mailbox first.
- This Mailbox has no table fields configured: When selecting a table event but the chosen mailbox has no tables configured, this error appears. Choose another mailbox or change the event type.
- For table events, you must select a Table Field: When creating the webhook for table events, a table field selection is mandatory.