Inspect PDF Metadata Before Routing

🧩 Problem

Flows need to know PDF size or page count to branch correctly. When malformed or unstructured data hits routers, filters, or API connectors, entire automations halt or silently drop records. Teams end up retrying runs, hand-editing payloads, and explaining delays to customers.

💡 Why This Happens

Automation tools don’t expose PDF metadata. Most automation platforms assume well-formed payloads and do minimal validation. AI models, third-party APIs, and changing vendor schemas drift over time, mixing encodings, formats, and unexpected fields that downstream steps cannot tolerate.

🚀 The Fix: PDF Info (API Endpoint)

Use this endpoint to solve the problem reliably inside Zapier, Make.com, n8n.

Endpoint

POST https://api.postthatgetthis.com/pdf/info

Example Input

{ "file_url": "https://example.com/file.pdf" }

Example Output

{ "pages": 4, "size_bytes": 204800 }

📦 What This Solves

• Get page counts
• Check file size
• Branch flows without downloads

Not seeing your exact problem? Tell us what’s breaking in your workflow and we’ll help fix it: Submit A Problem.

🔗 Related Use Cases

• Split PDFs into Pages
• Merge PDFs

👉 Try it now

Use this endpoint directly in your automation tool. POST → get cleaned, structured data. Every time.