Resolve Variables
Use this action when workflow or agent steps need values from your company variables — including secrets — inside CEL expressions.
Best for
- Loading an API key before an HTTP request step, then using it as
"Bearer " + myToken - Keeping credentials out of workflow definitions
- Reusing the same configuration values across many workflows
Main fields
| Field | What it does |
|---|---|
| Entries | The list of variables to load. Each entry has a Variable Name that must match the name of a variable defined in your company |
What later steps can use
This action does not create a separate step output. Each resolved variable is placed directly into the CEL context under its own name, so later expressions can reference it like any other value.
Example:
- Load a variable named
myToken - Use
"Bearer " + myTokenin a later HTTP header
Tips
- Variables are created and managed in the AutoTalk app; this action is how workflow and agent runs read them. Values are stored encrypted and only decrypted at run time.
- A variable must be marked "readable by automations" before this action can read it. That switch is off by default, and it is off for everything AutoTalk creates for you — channel credentials, relay signing tokens, OAuth tokens. Those are presented to third parties on your behalf, so a workflow is never allowed to read them back. Turn it on only for variables you created yourself and intend a workflow to use.
- The resolved value is not redacted anywhere. It becomes an ordinary CEL value, so it flows into any expression that names it — including a tool's output, which the agent then reads. Treat a resolved variable as visible to the run.
- A name this action cannot read fails the step. That is true whether the variable does not exist or exists without the readable-by-automations flag — the two are deliberately indistinguishable, so the action cannot be used to probe which names exist. (This changed: a missing name used to be skipped with a warning while the run carried on, which left a later expression quietly empty and blamed the wrong step.)
- Run this as one of the first steps (or as a pre-action) so the values are available everywhere after it.