Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Parseur

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.

CategoryOther
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Parseur with Flows360

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.

Use the Parseur connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 6 actions and 5 triggers.

Available actions

  • Get Parsed Document by ID
  • Create Document
  • Create Document from File
  • Reprocess Document
  • Find Document
  • Custom API Call

Available triggers

  • New Document Processed
  • New Table Field Processed
  • New Document Not Processed
  • New Document Export Failed
  • New Mailbox

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Parseur
  • Package: @activepieces/piece-parseur@0.2.0
  • Exact artifact digest: sha256:bebf1301750ae1307e62c98b297a2d964fa46d90bd61a666cb30ae6905000b07
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Get Parsed Document by ID (getParsedDocumentById), Fetch parsed JSON / structured output for a given document ID Classification: read.
  • Create Document (createDocument), Creates a new document. Classification: read.
  • Create Document from File (createDocumentFromFile), Creates new document in mailbox from file. Classification: read.
  • Reprocess Document (reprocessDocument), Send an existing document back through parsing (e.g. after updating template). Classification: read.
  • Find Document (findDocument), Finds a document based on search param. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Document Processed, webhook.
  • New Table Field Processed, webhook.
  • New Document Not Processed, webhook.
  • New Document Export Failed, webhook.
  • New Mailbox, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects11
Supported actionsNot published
Triggers5

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Get Parsed Document by ID Yes No Fetch parsed JSON / structured output for a given document ID
Create Document Yes No Creates a new document.
Create Document from File Yes No Creates new document in mailbox from file.
Reprocess Document Yes No Send an existing document back through parsing (e.g. after updating template).
Find Document Yes No Finds a document based on search param.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Document Processed Yes No webhook trigger declared by the pinned package.
New Table Field Processed Yes No webhook trigger declared by the pinned package.
New Document Not Processed Yes No webhook trigger declared by the pinned package.
New Document Export Failed Yes No webhook trigger declared by the pinned package.
New Mailbox Yes No polling trigger declared by the pinned package.

Triggers

New Document Processed · Webhook

Fires when a new document is successfully processed and parsed by Parseur.

Inputs

  • mailboxId · string
New Table Field Processed · Webhook

Fires when a document with table fields is processed, and triggers for each row (table field) separately.

Inputs

  • mailboxId · string
New Document Not Processed · Webhook

Fires when Parseur fails to parse a document (e.g. no matching template).

Inputs

  • mailboxId · string
New Document Export Failed · Webhook

Fires when an automated export endpoint (webhook / integration) fails for a processed document.

Inputs

  • mailboxId · string
New Mailbox · Poll

Fires when a new mailbox is created in the Parseur account.

Setup

Setup

  1. Add the Parseur connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-parseur@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 6 actions and 5 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Parseur connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-parseur@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com