Send to other apps (Zapier, Make)

Send to other apps tells Zapier or Make about new customers, booked jobs, finished calls and more, and they pass it on to Google Sheets, Slack, Jobber, Housecall Pro and thousands more. Set it up on Settings › Send to other apps (developers call these webhooks).

Owners and Admins only, on Pro, Business or Enterprise. On Starter the page shows an upgrade card and older connections stay paused. Webhooks by Zapier needs a paid Zapier plan (Professional or higher) or trial. Make’s free plan includes webhooks.

What we can send

You pick the moments. They come from every channel, never from sample customers or demo data.

Connect Zapier

1. 1

   In Zapier, make a Zap with the trigger Webhooks by Zapier and the Event Catch Hook. Select Continue twice, leaving Pick off a child key empty. On the Test tab, copy the URL starting https://hooks.zapier.com/.

2. 2

   On Settings › Send to other apps, select Connect an app, Zapier and Next. Paste the URL into Paste the address from Zapier and select Next. If you have several, rename it from Zapier.

3. 3

   Tick the moments you want, select Save and continue, then Send a sample.

   It worked. Zapier got the sample. It’s a made-up customer, Sam Sample.

4. 4

   In Zapier, select Test trigger, add your action and publish the Zap.

Connect Make

1. 1

   In Make, start a scenario with the Webhooks app’s Custom webhook. Next to Webhook, select Add, name it, select Save and copy the address (https://hook.us1.make.com/…).

2. 2

   On Settings › Send to other apps, select Connect an app and Make, paste the address and select Next.

3. 3

   Tick the moments you want, select Save and continue, then Send a sample while Make is waiting for data.

   It worked. Make got the sample.

4. 4

   Add your next modules and switch the scenario on.

Ready-made setups

Each starts from a connection with its moment ticked and a sample sent.

New customers into a Google Sheet

1. Connect with A new customer reaches out, and make a sheet with the columns below.
2. Zapier: add Google Sheets → Create Spreadsheet Row. Make: add Google Sheets → Add a Row (its fields are under data → lead).
3. Map each column to its field:

Text your on-call tech on emergencies

1. Connect with only A customer has an emergency, so routine jobs wake nobody.
2. Text your tech’s number with SMS by Zapier or a Twilio “send a message” step.
3. Message: “Emergency: {customer name}, {customer phone}, {service needed}. {dashboard url}”.

Booked jobs into Jobber or Housecall Pro

1. Connect with A job is booked, and A job is moved and A job is cancelled if wanted.
2. Add the Jobber or Housecall Pro action that creates a client or job (names differ, so check each app’s Zapier or Make listing).
3. Map the start from Data Appointment Start (or Data Appointment Start Display, written out in your time zone), the service from Data Appointment Service Type, and the customer from Data Lead Customer name, phone and address.

New customers into Slack, Teams or Google Chat

1. Connect with A new customer reaches out, plus A customer asks for a person if your team should step in.
2. Add Slack → Send Channel Message, or a Microsoft Teams or Google Chat message.
3. Message: “New customer: {customer name} needs {service needed}. {dashboard url}”.

Check it’s working

Open a connection on Settings › Send to other apps. Its top line says how it’s doing.

Activity marks each message Sent, Trying again, Gave up, Queued or Waiting (paused). Details shows What we sent and What they answered. Resend repeats one, and Resend everything that failed repeats all that gave up.

If the other app is down

Nothing is lost. We retry for about 3 days, less and less often, emailing you at most once a day. After that, or once the other app says the address is gone, we pause the connection, hold new moments and email you. Resume sends what was held, up to 3 days old.

Edit, turn off or delete a connection

To turn a connection off without losing it, use the switch on its page, and turn it back on to send again. Edit changes the name, address or moments, never the signing secret. Delete removes it and its activity, not your Zap or scenario.

For developers

Each moment is an HTTPS POST with a JSON body. Any 2xx within 30 seconds counts as received, and redirects aren’t followed. Dedupe on id, which retries and Resend repeat. isTest is true for samples.

{
  "id": "6f1c2a8e-0d4b-4f7e-9a51-3c2b7d9e1f04",
  "type": "lead.created",
  "apiVersion": "1.0",
  "occurredAt": "2026-11-04T16:02:11.000Z",
  "isTest": false,
  "businessId": "2b7e…",
  "entityType": "Lead",
  "entityId": "9d3f…",
  "correlationId": null,
  "data": {
    "lead": {
      "id": "9d3f…",
      "createdAt": "2026-11-04T16:00:41.000Z",
      "status": "New",
      "channel": "phone",
      "customer": { "name": "Sam Sample", "phone": "+15555550123", "email": "sam@example.com" },
      "address": { "line": "12 Main St", "city": "Riverside", "state": "CA", "zip": "92501" },
      "serviceNeeded": "Water heater leaking",
      "urgency": "high",
      "isEmergency": false,
      "preferredTime": null,
      "summary": "Water heater in the garage is leaking. Wants someone tomorrow morning.",
      "dashboardUrl": "https://intakenexus.com/dashboard/leads/9d3f…"
    }
  }
}

The signature is the lowercase hex HMAC-SHA256 of <t>.<raw body>, keyed with the signing secret as UTF-8 text, whsec_ prefix included. Verify the raw body before parsing and reject old timestamps. The secret shows once, when you connect Another app or select Make a new secret under Advanced (for developers).

import crypto from 'node:crypto';

// rawBody: the request body exactly as it arrived (a string, BEFORE JSON.parse).
// header:  the X-Webhook-Signature header. secret: your signing secret (whsec_…).
export function isFromIntakeNexus(rawBody, header, secret, toleranceSeconds = 300) {
  const parts = header.split(',');
  const t = parts.find((p) => p.startsWith('t='))?.slice(2);
  const signatures = parts.filter((p) => p.startsWith('v1=')).map((p) => p.slice(3));
  if (!t || signatures.length === 0) return false;
  if (Math.abs(Date.now() / 1000 - Number(t)) > toleranceSeconds) return false;

  const expected = crypto.createHmac('sha256', secret).update(`${t}.${rawBody}`, 'utf8').digest('hex');
  // During the 24 hours after "Make a new secret" there are two v1= values: accept either.
  return signatures.some(
    (s) => s.length === expected.length && crypto.timingSafeEqual(Buffer.from(s), Buffer.from(expected)),
  );
}

import hashlib
import hmac
import time

def is_from_intakenexus(raw_body: bytes, header: str, secret: str, tolerance_seconds: int = 300):
    parts = header.split(",")
    t = next((p[2:] for p in parts if p.startswith("t=")), None)
    signatures = [p[3:] for p in parts if p.startswith("v1=")]
    if t is None or not signatures:
        return False
    if abs(time.time() - int(t)) > tolerance_seconds:
        return False

    signed = f"{t}.".encode("utf-8") + raw_body
    expected = hmac.new(secret.encode("utf-8"), signed, hashlib.sha256).hexdigest()
    # Two v1= values while a new secret is being swapped in: accept either.
    return any(hmac.compare_digest(s, expected) for s in signatures)

Retries come after about 1 minute, 5 minutes, 30 minutes, 2 hours, 5 hours, 10 hours, 24 hours and 24 hours. A 4xx other than 408 or 429 isn’t retried. A 410 pauses the connection at once.

Troubleshooting