Upload, process, and manage documents programmatically with FlowParser's REST API.
FlowParser currently provides 2 triggers that can start a workflow and 1 action a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
New Parsed Document by Template
Triggers when a new document is parsed using a specific template
New Parsed Document Found
Triggers when a document has been successfully parsed
Upload Document
Upload a new document to FlowParser for processing
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 FlowParser event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Parsed Document by Template
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported FlowParser 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
Upload Document
Combine FlowParser with another integration and Coherence records to connect product and engineering activity to the customers and work it affects.
Starts with
New Parsed Document by Template
Finishes with
Upload Document, then preserve the outcome in Coherence
The exact authentication fields depend on FlowParser. The workflow structure stays straightforward:
Authorize the FlowParser 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 FlowParser or provide a complementary trigger or action.
FlowParser currently provides 2 triggers that can start a workflow and 1 action a workflow can run. Use those building blocks to connect product and engineering activity to the customers and work it affects.
FlowParser currently lists 2 triggers and 1 action 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 FlowParser 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.
