The Dynamic Duo: Custom and Response Webhooks in Make.com

Custom webhooks and response webhooks are two powerful tools that, when combined on Make.com, can enhance your scenario functionality significantly. Imagine creating a lead capture form on Make.com, featuring fields for name, phone number, email, and comments without any additional tools.

First, let's understand basically how they work:

Webhooks empower you to transmit data to Make via HTTP. By generating a unique URL, webhooks enable external applications, services, or other Make scenarios to interact with your platform. Leverage webhooks to initiate the execution of specific scenarios.

Typically, webhooks function as instantaneous stimuli. In contrast to scheduled triggers that routinely query a service for fresh data to process, webhooks promptly activate the scenario as soon as the webhook URL registers a request.

Let's set up a new scenario using the Custom Webhook module. When you do this, a new URL will be generated. Save your scenario, copy the URL, and paste it into your browser's address bar, then hit enter. Typically, the response from the webhook will be an HTML message with a 200 OK status, typically shown as "Success".

Now that we have Batman, let's bring Robin into action. Connect a Webhook Response module to the webhook and configure the body. Use a simple JSON format like this:

{
  "hasaccess": {{true}},
  "clientid": "001",
  "description": "has access"
}

Now, access the webhook URL again. What do you see? While it may not be magic on its own, there's a lot of potential for doing magical things with this configuration.

The real strength of using both Custom and Response Webhooks lies in their ability to create seamless, interactive workflows that transcend the limitations of static automation. You can place numerous other modules between a custom webhook and a webhook response to craft fascinating combinations — from speech-to-text automation to generating PDFs in Make. Here's how you can leverage this dynamic duo:

1. Advanced AI Interactions: After a ChatGPT assistant processes a request with OpenAI function calling, you can integrate its response seamlessly into your workflow. Imagine the possibilities of real-time AI interaction, providing users immediate assistance or insights.
2. Dynamic Webpage Creation: You can place an entire dynamic webpage within a webhook response, enabling users to interact with it directly. Button clicks and form submissions can be sent to other webhooks, creating an interactive and fluid user experience that's both engaging and efficient.
3. Custom API Endpoints: With this powerful combination, you can even craft your own API endpoints. Enable authentication and provide secure access to your services, filling the gaps where pre-built solutions fall short. The flexibility of this setup ensures your system integration capabilities are virtually limitless.
4. Smart Home Automation with Real-Time Weather Alerts: Combine webhooks with smart home devices and weather APIs to make your home responsive to changing weather conditions. A custom webhook receives real-time updates from a weather API, and when significant events like sudden temperature drops or heavy rain are detected, it triggers automated actions. A Webhook Response can keep you informed of these adjustments, ensuring a seamless integration that enhances comfort and peace of mind.
5. Bee Colony Health Monitoring through Audio Analysis: Use webhooks to monitor the health of bee colonies by analyzing their buzzing sounds, providing invaluable insights into hive conditions. Audio data from bee hives is transmitted via a custom webhook and processed using AI-powered sound analysis tools within Make. By detecting sound patterns indicative of health or stress levels, the system can alert beekeepers to any irregularities. This setup allows for real-time updates on hive health, with the potential to automate data visualization on a dashboard. A Response Webhook can notify beekeepers of trends or potential issues, aiding in proactive hive management and conservation efforts. (I went a bit too creative with this one :) )

I would love to read your comments and suggestions for a practical, real-life project. I'm more than happy to take on the challenge and outline the steps here in detail.

Frequently asked questions

How do you return a response from a Make.com webhook?

Add a Webhook Response module at the end of a scenario that begins with a Custom Webhook. Set the status code (usually 200) and define the body — for example a JSON payload. When someone calls the webhook URL, Make sends that content straight back to them instead of the default "Accepted" message.

What is a webhook response in Make?

A webhook response is the reply Make sends back to whoever triggered a Custom Webhook. With the Webhook Response module you control the exact status code, headers and body, so your scenario can return real data — JSON, HTML or plain text — rather than simply acknowledging that it received the request.

Can Make.com act as an API endpoint?

Yes. By pairing a Custom Webhook that receives the request with a Webhook Response module that returns the result, you can place any processing modules in between and expose the whole scenario as a working API endpoint that accepts input and returns a structured response.