Hello guys, do we know if workflows support SIP headers ? Because it seems that only the assistant is able to fill the dynamic variables based on the SIP headers And the workflows do not 76e0f5fb-8340-43d3-9557-74e8c9819b01

Workflows do not natively support SIP headers for dynamic variables only Assistants can auto-fill them via

assistantOverrides.variableValues

, so to use SIP headers in a Workflow, you must route the call through an Assistant webhook that injects the variables.. [https://docs.vapi.ai/advanced/sip](https://docs.vapi.ai/advanced/sip?utm_source=chatgpt.com) [https://docs.vapi.ai/workflows/overview](https://docs.vapi.ai/workflows/overview?utm_source=chatgpt.com)

Ok thank you very much, let me see if we can integrate this in our work flow

Vapi workflows don’t auto-populate [customer.phone](http://customer.phone) from SIP INVITE headers, only Assistants do via assistantOverrides, so to set the caller’s number like From: or X-Lead-\* headers, you’ll have to handle it in an Assistant webhook and pass it manually as a variable..

Thanks

Hello, Thanks for patiently waiting. Vapi workflows currently don’t auto-populate the

customer.phone

field from the SIP INVITE headers. This behavior is only available when using Assistants, since they can parse those headers through

assistantOverrides

. If you need to capture the caller’s number (for example, from the

From:

header or custom headers like

X-Lead-*

), the way to handle this is through an Assistant webhook. In the webhook, you can extract the caller information from the SIP INVITE headers and then pass it manually into your workflow as a variable. In other words: - Workflows = no automatic mapping from SIP headers →

customer.phone

. - Assistants = can override and pull that info with

assistantOverrides

. - Solution = use a webhook to grab the header data yourself and inject it into the workflow. Let us know if you need further assistance.

Hello, can you help me and explain how to create a webhook to grab the header data yourself and inject it into the workflow?