AlgoDocs ACTION
Upload File
Uploads a local file to an AlgoDocs folder for processing by a specific extractor via multipart/form-data (POST /v1/document/upload_local/{extractorId}/{folderId}). Returns the created document record including its
id and upload metadata. Run List Extractors to find a valid extractor ID and List Folders to find a valid folder ID before calling this action. The returned document id is the value to configure in New Extracted Data. See the documentation.- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's AlgoDocs account once, then configure and run Upload File 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: "algodocs-upload-file",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
algodocs: { authProvisionId: "apn_xxxxxxx" },
extractorId: "Extractor ID",
folderId: "Folder ID",
},
})
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": "algodocs-upload-file",
"configured_props": {
"algodocs": { "authProvisionId": "apn_xxxxxxx" },
"extractorId": "Extractor ID",
"folderId": "Folder ID"
}
}'// 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": "algodocs",
},
},
},
)
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: "algodocs-upload-file",
arguments: {
extractorId: "Extractor ID",
folderId: "Folder ID",
},
})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 |
|---|---|---|
extractorId Extractor ID | string | The ID of the extractor. Run the List Extractors action to get a list of valid extractor IDs. Example: 6d86215bf9cb4fc6ac1f6967. Required |
folderId Folder ID | string | The ID of the folder. Run the List Folders action to get a list of valid folder IDs. Example: 1a5e2f9c624b. Required |
file File | string | A file URL or a path to a file in the /tmp directory (for example, /tmp/invoice.pdf). The file is sent to AlgoDocs as multipart/form-data. Required |
syncDir SyncDir | dir | 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
- algodocs-upload-file
- Version
- 0.0.2
- App
- AlgoDocs
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗