hy guys. i made my own algorithmus for meeting planing with make.com and i give back possible dates as a json. i can see the json in the chat and in the logs when i call. i made a message which is triggerd when the webhook_call is done. how can i add the possible dates in this message? something like: "Available dates are: XXX" how can i do this? thanks markus

Hi Markus! 👋 I see you're trying to add dates from your webhook JSON response into a message in Make.com. While I can't provide exact step-by-step instructions for your specific Make.com interface, I can definitely help with the approach! Based on the information I found, here's how you can add those dates to your message: ### 1. Understanding Your Webhook Response Structure First, you need to understand the structure of your JSON response. Typical webhook responses in Make.com look like this:

json
{
  "results": [
    {
      "toolCallId": "call_choKmdslU31UJDabum0UVYIT",
      "result": [
        {
          "start_date": "2025-02-18",
          "end_date": "2025-02-21"
        }
      ]
    }
  ]
}

Or sometimes like this:

json
{
  "results": [
    {
      "toolCallId": "call_g4LBH87kQ7fmcKFbcVaKKlLV",
      "result": "These are all available slots: {\"2025-02-21\":[{\"start\":\"2025-02-21T08:30:00.000Z, 2025-02-21T08:45:00.000Z\"}]}"
    }
  ]
}

### 2. Accessing the Data in Make.com When your webhook is triggered, Make.com receives this JSON data. According to the [information I found](https://discord.com/channels/1211482211119796234/1211483291191083018/threads/1340737584309211136), "in Make.com I can see that the webhook response had a full **result**", which means your date data is available in the scenario. ### 3. Parsing the JSON and Adding to Your Message To add the dates to your message: 1. In your Make.com scenario, after the webhook module, add a JSON Parse module or use the built-in data mapping functions to extract the dates from the response. 2. If your dates are in the

result

field, you'll need to access them using the appropriate mapping. For example, if using the first JSON structure above, you might reference something like:

{{1.results[0].result[0].start_date}}

(the exact syntax depends on Make.com's current data mapping format).

this is my response. { "results": [ { "result": "[{\"terminvorschlag\":\"2025-04-14T08:00:00+02:00\"},{\"terminvorschlag\":\"2025-04-14T08:15:00+02:00\"},{\"terminvorschlag\":\"2025-04-14T08:30:00+02:00\"},{\"terminvorschlag\":\"2025-04-14T08:45:00+02:00\"},{\"terminvorschlag\":\"2025-04-14T09:00:00+02:00\"},{\"terminvorschlag\":\"2025-04-14T09:15:00+02:00\"},{\"terminvorschlag\":\"2025-04-14T09:30:00+02:00\"},{\"terminvorschlag\":\"2025-04-14T09:45:00+02:00\"},{\"terminvorschlag\":\"2025-04-14T10:00:00+02:00\"},{\"terminvorschlag\":\"2025-04-14T10:15:00+02:00\"}]", "tool_call_id": "call_YxPWICufB3LZXBW7WL6SHX4Y" } ] }

Hey! To help track down this issue, could you share: - The call ID - When exactly this happened (the timestamp) - What response you expected to get - What response you actually got instead This would really help us figure out what went wrong!

i cannot give you a call id because it was in chatmode

Remove the "Request complete" message from your tool messages property array. if request complete message exists or selected in for your tool messages then VAPI uses this message to convey the tool call response, not your tool call result. That's why it doesn't get voiced out after the tool call is resolved.  just remove this request complete message, and then your tool call response will be used to generate the assistant's next response.

no it is not happening https://cdn.discordapp.com/attachments/1356366481021206813/1356865018376749096/image.png?ex=67ee1e85&is=67eccd05&hm=0963b8012846a9b4a1333705e0e1766d33f0482628818ac1284548fd7ea6aa38&

Hi, checking if this is resolved/solved for you?

I'm having the same issue! The caller needs to engage to get the tool result from the webhook response. Vapi agent just stays silent if not engaged about the result

Hey, Koiti, a gentle reminder for you to continue this thread.