I am having an issue with my workflow that I created (workflow id: 323e8d08-6c4f-43f4-b6eb-55c040eba4d0, call id: 5637e18e-00ab-4e31-b29c-07dd6b05ce6a, account: ryan@degrootent.com). I have the flow set up to collect data from the user being called via the variable extraction feature. I have very specific definitions and enums set, and in my testing I make sure to speak very slowly and clearly. However when I check the call log, there are no variables extracted from the conversation ( the ones you can use with {{ }}). I tried testing if I wrote my flow wrong by using the template provided, and it also did not display any extracted variables from the conversation. I also tried using a api call (while the workflow is in progress) to a endpoint I own with a {{ variable }} as the payload, and it sent an empty string. I am not sure if I am looking in the wrong place for these variables, or if they are only stored during execution of the workflow. Any assistance would be appreciated. https://cdn.discordapp.com/attachments/1381671623874183260/1381671624217989201/Screenshot_2025-06-09_112844.png?ex=68772ab9&is=6875d939&hm=0a098950fe788143296daaa65bc7dfc52742be33e5b3cfcfa523b7db534470f3&

Suggestion: Double-check that your Gather node is correctly configured with the variable names, data types, and marked as required if needed. If variables are still not appearing in your call logs or API payloads, try creating a minimal test workflow with a single Gather node and simple variable (e.g.,

first_name

as a string) to isolate the issue. If the problem persists, it may be a platform issue—consider reaching out to [Vapi support](https://docs.vapi.ai/support) with your workflow and call IDs for further investigation. Sources: - [Gather Node Documentation](https://docs.vapi.ai/workflows/nodes/gather) - [Workflows Quickstart](https://docs.vapi.ai/workflows/quickstart) - [Vapi Support](https://docs.vapi.ai/support)

the gather node link you proivded for documentation returns a page not found

Here is a link to the documentation with a fixed link:

Was this fixed?

@np are you encountering issues with extracted data from the conversation node? If so, please explain how you are encountering this.