DocuMerge

Overview

Connect DocuMerge with Flows360

Merge and generate documents with dynamic data

Use the DocuMerge 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 5 actions and 2 triggers.

Available actions

• Combine Files
• Convert File to PDF
• Create Data Route Merge
• Create Document Merge
• Split PDF

Available triggers

• New Merged Document
• New Merged Route

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: DocuMerge
• Package: @activepieces/piece-documerge@0.1.7
• Exact artifact digest: sha256:840d493f6f396468a9cf850c39ebabed8b4bc5c4d83e03239cb9996ba98688a2
• 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

• Combine Files (combine_files), Combine multiple files into a single PDF or DOCX Classification: read.
• Convert File to PDF (convert_file_to_pdf), Convert a given file to PDF Classification: read.
• Create Data Route Merge (create_data_route_merge), Send data to your Data Route URL Classification: read.
• Create Document Merge (create_document_merge), Send data to your Merge URL Classification: read.
• Split PDF (split_pdf), Extract or remove specific pages from a PDF file Classification: read.

Trigger contracts

• New Merged Document, webhook.
• New Merged Route, webhook.

Verification

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

Capability summary

Authentication

Authentication method: custom

Authentication profiles

Supported objects

Triggers

Setup

Setup

1. Add the DocuMerge 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-documerge@0.1.7; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
• Only the 5 actions and 2 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

Related documentation