Expressions Workflow | ElevenLabs | Page 1

random steppe Dec 17, 2025, 1:01 AM

#

Can you share some covnersation ids?

earnest parrot Dec 17, 2025, 5:28 AM

#

also having this issue was this resolved on your end? also with enterprise account

quartz flax Dec 17, 2025, 5:33 AM

#

Agent: agent_4801kceyc453fpdvsqcq30a6ce5e
ConversationID: https://elevenlabs.io/app/agents/history/conv_3201kchv8xtce8zr4y5p98kjkr39

ElevenLabs

ElevenLabs Agents - Conversation history

View and analyze your ElevenLabs Agents conversation history. Review past conversations, performance metrics, and conversation transcripts to improve your AI agents.

random steppe Dec 17, 2025, 5:36 AM

#

Thanks for sharing, engs will follow up

steady aspen Dec 17, 2025, 7:27 AM

#

Hi! Sorry for the inconvenience, this is a limitation of expressions that we are actively working to fix

Generally when using expressions to move from a subagent to another node it's best to pair it with an LLM evaluation using AND (Wrap in > AND). Because even though the expression is true, the LLM still needs to decide to go in that direction, and the evaluation helps it make that decision. In other words, an expression controls whether the LLM has access to a specific path - if the expression is false, the agent is guaranteed to not go through a given path, however, if the expression is true, it does not (yet) guarantee that the LLM will immediately go through it

This is not the case when using expressions to move from a tool node, for example, where an expression being true guarantees that the workflow will go in a specific direction, as expected

We are working on making transitions from subagents work in the same, consistent way - it should be available early next month

quartz flax Dec 17, 2025, 7:41 AM

#

So if I understand this correctly:

SubAgent Node

For now wrap with the LLM eval
Does not guarantee the transition, even when the condition evaluates to true

Tool Node

Works as expected (a true expression guarantees the transition)

Can you confirm whether booleans are supported in expressions? One of the support folks told me to send the string "True" instead of a boolean true/false. Apparently there is a bug with boolean ?

quartz flax Dec 17, 2025, 3:20 PM

#

hey @random steppe What’s your recommendation for switching between subagents using LLM conditions or Using expression with LLM eval to determine which node to go?

#

like write something like this as LLM condition

Proceed to Insurance Selection when the following are true:

Insurance has NOT been selected yet during this call (initial flow)
OR
User explicitly requests to change or update their insurance

OR would you prefer i write this using expression with LLM Eval

#Expressions Workflow