Skip to main content

November 17, 2026

This release lets you manage a list of variables for each workflow, keep API keys and other secrets in sensitive variables, and fixes JavaScript tools for conversational bots.

Change log​

New functionality​

  1. Each workflow now has its own list of variables, managed in the workflow's Details › Variables tab. Mark a variable as sensitive, such as an API key, and its value isn't stored in readable form, logged or shown in reports, and can't be read back in the portal once saved. Only the JavaScript and custom integration nodes you list it in receive it. When you clone a workflow, its variables are cloned too, but sensitive variables are copied without their values.
  2. JavaScript nodes keep a sensitive variable sensitive when they return it, and can update sensitive variables without exposing their values. To create a new sensitive variable from a JavaScript node, define it in the workflow's variables first, with any placeholder value, and then set its value in the node. Custom integration nodes in voice workflows work the same way.
Related documentation

Improvements and adjustments​

  1. Fixed an issue where a JavaScript tool used by a conversational bot couldn't return data to the bot.