View as Markdown
PDF4me icon

PDF4me ACTION

Merge PDF Files

Merge multiple PDF files into a single PDF. See the documentation
  • Action
  • Writes data
  • API key
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's PDF4me account once, then configure and run Merge PDF Files 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: "pdf4me-merge-pdfs",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    pdf4me: { authProvisionId: "apn_xxxxxxx" },
    filePaths: ["File Paths or URLs"],
    filename: "File 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.

Merge PDF Files inputs
Property Type Description
filePaths File Paths or URLs string[]
The files to process. For each entry, provide either a file URL or a path to a file in the /tmp directory (for example, /tmp/myFile.pdf)
Required
filename File Name string
The filename to save the resulting PDF in the /tmp directory
Required
syncDir SyncDir dir
Required

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
pdf4me-merge-pdfs
Version
0.1.3
App
PDF4me
Authentication
API key
Read-only
No
Destructive
No
Open world
Yes