Custom Function (GET) not receiving arguments from Extract Variables node

Support Help
2

Based on the documentation and community discussions, there’s a known issue with how dynamic variables work in Custom Functions with GET requests in Conversation Flow.

The Root Cause:

When you extract variables using the Extract Dynamic Variables node, those variables are saved to the session context(1). However, for Custom Functions with GET requests, there’s a specific configuration requirement for query parameters(2).

The Solution:

In your Custom Function’s Query Parameters section, you need to configure both the parameter description AND ensure the variable is properly referenced. Based on community troubleshooting, try this approach(3)(4):

  1. In the Query Parameters section, set:

    • Key: task
    • Description: Use this as the task id: {{task}}(3)

  2. Make sure the Extract Variables node runs before your Custom Function node in the flow(5)

  3. Verify the variable name matches exactly (case-sensitive) between extraction and usage(5)(4)

Important Notes:

  • Query parameters can include dynamic variables, and there’s a switch to change between parameter description or const value(2)
  • Both description and const value can use dynamic variables(2)
  • The description will be resolved by the LLM while const value will be applied directly to the function(2)

Verification:

After making these changes, check your call logs. You can verify if the variable was properly extracted by looking at the collected_dynamic_variables field in your call details(6)(5).

If the issue persists after these adjustments, the call logs should show whether the variable has a value when the tool is invoked(5).