ive set up a tool called inquiry summary that ive linked the make webhook to. i;ve also set up a structured output called call summary. #vapitomake #1211483291191083018

Thanks for sharing your setup! Could you clarify what specific issue or error you’re experiencing with the Vapi to Make integration or the call summary output? Sources: - [Vapi Integration Tools Documentation](https://docs.vapi.ai/tools) - [Vapi Structured Outputs Quickstart](https://docs.vapi.ai/assistants/structured-outputs-quickstart)

That’s a solid setup with the Inquiry Summary and structured Call Summary outputs. I can help optimize how the data flows from Vapi to Make so you get cleaner, actionable insights without extra manual work. Are you looking to automate follow-ups or just streamline reporting? Understanding your main pain point will help me suggest the most efficient approach. How often do you need these summaries generated? @Revstar

Hi this it the error i see, https://cdn.discordapp.com/attachments/1451586792816906241/1451938917472407582/image.png?ex=6947fefd&is=6946ad7d&hm=5ff0e09a97fafaab418d0d5aa9b75a6370edb5e228ae08ea09cf77f9a5d1678d&

Thanks for sharing this, it’s helpful. The call summary is coming into Make correctly, so the issue is likely with the email module setup (sender or how the data is mapped). Once that’s fixed, the same call summary can be reused for Whats App as well. I can help you clean this up and set it up properly end to end. Happy to discuss and troubleshoot this with you privately. @User

Hi Revstar, Thanks — sounds like you’re almost there. Next steps to get the email (and WhatsApp) sending the summary correctly: 1. In Make: open the scenario run history for the failing run and inspect the Webhook module’s incoming JSON sample. Confirm the path to the summary (common paths:

message.toolWithToolCallList[0].toolCall.function.arguments

or

message.toolCallList[0].arguments

). 2. If the summary arrives as a nested JSON string, add a Parse JSON / JSON > parse step in Make to convert it to fields before mapping into the Email/WhatsApp modules. 3. Map the parsed fields into your Email module body (subject/from/to must be configured in the Email module). If your Email module shows blank content, verify you mapped the correct parsed field (e.g.,

callSummary.text

or the specific key names). 4. Check the Email module error screenshot you shared for the exact failure (auth, missing sender, or invalid recipients). Common fixes: - Sender authentication: ensure SMTP/API credentials configured in the Email module are valid. - From address: use an authorized/supported sender for your email provider. - Required fields: ensure the module’s Body field is mapped to the parsed summary field, not the raw webhook object. 5. For WhatsApp: reuse the same parsed fields and map them into your WhatsApp/send message module. If WhatsApp requires a single text string, concatenate fields in Make using a Text Aggregator or Compose step. If you paste a redacted sample of the webhook JSON you see in Make (remove PII) and the exact Email module error text, I’ll point to the exact JSON path to map and the minimal parse step to add.