Hey! I’ve handled similar Vapi workflow issues before — that “N/A” usually means the extracted variables aren’t being passed or mapped correctly from the conversation. I can help review your extraction setup, structured output schema, and workflow connections to trace where it’s failing. Sometimes the variable names or JSON paths cause silent breaks. Did you define those variables in the assistant’s structured output or only within the workflow node? @Nuri