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.
- Variables marked as secret are automatically redacted in log entries.
- A name that does not match any variable is skipped with a warning — the step itself does not fail, so double-check spelling when a later expression comes up empty.
- Run this as one of the first steps (or as a pre-action) so the values are available everywhere after it.