Eden AI ACTION
Translate Document
Translates a document from a local file or URL. See the documentation
- Action
- Writes data
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Eden AI account once, then configure and run Translate Document 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: "eden_ai-translate-document",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
eden_ai: { authProvisionId: "apn_xxxxxxx" },
providers: ["Providers"],
fallbackProviders: ["Fallback Providers"],
},
})
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": "eden_ai-translate-document",
"configured_props": {
"eden_ai": { "authProvisionId": "apn_xxxxxxx" },
"providers": ["Providers"],
"fallbackProviders": ["Fallback Providers"]
}
}'// 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": "eden_ai",
},
},
},
)
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: "eden_ai-translate-document",
arguments: {
providers: ["Providers"],
fallbackProviders: ["Fallback Providers"],
},
})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 |
|---|---|---|
providers Providers | string[] | One or more providers that the data will be redirected to in order to get the processed results. See the documentation for available providers. Required |
fallbackProviders Fallback Providers | string[] | Providers to be used as fallback if the call to the first provider fails. To use this, you must input only one provider in the Providers prop, and you can input up to 5 fallbacks. They will be tried in the same order they are input, and it will stop on the first provider who doesn't fail. Optional |
showOriginalResponse Show Original Response | boolean | If set, the response will include the original response of the provider. Optional |
sourceLanguage Source Language | string | This should be a language code (e.g. en, fr) Optional |
targetLanguage Target Language | string | This should be a language code (e.g. en, fr) Required |
file File Path Or Url | string | Provide either a file URL or a path to a file in the /tmp directory (for example, /tmp/example.pdf) 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
- eden_ai-translate-document
- Version
- 1.0.3
- App
- Eden AI
- Authentication
- API key
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗