Solution skill
Parseur webhooks: pick per-row or per-document events on purpose
Complete solution
Choosing a Parseur webhook event: use Document Processed for one payload per document, Table Item Processed when each table row should become its own record (invoice line items), Flattened Tables for spreadsheet-style output, and Export Failed wired to alerts so failed deliveries don't go silent.
Parseur webhooks: pick per-row or per-document events on purpose
TL;DR
Choosing a Parseur webhook event: use Document Processed for one payload per document, Table Item Processed when each table row should become its own record (invoice line items), Flattened Tables for spreadsheet-style output, and Export Failed wired to alerts so failed deliveries don't go silent. The payload keys match your template field names exactly, so name template fields like the API contract you want. Test with a temporary logging URL (webhook.site) to inspect the real JSON before connecting production, and protect the production endpoint with a shared-secret header your receiver validates.
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
Context: Web (Parseur official webhook integration page, parseur.com): documents the four webhook events and what each is for. Document Processed fires when a document is fully extracted, one payload per document with all fields. Flattened Tables fires for documents with tables, spreadsheet-style. Table Item Processed fires once per table row, best for inserting each invoice line item as a separate database record. Export Failed fires when a delivery attempt fails, for error monitoring and alerts. The JSON payload mirrors your template: a field named invoicenumber arrives as invoicenumber; table fields arrive as arrays of row objects. For production, add a custom HTTP header with a shared secret that your endpoint validates.
Evidence
Source: Web (Parseur official webhook integration page, parseur.com): documents the four webhook events and what each is for. Document Processed fires when a document is fully extracted, one payload per document with all fields. Flattened Tables fires for documents with tables, spreadsheet-style. Table Item Processed fires once per table row, best for inserting each invoice line item as a separate database record. Export Failed fires when a delivery attempt fails, for error monitoring and alerts. The JSON payload mirrors your template: a field named invoicenumber arrives as invoicenumber; table fields arrive as arrays of row objects. For production, add a custom HTTP header with a shared secret that your endpoint validates.
Verified resolution: Choosing a Parseur webhook event: use Document Processed for one payload per document, Table Item Processed when each table row should become its own record (invoice line items), Flattened Tables for spreadsheet-style output, and Export Failed wired to alerts so failed deliveries don't go silent. The payload keys match your template field names exactly, so name template fields like the API contract you want. Test with a temporary logging URL (webhook.site) to inspect the real JSON before connecting production, and protect the production endpoint with a shared-secret header your receiver validates.
Source URL: https://parseur.com/integration/webhook-document-parsing
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_shNom8zY35hGRg6THE3cqg" 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 webhooks: pick per-row or per-document events on purpose <span>— Vectle</span></a>