Integration

Talend Cloud integration

Talend Cloud (Qlik Talend Cloud) Management Console API for data integration operations. Run tasks and plans on demand and follow their executions (status, timings, processed and rejected row counts, errors), terminate a running task, re-run a plan from a failed step, pause or resume tasks and plans, and read workspaces, environments, tasks, plans, run configurations, schedules and upcoming scheduled runs, artifacts, projects, resources, remote engines and clusters. Creating, editing or deleting tasks, plans, schedules, workspaces, environments, connections and engines, promotions, run profiles, engine pairing and user permissions are not exposed, nor are connection details, task parameter values, webhook trigger URLs or engine pre-authorized keys. Authentication is a Talend Cloud Personal Access Token (generated in the Talend Cloud portal under Profile Preferences) sent as a bearer token; a service account token expires after 30 minutes and cannot be stored here. The connection's region is the API region of your Talend Cloud account: us, eu, ap, au or us-west.

Connect Talend Cloud How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Talend Cloud.Built from the 42 Talend Cloud tools below, on the connection you add once.

What you can do with Talend Cloud

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Execution, 8 operations

get_task_executionGet task executionGETReturns the status of a task execution: status, detailed execution status, trigger, start and finish times, engine, processed and rejected row counts, and error type and message if it failed.
list_executions_of_planList executions of planGETLists the executions of one plan in pages of up to 100, filtered by status, the last N days or a from/to window in epoch milliseconds.
list_executions_of_taskList executions of taskGETLists the executions of one task in pages of up to 100, filtered by status, the last N days (1 to 60) or a from/to window in epoch milliseconds.
list_plan_executionsList plan executionsGETLists plan executions you can see, in pages of up to 100: ids, start and finish times, status, counts of planned and done executables. Filters: environment or workspace, status, days, from/to.
list_task_executionsList task executionsGETLists task executions in pages of up to 100, filtered by environment or workspace, status, the last N days (1 to 60, default 60) or a from/to window in epoch milliseconds.
run_taskRun taskPOSTStarts a run of a task now and returns its executionId; follow it with get_task_execution. Optional: parameter values for this run, log level and a timeout in minutes.
search_task_executionsSearch task executionsPOSTLists task executions with filters in the body, which also allows filtering on task tags: environment or workspace, status, last N days or a from/to window, in pages of up to 100.
terminate_task_executionTerminate task executionDELETETerminates a running task execution. Success has an empty body.

Plan, 4 operations

get_planGet planGETReturns one plan: name, description, workspace, status, pause state and its chart of steps, each with its tasks (flows), next step and step run on exception.
get_plan_executionGet plan executionGETReturns the detailed status of a plan execution: status, start and finish times, planned and done executable counts and the status of each executed task.
list_plansList plansGETLists plans in pages (up to 100), filtered by environment, workspace, name, plan id or a task they contain: id (executable), name, workspace. Use the executable as planId.
run_planRun planPOSTStarts a run of a plan and returns its executionId. To re-run a failed plan execution from one step, also pass executionPlanId and stepId; rerunOnlyFailedTasks limits it to failed tasks.

Schedule, 4 operations

get_plan_scheduleGet plan scheduleGETReturns the schedule linked to a plan: description, environment and triggers. Needs view permission on the plan's workspace.
get_scheduleGet scheduleGETReturns one schedule: description, environment, the task or plan it applies to, and its triggers (once, daily, weekly, monthly or cron, with times, days, time zone and timeout).
get_task_scheduleGet task scheduleGETReturns the schedule linked to a task: description, environment and triggers. Needs view permission on the task's workspace.
list_schedulesList schedulesGETLists schedules in pages (up to 100), filtered by environment, a regular expression on the description, or only those bound to a task or plan.

Event, 3 operations

list_plan_scheduled_triggersList plan scheduled triggersGETLists the times a plan's cron schedule will trigger between from and to (epoch milliseconds), in pages of up to 100.
list_task_scheduled_triggersList task scheduled triggersGETLists the times a task's cron schedule will trigger between from and to (epoch milliseconds), in pages of up to 100.
simulate_schedule_eventsSimulate schedule eventsGETSimulates a schedule: lists the date-times it would trigger between from (default now) and to (epoch milliseconds), each with the name of the trigger that produced it.

Artifact, 2 operations

get_artifactGet artifactGETReturns one artifact: name, type, available versions and workspace.
list_artifactsList artifactsGETLists artifacts (jobs, routes, data services published from Talend Studio) in pages of up to 100, filtered by environment, workspace, name or type, with their versions.

Pause, 2 operations

pause_or_resume_planPause or resume planPUTPauses (pause=true) or resumes (pause=false) the executions of a plan, with an optional note (pauseContext) recording why, for example a maintenance window.
pause_or_resume_taskPause or resume taskPUTPauses (pause=true) or resumes (pause=false) a task. Paused: running executions finish, new scheduled, manual and webhook runs are discarded. Resumed: every trigger is active again.

Project, 2 operations

get_projectGet projectGETReturns one project: name, technical label, description, repository URL and type, author, owner, project type and dates. Works only with a Personal Access Token.
list_projectsList projectsGETLists projects in pages of up to 100, optionally filtered by name: technical label, description, repository URL and type, author, owner and dates. Works only with a Personal Access Token.

Remote engine, 2 operations

get_remote_engineGet remote engineGETReturns one remote engine: name, workspace, runtime id, availability, pairing status, run profiles, cluster and dates. Its pre-authorized pairing key is not returned.
list_remote_enginesList remote enginesGETLists remote engines: name, workspace, runtime id, availability, pairing status, run profiles and cluster. query filters them in FIQL, for example workspace.environment.id==<id>.

Remote engine cluster, 2 operations

get_remote_engine_clusterGet remote engine clusterGETReturns one remote engine cluster: name, workspace, runtime id, availability, whether managed, and the ids of its engines.
list_remote_engine_clustersList remote engine clustersGETLists remote engine clusters: name, workspace, runtime id, availability and whether managed. _s filters them in FIQL, for example name==NewCluster.

Resource, 2 operations

get_resourceGet resourceGETReturns one resource: name, description, workspace and whether it is a file.
list_resourcesList resourcesGETLists resources (files and other shared resources used by tasks) in pages of up to 100, filtered by name, environment or workspace.

Run config, 2 operations

get_plan_run_configGet plan run configGETReturns a plan's run configuration: its trigger (type, interval, start date and time, time zone, cron) and whether parallel runs are allowed.
get_task_run_configGet task run configGETReturns a task's run configuration: trigger (type, interval, start, time zone, cron), runtime, parallel runs allowed, log level, run-as user, timeout and deployment strategy.

Search, 2 operations

search_scheduled_executionsSearch scheduled executionsPOSTLists the scheduled runs of all tasks and plans of an environment up to a date (to, epoch milliseconds), optionally narrowed to workspaces, tags or a runtime, in pages of up to 100.
search_tasksSearch tasksPOSTSearches tasks by name (contains), environment or workspace (not both), artifact, runtime, run profile, tags (all must match) or trigger type, in pages of up to 100.

Step, 2 operations

get_plan_execution_stepGet plan execution stepGETReturns one step of a plan execution (error handler excluded): status, times, planned and done executable counts and the status of the tasks and plans it ran.
list_plan_execution_stepsList plan execution stepsGETLists the steps of a plan execution in designed order (error handlers excluded): ids, start and finish times and status of each step.

Task, 2 operations

get_taskGet taskGETReturns one task: name, description, version, workspace, artifact and version, tags, connection and resource ids, auto-upgrade settings and pause state. Parameter values are not returned.
list_tasksList tasksGETLists tasks in pages (up to 100), filtered by environment, workspace, name, artifact or runtime: id (executable), name, workspace, artifact and runtime. Use the executable as taskId.

Environment, 1 operation

list_environmentsList environmentsGETLists the environments you can see (for example Development, QA, Production) with their default flag and cloud engine limit. query filters them in FIQL, for example name==Dev*.

Error handler, 1 operation

get_plan_step_error_handlerGet plan step error handlerGETReturns the execution of the error handler of one plan step: status, times, planned and done executable counts and the status of the tasks and plans it ran.

Workspace, 1 operation

list_workspacesList workspacesGETLists the workspaces you can see, with their owner, type (shared, personal or custom) and environment. query filters them in FIQL, for example name==Finance*.

Use Talend Cloud from Claude Code, Cursor or Codex

Connect Talend Cloud in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Talend Cloud operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Talend Cloud

Create your workspace
Sign up free. Nothing to install.
Connect Talend Cloud once
Add your Talend Cloud connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.