Browser Use ACTION
Upload Workspace Files
Create presigned upload URLs for Browser Use workspace files, and optionally upload local Pipedream files to those URLs. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Browser Use account once, then configure and run Upload Workspace 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: "browser_use-upload-workspace-files",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
browser_use: { authProvisionId: "apn_xxxxxxx" },
workspaceId: "Workspace ID",
prefix: "Prefix",
},
})
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": "browser_use-upload-workspace-files",
"configured_props": {
"browser_use": { "authProvisionId": "apn_xxxxxxx" },
"workspaceId": "Workspace ID",
"prefix": "Prefix"
}
}'// 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": "browser_use",
},
},
},
)
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: "browser_use-upload-workspace-files",
arguments: {
workspaceId: "Workspace ID",
prefix: "Prefix",
},
})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 |
|---|---|---|
workspaceId Workspace ID | string | Select a Browser Use workspace or provide a workspace ID. Required Dynamic |
prefix Prefix | string | Optional directory prefix to upload into. Example: uploads/. Optional |
filePaths Local File Paths or URLs | string[] | Optional local Pipedream file paths or URLs to upload, usually under /tmp. Example: /tmp/report.csv. Names are derived from each file. Optional |
syncDir Sync Directory | dir | Directory containing local files to upload. Use /tmp for files generated by previous steps. Optional |
contentType Content Type | string | Content type to use for local file path uploads. Example: text/csv. Optional |
filesJson File Upload Items JSON | string | Optional JSON array of file metadata for presigned URLs without uploading local files. Example: [{"name":"data.csv","contentType":"text/csv","size":1234}]. Browser Use accepts 1 to 10 files per request. 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
- browser_use-upload-workspace-files
- Version
- 0.0.2
- App
- Browser Use
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗