----------------------------- **While I generate an answer, here are some sources that might be helpful**: * [Set up your Server URL]() * [Call Functions]() * [Create Assistant]() * [Pizza Website Example]() -----------------------------

### Answer When setting up function calling with Vapi and integrating with Zapier, it's important to ensure that the payload from Vapi is structured in a way that Zapier can recognize and parse the parameters you're interested in. Vapi sends

POST

requests to your Server URL with a specific body structure, including

type

,

call

object, and other relevant properties [(1)]() . You should verify that the structure of the data sent by Vapi matches what Zapier expects to receive in the webhook trigger. If Zapier is capturing the raw payload but not parsing it as expected, consider using Zapier's custom code options (like Code by Zapier) to manually parse the raw body of the incoming request. You might need to write a small script that extracts the specific parameters from the raw JSON payload. Additionally, ensure that your Server URL in Vapi is correctly set up to point to the Zapier webhook URL and that there are no discrepancies in the expected data format. For more advanced setups, you might explore the possibility of custom functions within Vapi to format the data in a way that's immediately usable by Zapier [(2)]() . Remember, Vapi allows the definition of custom functions, and with proper configuration, you can tailor the outgoing requests to meet your requirements.

Got it. Tagging @User for additional help.