Talend Management Console
Last updated: 9/30/2026Upcoming changes for UI
In R2026-11, Talend Management Console will mask the webhook URL for a task or plan trigger, displaying it as *******, for users who do not have Operator (Execute) permission on the space. Users with this permission will continue to see the full webhook URL.
For more information, see Webhooks in Talend Management Console and Generating a webhook URL.
Upcoming changes for API
In the same R2026-11 release, the run-config response returned for task and plan executables will mask the webhook trigger url as ******* for callers who do not have Operator (Execute) permission on the space. Callers with this permission will continue to receive the full URL.
Before:
{
"trigger": {
"webhook": {
"name": "wh",
"triggerCalls": 10,
"triggerTimeout": 30000,
"runAsUser": "myuser",
"runAsUserType": "HUMAN",
"url": "https://webhooks.eu.cloud.talend.com/mywebhook/<webhook-id>"
}
}
}After, for callers without Operator (Execute) permission on the space:
{
"trigger": {
"webhook": {
"name": "wh",
"triggerCalls": 10,
"triggerTimeout": 30000,
"runAsUser": "myuser",
"runAsUserType": "HUMAN",
"url": "*******"
}
}
}What you should do
If you have automation, integrations, or service accounts that read the webhook URL through the API, grant them Operator (Execute) permission on the relevant space before this change takes effect. Otherwise, they will receive the masked value instead of the webhook URL.
New features
| Feature | Description |
|---|---|
| Lineage generated for each Job task execution |
When lineage collection is enabled for a Job task, lineage is now generated for each task execution instead of only the first successful execution of a task version. This update helps ensure that lineage changes are reflected after every run in Qlik Cloud. For more information, see Enabling lineage collection for Job tasks. |