View as Markdown
PDF.co icon

PDF.co ACTION

PDF Merge

Merge PDF from two or more PDF files into a new one. See docs here
  • Action
  • Writes data
  • API key
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's PDF.co account once, then configure and run PDF Merge from your backend or agent.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "pdf_co-pdf-merge",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    pdf_co: { authProvisionId: "apn_xxxxxxx" },
    urls: ["URL"],
    name: "Name",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

PDF Merge inputs
Property Type Description
urls URL string[]
Array of urls to the source PDF files in the same order that you want them to be processed. Supports links from Google Drive, Dropbox and from built-in PDF.co files storage.
Required
name Name string
File name for generated output.
Optional
expiration Expiration integer
Output link expiration in minutes. Default is 60 (i.e. 60 minutes or 1 hour).
Optional
async Async boolean
Runs processing asynchronously. Returns JobId.
Optional
profiles Profiles any
Use this parameter to set additional configuration for fine tuning and extra options. Explore PDF.co for profile examples.
Optional

REFERENCE

Tool details

Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.

Registry key
pdf_co-pdf-merge
Version
0.0.2
App
PDF.co
Authentication
API key
Read-only
No
Destructive
No
Open world
Yes