​ To learn more, see the sources I considered: [[1] Step 3: Add transition conditions](https://docs.retellai.com/build/conversation-flow/transition-condition) [[2] Discord message from @development_org_26839 on 2025-07-04](https://discord.com/channels/1186424376300679209/1186462578310910112/1390774938679378011) ​

### Answer Yes, you can use dynamic variables inside trigger conditions for global nodes in Conversation Flow [(1) ]() . When defining transition conditions for global nodes, you have two options : 1. Prompt conditions - Natural language conditions evaluated by the LLM 2. Equation conditions - Mathematical equations using dynamic variables For equation conditions with dynamic variables, you can use syntax like :

- {{user_age}} > 18
- {{current_time}} > 9 AND {{current_time}} < 18
- {{user_location}} == "New York"
- {{user_location}} != "New York"
- "New York, Los Angeles" CONTAINS {{user_location}}
- "New York, Los Angeles" NOT CONTAINS {{user_location}}
- {{user_age}} < 18 OR {{user_location}} == "New York"
- {{name}} exists

You can only use variables that are passed in as dynamic variables for equation conditions . If you need to use information extracted by the LLM during the call, you should use prompt conditions instead . Based on community discussions, one user successfully implemented global node conditions using patterns like [(2) ]() :

{{conversation_context}} contains "GO TO Transfer Call or for eg GO TO ABC NODE"
AND {{trigger_source}} == "system"
AND {{trigger_source}} != "user"

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.

### Answer Based on the documentation, dynamic variables can be used in call transfer configurations. According to the Call Transfer Node documentation, you can set the transfer number to be either a number in e.164 format, a SIP URI, or a dynamic variable that gets substituted at runtime [(1) ]() . The documentation specifically states that you can set transfer number extension if needed, with extensions that must be 0-9, '*', '#' (e.g., 123#) . However, the documentation doesn't explicitly confirm whether dynamic variables work in the extension field specifically. Dynamic variables are documented to work in several call transfer areas [(2) ]() : - Transfer call phone numbers - Warm transfer instructions - Custom SIP header values for call transfers [(3) ]() Community discussions indicate some limitations with dynamic variables in certain transfer fields. One user reported that dynamic variables didn't work in the static "transfer to" field when using the transfer tool [(4) ]() [(5) ]() . For the extension field specifically, I don't have explicit documentation confirming dynamic variable support. If you need dynamic extension values, you may want to test this in your implementation or consider using dynamic routing instead of static routing for more flexibility with runtime values [(5) ]() .

​ To learn more, see the sources I considered: [[1] Call Transfer Node](https://docs.retellai.com/build/conversation-flow/call-transfer-node) [[2] Dynamic Variables](https://docs.retellai.com/build/dynamic-variables) [[3] Set & parse custom SIP headers](https://docs.retellai.com/build/telephony/sip-headers) [[4] Dynamic variable in "transfer to" field of transfer tool](https://discord.com/channels/1186424376300679209/1284687475364724797) [[5] transfer call function isnt working-URGENT](https://discord.com/channels/1186424376300679209/1341907616284282882) ​

Feel free to tag @AI Evy with additional questions. I also appreciate feedback, it helps me improve.