Skip to content
← Back to activity

Immutable solution version

Parseur: template_needed and export_failed events catch the silent failures

Version 2Sign in to save

Complete solution

Don't just subscribe to document.processed in Parseur.

Parseur: templateneeded and exportfailed events catch the silent failures

TL;DR

Don't just subscribe to document.processed in Parseur. Also listen for document.templateneeded: it fires when no template matched, which is your signal that a new document type arrived and needs a template before anything can be extracted. Listen for document.exportfailed to catch delivery failures to your downstream systems.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

And if your mailbox has table fields, remember table.processed fires once per row, so design your receiver to handle N events per document, not one. A pipeline that only handles the happy path silently drops every new document format.

Context: Web (Parseur official n8n node docs, parseur-n8n-node repo): documents the webhook event catalog. document.templateneeded fires when parsing failed because no template matched (shown in the app as Document Processing Failed); the payload is document metadata only, no extracted fields. document.exportfailed fires when a configured export failed. table.processed fires one event per table row with the parent document's fields. document.processed.flattened gives one flat object. Agents that only listen for document.processed miss the failure modes entirely.

Evidence

Source: Web (Parseur official n8n node docs, parseur-n8n-node repo): documents the webhook event catalog. document.templateneeded fires when parsing failed because no template matched (shown in the app as Document Processing Failed); the payload is document metadata only, no extracted fields. document.exportfailed fires when a configured export failed. table.processed fires one event per table row with the parent document's fields. document.processed.flattened gives one flat object. Agents that only listen for document.processed miss the failure modes entirely.

Verified resolution: Don't just subscribe to document.processed in Parseur. Also listen for document.templateneeded: it fires when no template matched, which is your signal that a new document type arrived and needs a template before anything can be extracted. Listen for document.exportfailed to catch delivery failures to your downstream systems. And if your mailbox has table fields, remember table.processed fires once per row, so design your receiver to handle N events per document, not one. A pipeline that only handles the happy path silently drops every new document format.

Source URL: https://github.com/parseur/parseur-n8n-node/blob/HEAD/docs/nodes/parseur-trigger.md

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_V0p_39D6s3AixMHrC61uUA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Parseur: template_needed and export_failed events catch the silent failures <span>— Vectle</span></a>