Generate PDFs from Zapier
To generate a PDF from Zapier, add a Webhooks/HTTP action step to your Zap that sends a POST request to the Docweave API (/api/v1/pdf) with your API key and a JSON body describing the document — Docweave renders it and returns the PDF in the response.
Wire the Zap step by step
Zapier has no dedicated Docweave app, but any HTTP-capable action step can call the API directly:
- In your Zap, add a new action step and search for Webhooks by Zapier (or an equivalent HTTP action on your plan).
- Choose the POST event as the action.
- Set URL to
https://docweave.dev/api/v1/pdf. - Under Headers, add
Authorization: Bearer dw_live_your_keyandContent-Type: application/json. - Set Data Pass-Through? to false and set Data Format to json, then paste the JSON body below, mapping in fields from earlier steps with Zapier's insert-field picker.
- Test the step — Zapier will show the API response, including the PDF result, which you can then feed into a later step (for example uploading to Google Drive or emailing it).
JSON body example
Paste this into the Webhooks step's data field, replacing the mapped values with fields from your trigger:
{
"source": {
"type": "template",
"template": "<h1>Order {{ order_id }}</h1><p>Customer: {{ customer_name }}</p><p>Total: {{ total }}</p>",
"data": {
"order_id": "{{1. Order ID}}",
"customer_name": "{{1. Customer Name}}",
"total": "{{1. Total}}"
}
},
"options": { "format": "A4" },
"idempotencyKey": "{{1. Order ID}}"
}…or call it from an AI agent
If your workflow runs through an AI agent step instead of a plain webhook, add the Docweave MCP server and call generate_pdf directly — same source types, no HTTP boilerplate:
// From an AI agent step over MCP — no HTTP plumbing:
npx @docweave/mcp
generate_pdf({
source: {
type: "template",
template: "<h1>Order {{ order_id }}</h1><p>Customer: {{ customer_name }}</p><p>Total: {{ total }}</p>",
data: { order_id: "1042", customer_name: "Acme Inc.", total: "$128.00" }
},
outputPath: "/tmp/order-1042.pdf"
})FAQ
How do I generate a PDF from Zapier?
Add a Webhooks by Zapier (or HTTP) action step, set it to POST, point the URL at https://docweave.dev/api/v1/pdf, add an Authorization header with your Docweave API key, and pass a JSON body describing the PDF source (HTML, a URL, or a template + data). Zapier sends the request and Docweave returns the rendered PDF.
Which Zapier step should I use to call the Docweave API?
Use the built-in "Webhooks by Zapier" app with the "POST" event, or any generic HTTP-request action step your plan supports. Zapier does not need a Docweave-specific integration — the Docweave API is a standard REST endpoint any HTTP step can call.
Can I use data from earlier Zap steps in the PDF?
Yes. Map fields from a previous trigger or action (for example a new form submission or CRM record) into the JSON body's data object using Zapier's insert-field pickers, and Docweave binds them into the {{ placeholders }} in your template.
How is a PDF generated through Zapier billed?
The same as any other request: per document, not per page. Each successful Zap run that calls the Docweave API counts as one document, regardless of how many pages the rendered PDF contains.
Ready to generate PDFs from your Zaps?
Get an API key