iLovePDF ACTION
Process Files
Process one or more files with the desired tool. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's iLovePDF account once, then configure and run Process 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: "ilovepdf-process-files",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
ilovepdf: { authProvisionId: "apn_xxxxxxx" },
filePaths: ["File Paths or URLs"],
tool: "Tool",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "ilovepdf-process-files",
"configured_props": {
"ilovepdf": { "authProvisionId": "apn_xxxxxxx" },
"filePaths": ["File Paths or URLs"],
"tool": "Tool"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "ilovepdf",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "ilovepdf-process-files",
arguments: {
filePaths: ["File Paths or URLs"],
tool: "Tool",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| 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 |
tool Tool | string | The tool to be used for the operation Required |
extraParameters Extra Parameters | object | Any extra parameters to be passed. Values will be parsed as JSON when applicable. Refer to the documentation for the extra parameters of each tool. Optional |
outputFilename Output Filename | string | If specified, the name of the file that will be written to the /tmp folder. Defaults to the download filename returned by the API. Optional |
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
- ilovepdf-process-files
- Version
- 1.0.3
- App
- iLovePDF
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗