Attachment PDFs in No-Code Tools
When a PDF URL triggers a download instead of opening, no-code tools cannot handle it. There is no way to write a headless browser workaround in Power Automate, Zapier, or Make. PDFPipe is the fix.
The problem no-code tools cannot solve
No-code platforms have built-in HTTP actions that can call APIs and process JSON responses. But when a PDF URL triggers a file download (attachment disposition) instead of returning the file content directly, the HTTP action gets an empty response or an HTML page.
In a coding environment, you could spin up Puppeteer or Playwright to capture the download. In Power Automate, Zapier, or Make, that is not an option. You are stuck with whatever the HTTP action can do - and it cannot handle attachment PDFs.
PDFPipe bridges this gap. You make one HTTP POST with the URL, and PDFPipe returns structured data in the response body. It does not matter whether the PDF is inline or an attachment - your no-code flow stays the same.
One HTTP action in any no-code tool
The setup is identical across platforms: add an HTTP action, point it at the PDFPipe API, and pass the PDF URL in the request body. The structured data comes back in the response for you to use in the next step of your flow.
HTTP action request body
This is the JSON body you configure in the HTTP action of your no-code tool. The URL can be any public PDF link - inline, attachment, redirect chain - PDFPipe handles it. It must be reachable without a login (PDFPipe does not send cookies), so for Drive, SharePoint, or Dropbox files use an "anyone with the link" sharing link.
{
"url": "https://supplier.com/invoices/download/INV-2025",
"format": "json",
"returnMethod": "inline"
}What you get back
The response contains the PDF's text in the format you asked for, as a string in the content field. Use it directly in the next step of your flow - no file handling, no downloads, no custom code. Attachment PDFs go through the headless browser and come back as a 202 with a poll URL, so add a short polling loop (each platform guide shows how).
- JSON with per-page text and the PDF's metadata
- Plain text for search or NLP steps
- Markdown with one section per page for document workflows
- CSV with one row per page for spreadsheet integration
Step-by-step guides for your platform
We have detailed setup guides for the most popular no-code platforms. Each guide walks you through the full setup from creating a flow to processing the response.
Stop fighting with attachment PDFs
300 free requests per month. All paid plans include unlimited attachment PDFs. No credit card required.