Parseur is a document/email parsing tool that extracts structured data from emails, attachments, PDFs, invoices, forms, etc. It supports dynamic templates and table fields, and delivers parsed output to integrations (e.g. via webhook or API). This integration enables reactive workflows based on new processed documents, failed processing, mailbox changes, and more.
Parseur currently provides 5 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
New Document Processed
Fires when a new document is successfully processed and parsed by Parseur.
New Table Field Processed
Fires when a document with table fields is processed, and triggers for each row (table field) separately.
New Document Not Processed
Fires when Parseur fails to parse a document (e.g. no matching template).
New Document Export Failed
Fires when an automated export endpoint (webhook / integration) fails for a processed document.
New Mailbox
Fires when a new mailbox is created in the Parseur account.
Get Parsed Document by ID
Fetch parsed JSON / structured output for a given document ID
Create Document
Creates a new document.
Create Document from File
Creates new document in mailbox from file.
Reprocess Document
Send an existing document back through parsing (e.g. after updating template).
Find Document
Finds a document based on search param.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Parseur event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Document Processed
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Parseur action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Get Parsed Document by ID
Combine Parseur with another integration and Coherence records to move information into the same workspace as the people, records, and next steps it affects.
Starts with
New Document Processed
Finishes with
Get Parsed Document by ID, then preserve the outcome in Coherence
The exact authentication fields depend on Parseur. The workflow structure stays straightforward:
Authorize the Parseur account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Parseur or provide a complementary trigger or action.
Parseur currently provides 5 triggers that can start a workflow and 6 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
Parseur currently lists 5 triggers and 6 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Parseur triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
