Docs/Integrations/Zapier

Connect Netounim to Zapier

Forward Netounim events to any of 6,000+ Zapier apps (Google Sheets, Slack, HubSpot, Pipedrive, Notion, Airtable…) via webhooks. No code, ~5 minutes to set up.

Heads up. Netounim doesn't yet have a dedicated Zapier app in their public directory. This guide uses Zapier's built-in "Webhooks by Zapier" integration, which is free and works on every Zapier plan. A native app is on the roadmap.

Quickstart — 3 steps

Create the Zap trigger in Zapier

Sign in to zapier.com and click Create Zap.
Pick the trigger app: Webhooks by Zapier.
Trigger event: Catch Hook.
Continue → Zapier shows you a Custom Webhook URL like:
```
https://hooks.zapier.com/hooks/catch/123456/abcdef/
```
Copy that URL. Leave the Zapier tab open.

Register the webhook in Netounim

Open Settings → Webhooks.
Click Create webhook.
Paste the Zapier URL into the URL field.
Check the events you want to forward (e.g. EMAIL_REPLIED, LEAD_ADDED, BULK_COMPLETED).
Save. Netounim returns the signing secret once — copy it now, you'll need it in step 3.

Test the connection

Back in your Netounim webhook detail, click Send test event.
Switch to Zapier — the Catch Hook step should turn green and show the test payload.
Continue building your Zap: add any action app (Google Sheets, Slack, HubSpot…) and map the fields from the payload.

Done. From now on, every event you subscribed to fires the Zap.

Verify the signature (recommended)

Netounim signs every webhook delivery with HMAC-SHA256 via theX-Netounim-Signatureheader. To verify it inside the Zap, insert a Code by Zapierstep (Run JavaScript) between Catch Hook and your action.

// Inputs (configure in Code by Zapier UI):
//   secret    = your Netounim webhook signing secret
//   signature = {{header X-Netounim-Signature}}
//   body      = {{Raw Body}}

const crypto = require('crypto');

// Header format: "t=<unix-ms>,v1=<hex>"
const parts = Object.fromEntries(
  inputData.signature.split(',').map(p => p.split('='))
);
const expected = crypto
  .createHmac('sha256', inputData.secret)
  .update(`${parts.t}.${inputData.body}`)
  .digest('hex');

if (parts.v1 !== expected) {
  throw new Error('Invalid signature — possible spoofing');
}

return { verified: true };

Without this step, anyone who guesses your Zapier Catch Hook URL could fire fake events. The verification adds ~30 ms per event and is a one-time setup.

Recipe examples

EMAIL_REPLIEDSend a Slack DM to the SDR

When a lead replies to one of your campaigns, ping the SDR who created it. No more checking the inbox tab — replies come to you in Slack.

LEAD_ADDEDAppend a row to a Google Sheet

Mirror every new lead into a Google Sheet for reporting, sales-ops dashboards, or sharing with non-Zapier teammates.

BULK_COMPLETEDCreate a Notion page with the summary

When a bulk enrichment job finishes, log it as a Notion page with the count of finds / misses. Great audit trail across the team.

CAMPAIGN_SENTPush to HubSpot as a Sales Activity

Log every outbound email as a Sales Activity on the matching HubSpot contact. Closes the loop with your CRM without a native sync.

FAQ

›Does this require a paid Zapier plan?

No. Webhooks by Zapier works on every plan including Free. You'll hit Zapier's task quota if you wire high-volume events (e.g. EMAIL_OPENED on a 10k campaign = 10k tasks) — filter at the Netounim webhook level to avoid this.

›Why not a native Netounim Zapier app?

A native app means Netounim-branded triggers/actions in Zapier's search bar — better discoverability, no webhook setup. But it requires Zapier's review process (4–6 weeks) and ongoing maintenance. We'll ship one when there's demand. Today, Webhooks-by-Zapier covers the same use cases.

›What's the delivery latency?

Real-time. Netounim fires the webhook within seconds of the event (campaign sent, reply received, etc.). Zapier polls Catch Hook URLs in real-time too — total end-to-end is typically < 10 s.

›What if Zapier is down?

Netounim retries each failed delivery up to 3 times with exponential backoff (5 → 10 → 20 minutes). Beyond that, the delivery is logged as failed in Settings → Webhooks for inspection. Re-send manually if needed.

Ready to wire your first Zap?

Webhooks settings are in your dashboard.

Open Settings → Webhooks

← Back to docs Make.com guide →