PDF Generation Template Editor
Open-source visual PDF generation engine with customizable templates and developer-friendly APIs.
Open-source visual PDF generation engine with customizable templates and developer-friendly APIs.
When the ComPDF app in Zapier offers the action you need, use it directly. Otherwise, use Webhooks by Zapier to call ComPDF Cloud and access the capabilities you need. After processing a document, pass the result to the next app in your Zap.
Before you start: A Zapier account, a ComPDF API key, and a non-sensitive sample file.
Follow these steps to build your automated workflow. For a more detailed walkthrough, see Process PDF on Zapier with ComPDF.
POST, and use https://api-hub.compdf.com/api/v2/files/upload as the URL.Authorization: Bearer YOUR_API_KEY, map file or url, set mode to VisualExtract or LayoutExtract, and optionally add metadata.code: 200, save data.batchId and data.taskIds, then add a result action or a controlled Delay + task lookup.| Field | Example value |
|---|---|
| Method | POST |
| URL | https://api-hub.compdf.com/api/v2/files/upload |
| Header | Authorization: Bearer YOUR_API_KEY |
url | File URL from the trigger |
mode | VisualExtract |
metadata | {"source":"zapier"} |
You can build a workflow from scratch, or start with a ComPDF template and use it as a core step in your automation. Choose a template to get started. Find more workflows in the ComPDF Zapier integrations directory.
Watch Drive files and convert files that have been updated to DOCX. Customize the next steps for your needs, such as saving the file to Google Drive, emailing it to a customer, or sharing it with colleagues.
Use an email attachment as the input and continue with the generated PDF.
Extract fields from an updated Drive document and map them to a business app.
If the current ComPDF action list does not include the capability you need, use a generic HTTP request with Webhooks by Zapier:
POST https://api-hub.compdf.com/api/v2/files/upload
Authorization: Bearer YOUR_API_KEY
Content-Type: multipart/form-data
url={{Trigger File URL}}
mode=VisualExtract
metadata={"source":"zapier","record_id":"{{Record ID}}"}Check the response body for code: 200, then save data.batchId and data.taskIds.
| Symptom | What to check |
|---|---|
401 / unauthorized | Confirm that the API key is valid and the Authorization value starts with Bearer . |
| ComPDF cannot retrieve the file | Confirm that the trigger URL is accessible without a browser session and has not expired. |
| Request succeeds but the result is not ready | Check the response-body code, keep the task ID, and add Delay + lookup or a Catch Hook. |
| Duplicate records | Keep a source ID in metadata and make sure downstream actions can identify duplicate records. |
Should I use the ComPDF app or Webhooks by Zapier?
Use the ComPDF app when it offers the action you need. Use Webhooks by Zapier when the current action list does not expose the endpoint or parameter you need.
How do I handle asynchronous tasks?
Save the task ID, then use a controlled Delay and lookup or receive a verified ComPDF webhook through a Catch Hook.
Can I upload private files?
Yes. Use a file-capable multipart request for private sources. A URL must be accessible to ComPDF and remain valid long enough for retrieval.