Connect FlowParser to Coherence.
Upload, process, and manage documents programmatically with FlowParser's REST API. 2 triggers can start a workflow, and 1 action can run inside one.
TRIGGERS AND ACTIONS
Everything FlowParser can do in a workflow.
Triggers start a workflow when something happens in FlowParser. Actions are the steps a workflow can run there.
Names as listed in the automation catalog Coherence workflows use.
WORKFLOW IDEAS
What you can automate with FlowParser.
Starting points for a workflow. Choose the exact fields, conditions, and records it updates.
or New Parsed Document FoundFinishes with · Create or update a Coherence record
or New Parsed Document Found
SET UP
How to connect FlowParser.
The exact authentication fields depend on FlowParser. The workflow structure stays straightforward.
RELATED
Apps for the same workflow.
Apps that share a category with FlowParser or provide a complementary trigger or action.
QUESTIONS
FlowParser integration questions.
What can I automate with the FlowParser integration?
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.
How many FlowParser triggers and actions are available?
FlowParser currently lists 2 triggers and 1 action, each named on this page. The list is read from the automation catalog Coherence workflows use, so review those names before building a workflow.
Can FlowParser connect to other apps through Coherence?
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.
Do I need to write code to connect FlowParser?
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.
