CONNECT APP
Build with Talend
Data Analytics
- API key
MCP
Give your agent Talend tools
Every Talend action is exposed as an MCP tool on Pipedream's remote server. Point a client at it with your end user's ID and Connect resolves that user's Talend account for each tool call — you store no tokens.
// 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": "talend",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// e.g. run Execute Plan:
const result = await mcp.callTool({
name: "talend-execute-plan",
arguments: {
planExecutable: "Plan Executable",
},
})# access_token: mint a short-lived token with the Connect SDK — see the MCP guide
headers = {
"Authorization": f"Bearer {access_token}",
"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": "talend",
}
async with streamablehttp_client("https://remote.mcp.pipedream.net/v3", headers=headers) as (read, write, _):
async with ClientSession(read, write) as session:
await session.initialize()
tools = await session.list_tools()
# e.g. run Execute Plan:
result = await session.call_tool("talend-execute-plan", {
"planExecutable": "Plan Executable",
})API PROXY
Call the Talend API directly
For an endpoint with no pre-built tool, the Connect proxy forwards your request to the Talend API with the connected user's credentials attached. You store no tokens and write no refresh logic.
const resp = await pd.proxy.get({
externalUserId: "{external_user_id}", // any stable ID for this user in your system
accountId: "apn_xxxxxxx",
url: "https://api.example.com/v1/me",
})
// Any allowed Talend endpoint works here. Pipedream attaches the
// connected account's credentials to the outgoing request.# The path segment is the target URL, URL-safe base64 encoded:
# https://api.example.com/v1/me
curl "https://api.pipedream.com/v1/connect/{project_id}/proxy/aHR0cHM6Ly9hcGkuZXhhbXBsZS5jb20vdjEvbWU?external_user_id={external_user_id}&account_id=apn_xxxxxxx" \
-H "Authorization: Bearer {access_token}" \
-H "x-pd-environment: production"SDK
Run Talend actions from your backend
Connect a user's Talend account once, then run Execute Plan on their behalf from your own code — TypeScript, Python, or plain HTTP.
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: "talend-execute-plan",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
talend: { authProvisionId: "apn_xxxxxxx" },
planExecutable: "Plan Executable",
},
})from pipedream import Pipedream
pd = Pipedream(
client_id="{oauth_client_id}",
client_secret="{oauth_client_secret}",
project_id="{project_id}",
project_environment="production",
)
result = pd.actions.run(
id="talend-execute-plan",
external_user_id="{external_user_id}", # any stable ID for this user in your system
configured_props={
"talend": {"authProvisionId": "apn_xxxxxxx"},
"planExecutable": "Plan Executable",
},
)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": "talend-execute-plan",
"configured_props": {
"talend": { "authProvisionId": "apn_xxxxxxx" },
"planExecutable": "Plan Executable"
}
}'TOOLS
Talend actions
On-demand operations your product or agent can configure and run on behalf of a connected user.
-
Execute Plan
actionAllows to run a Plan. See the documentation.Writev0.0.2 -
Get Available Plans Executions
actionList all plan executions the user is granted visibility on. For each plan execution returns execution and plan identifiers, start and finish timestamps, execution status and counters on done and planned executables within plan. See the documentation.Read-onlyv0.0.2 -
Get Plan Execution Status
actionGet detailed status of one plan execution. See the documentation.Read-onlyv0.0.2 -
List Environment Options
actionRetrieves available options for the Environment field.Read-onlyv0.0.1 -
List Plan Executable Options
actionRetrieves available options for the Plan Executable field.Read-onlyv0.0.1 -
List Plan Execution ID Options
actionRetrieves available options for the Plan Execution ID field.Read-onlyv0.0.1 -
List Workspace Options
actionRetrieves available options for the Workspace field.Read-onlyv0.0.1
No Talend triggers are available yet.
MULTI-APP
Use Talend with other popular apps
Most products don't stop at one integration. Pair Talend with the other apps your users rely on, and ship use cases that span both.
- App slug
- talend
- Authentication
- API key
- Categories
- Data Analytics
- Actions
- 7
- Triggers
- 0
- API proxy
- Available