Merge and generate documents with dynamic data
DocuMerge currently provides 2 triggers that can start a workflow and 5 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
New Merged Document
Triggers when a merged/populated document is created
New Merged Route
Triggers when a merged/populated route is created
Combine Files
Combine multiple files into a single PDF or DOCX
Convert File to PDF
Convert a given file to PDF
Create Data Route Merge
Send data to your Data Route URL
Create Document Merge
Send data to your Merge URL
Split PDF
Extract or remove specific pages from a PDF file
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 DocuMerge event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Merged Document
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported DocuMerge 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
Combine Files
Combine DocuMerge with another integration and Coherence records to turn activity in one tool into an owned next step in the shared workspace.
Starts with
New Merged Document
Finishes with
Combine Files, then preserve the outcome in Coherence
The exact authentication fields depend on DocuMerge. The workflow structure stays straightforward:
Authorize the DocuMerge 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 DocuMerge or provide a complementary trigger or action.
DocuMerge currently provides 2 triggers that can start a workflow and 5 actions a workflow can run. Use those building blocks to turn activity in one tool into an owned next step in the shared workspace.
DocuMerge currently lists 2 triggers and 5 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 DocuMerge 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.
