@JM It's great to hear that you've successfully set up the 'catch' custom webhook trigger in Zapier and are capturing the necessary information from Airtable. To pass the information back to VAPI, you're correct that you would typically use a POST request. However, you should not send the results to the same URL as your catch hook to avoid creating a loop. Instead, you should send the results to the callback URL provided by VAPI when the initial tool call was made. This callback URL is unique for each tool call and is designed to receive the results of the operation. It's how VAPI knows that the tool has completed its task and can process the results accordingly. Here's what you need to do: 1. Capture the callback URL from the initial request that VAPI sends to your Zapier webhook. 2. After processing the information from Airtable, use a Zapier action to make a POST request to the captured callback URL. 3. Format the POST request's body to match the expected JSON response structure that VAPI requires, which you've mentioned in the context. For example, the JSON response should look like this:

json
{
    "results": [
        {
            "toolCallId": "<unique_tool_call_id>",
            "result": "<your_processed_result>"
        }
    ]
}

Replace

<unique_tool_call_id>

with the ID you received from the initial VAPI request, and

<your_processed_result>

with the actual result you want to send back. If you're unsure about how to capture the callback URL or format the POST request in Zapier, please ask support for more info on this. Zapier's support or community forums can be a valuable resource for specific guidance on setting up the action steps in your Zap.

You can continue this conversation by mentioning me in the message.