Integrate ComPDF with Make

Connect Make with ComPDF to work with files from apps across your workflow. See the ComPDF Cloud feature list for the full set of supported capabilities.

Before you start: A Make account, a ComPDF API key, and a non-sensitive sample file.

Create a connection and run your first Scenario

This guide does not provide a verified, public ComPDF Blueprint. Build the Scenario with the modules available in your Make workspace.

1. Create a ComPDF account. Go to ComPDF Sign in / Sign up, then open the API Keys page. The account includes 200+ free API calls per month.
2. Create and save an API key. Copy the full key immediately and store it in a secure Make connection or a restricted variable. Do not put it in a shared Scenario or public Blueprint.
3. Create a Scenario. Add a source trigger, such as Google Drive Watch Files, then add the source app's Download File module.
4. Add ComPDF. Use an available ComPDF module, or add HTTP > Make a request. Set Method to POST and the URL to https://api-hub.compdf.com/api/v2/files/upload.
5. Configure the request body. Add Authorization: Bearer YOUR_API_KEY. For HTTP, select Multipart/form-data, add a File field named file, then add the mode and optional metadata text fields.
6. Run once and continue. Enable response parsing, verify the HTTP status and response-body code: 200, save the task ID, then wait for completion using a Custom Webhook or a controlled status check.

HTTP · Make a request configuration example

Field	Example value
Method	POST
URL	https://api-hub.compdf.com/api/v2/files/upload
Body type	Multipart/form-data
file	File: {{download.data}}
mode	Text: LayoutExtract
metadata	Text: {"source":"make"}
Response parsing	Enabled

Guides and Scenario examples

With ComPDF Integrations, you can connect ComPDF to apps in Make and process documents from those apps. See the detailed guide to learn how to build an automated workflow with Make.

Google Drive → ComPDF: Extract invoice fields

Watch a folder, download invoices, extract fields, and send exceptions for review.

Watch → Download → Extract → ERP / Review

Email / Dropbox → ComPDF: Convert or merge files

Receive source documents, convert or merge them, and save the processed files.

Source → File → ComPDF → Storage

Form → ComPDF: Process submitted documents

Process supporting documents, filter incomplete cases, and notify the owner when a review is needed.

Form → Extract → Filter → Queue

API request reference

For a generic HTTP request, use the multipart example below. Let Make generate the multipart boundary; do not set it manually.

POST https://api-hub.compdf.com/api/v2/files/upload
Authorization: Bearer YOUR_API_KEY
Content-Type: multipart/form-data

file={{download.data}}
mode=LayoutExtract
metadata={"source":"make","scenario_id":"invoice-intake"}

Confirm that the response contains code: 200 before continuing the workflow.

Troubleshooting

Symptom	What to check
Multipart request rejected	Select Multipart/form-data and let Make generate the boundary. Do not set a fixed boundary manually.
Empty file received	Inspect the download module's bundle and map the actual file data and name to the File field.
Response fields are missing	Enable response parsing and run the HTTP module once so Make can read the response structure.
Scenario continues too early	Save the task ID and use a Custom Webhook or controlled task status check before updating the destination system.

Frequently asked questions

Do I need to import a ComPDF Blueprint?

No. This guide uses a module-based setup. Build the Scenario in Make and check whether a ComPDF module is available in your workspace.

Do I need to set the Content-Type manually?

Select Multipart/form-data and let Make generate the boundary. Add the Authorization header separately.

How do I handle asynchronous tasks?

Use a Custom Webhook or a controlled task lookup. Match the task ID with the original business identifier before writing the final record.