Make.com webhook module

Wire Zenovay events into Make.com (formerly Integromat) scenarios — connect to Google Sheets, Airtable, HubSpot, Microsoft 365, Salesforce, and 1500+ other apps.

Make.com's Webhooks → Custom webhook module is what catches Zenovay events.

---

1. Create the Make.com webhook

1. In Make.com, create a new scenario.
2. Click the + button → search "Webhooks" → pick Webhooks → Custom webhook.
3. Click Add to create a new webhook hook:
   • Webhook name: Zenovay events (or anything memorable)
   • IP restrictions: leave empty unless you're locking down Zenovay's IPs (we don't publish a stable IP list — verify via signature instead)
   • JSON pass-through: leave off (Make.com will parse the body automatically)
4. Click Save and Copy address to clipboard — looks like https://hook.eu2.make.com/abcdef123456.

---

2. Add the webhook in Zenovay

1. In app.zenovay.com, go to Settings → Webhooks.
2. Pick the website that should fire events.
3. Click Add webhook.
4. Fill in:
   • Name: Make.com — <scenario name> (e.g. Make.com — Sync to Google Sheets)
   • URL: paste the Make.com webhook address from Step 1
   • Events: pick the ones the scenario should react to
5. Click Create webhook.
6. Click Send test event (paper-plane icon).

---

3. Pick up the sample data in Make.com

1. Back in the Make.com webhook module, click Run once at the bottom.
2. Make.com listens for the next incoming event. Click Send test event in Zenovay again.
3. Make.com captures the payload and shows the available fields. Click Save.
4. Add the next module(s) — e.g. Google Sheets → Add a Row — and map fields from the Zenovay payload.

---

4. Verify Zenovay's signature (recommended)

Make.com does NOT natively verify HMAC signatures. For scenarios where signature integrity matters, add a Tools → Set Variables module with this filter:

// In a "Filter" between the webhook and your action modules
{{contains(headers["x-zenovay-signature"]; "sha256=")}}

For full HMAC verification, you'd need to either:

1. Upgrade to a custom-code module (Make.com Premium / Pro plan), or
2. Front Make.com with a Cloudflare Worker that verifies and forwards:

import { createHmac } from 'crypto';

export default {
  async fetch(req) {
    const rawBody = await req.text();
    const signature = req.headers.get('x-zenovay-signature') || '';
    const provided = signature.replace(/^sha256=/, '');
    const expected = createHmac('sha256', YOUR_WEBHOOK_SECRET)
      .update(rawBody)
      .digest('hex');

    if (provided !== expected) return new Response('invalid signature', { status: 401 });

    await fetch(MAKE_WEBHOOK_URL, {
      method: 'POST',
      headers: { 'Content-Type': 'application/json' },
      body: rawBody,
    });
    return new Response('ok');
  },
};

Your webhook secret is shown in Settings → Webhooks → click the eye icon on the webhook card.

---

5. Common scenario recipes

---

Troubleshooting

• Webhook received the data but the scenario didn't execute: the scenario must be active (toggle in the bottom-left corner of the scenario editor).
• Field types are wrong (e.g., a number arrives as text): toggle JSON pass-through OFF on the webhook module so Make.com parses types automatically.
• Operations limit hit: Make.com counts each scenario step as one operation. Free tier = 1,000/month. Filter chatty events (like traffic_spike) in the Zenovay webhook config to stay under the limit.

---

Related

• Zapier catch-hook recipe
• n8n webhook trigger recipe
• Webhook reference & payload schema