/// EDIT
1 credit

Merge PDF API — combine up to 100 files

Order-preserving, metadata-aware, no page loss.

Try Merge PDF API — free →Read the docs

Free account. No card required.

How does the Merge PDF API work?

One HTTP request from any language. Every ASHDOCS endpoint uses the same X-API-Key header.

curl -X POST https://www.ashdocs.com/api/v1/tools/merge \
  -H "X-API-Key: ash_live_..." \
  -F "files=@chapter-1.pdf" \
  -F "files=@chapter-2.pdf"

How do I use Merge PDF API in Make, Zapier or n8n?

MAKE

Add an HTTP → Make a request module with multipart body: repeat the field key “files” once per PDF mapped from earlier modules, then download the merged result from the response URL.

Make setup guide →
ZAPIER

Use a Webhooks by Zapier Custom Request with a JSON body of file_urls (the attachment links from your trigger) and options.output set to “url” — map the returned file_url into Drive or Gmail.

Zapier setup guide →
n8n

In an HTTP Request node use Form-Data with several “files” parameters of type n8n Binary File, or send a JSON body of file_urls collected by earlier nodes.

n8n setup guide →
AIRTABLE

A scheduled automation script can collect the week’s attachment URLs and POST them as file_urls — the merged PDF lands back in an attachment field.

Airtable setup guide →

Common use cases

RELATED TOOLS