Make.com Scenario → Polished PDF in One Step
Build a scenario that grabs a live report URL, converts it to PDF via the API, and ships it to the right folder or email list without touching code.
Launch Make.com PDFs in three steps
- Prepare data with HTTP or Airtable modules. Fetch the public URL or HTML content that you want rendered, then store it in a variable.
- Call the PDF API with the HTTP module. Set the URL to `/v1/render`, choose POST, and include your API key in the Authorization header. The body can contain either `url` or `html`.
- Fan out the PDF to storage and notifications. Pipe the binary response into Google Drive, Dropbox, or Slack modules to archive and alert stakeholders.
Make.com integration code
Drop this snippet into your project, replace `PDF_API_KEY`, and generate your first PDF. Pair it with the curl request for quick smoke tests.
URL: https://api.yourdomain.com/v1/render
Method: POST
Headers:
Authorization: Bearer {{PDF_API_KEY}}
Content-Type: application/json
Body (JSON):
{
"url": "{{webhook.payload.url}}",
"options": {
"format": "Letter",
"printBackground": true
}
}
Test with curl
curl -X POST https://api.yourdomain.com/v1/render \
-H "authorization: Bearer ${PDF_API_KEY}" \
-H "content-type: application/json" \
-d '{"url":"https://demo.yourdomain.com/report"}' \
--output report.pdf
Common pitfalls & fixes
- Watch Make.com execution limits; upgrade your plan if scenarios run in bursts.
- Always URL-encode dynamic parameters before injecting them into JSON bodies.
- Add a router branch for non-200 responses so failed renders trigger alerts.
FAQ
Can I add watermarking?
Yes. Include a watermark layer in your HTML template or use CSS `background-image` before rendering.
How do I handle large batches?
Throttle scenario execution or hand off bulk jobs to a queue so you stay within plan limits.