Skip to main content
ElromcoMoveBoard

Integrations

Webhook — send leads to your own server

Send every new lead to your own server the moment it comes in, as signed JSON, with retries and a send log, and how your developer checks the signature.

  • 5 min read
  • Checked against MoveBoard
  • For owners & admins
On this page

The new-lead webhook sends every new lead to an address on your own server (or a tool like Zapier or Make that gives you one) about a minute after it comes in, as JSON, signed so your server can tell it really came from MoveBoard.

It is off until an admin saves an address and switches it on. A company that never sets it up sends nothing.

For more events (order changes, bookings, jobs, payments, tasks, notes) and several addresses, use Webhooks endpoints. The new-lead webhook keeps its own format and works exactly as before.

Before you start

Only your company's admins can see and change it, because it sends your customers' names, phone numbers and emails to another server. It is set per branch.

Set it up

  1. Go to Settings › Integrations › Webhooks, tab New-lead webhook.
  2. Type your server's address. It must start with https:// and be a public internet address. IP addresses, localhost and internal network names are refused.
  3. Turn on Send new leads and press Save.
  4. The first save makes your signing secret and shows it once. Copy it and give it to your developer. After that the page only shows its first and last letters.
  5. Press Send test. A sample lead (marked "test": true) goes to your address now, and the page says what your server answered.

New secret makes a new signing secret (it asks first). The old one stops signing at once.

Which leads are sent

Every new lead of the branch: from your website's quote forms and your own website form, lead providers and the lead API (Angi too), the website chat, the AI receptionist (once the call ends), customers asking for a new move in their account, and leads the office makes (New order, quick lead). The payload's channel says which: website, lead_provider, ai_receptionist or office.

Not sent: imported orders, a copy (clone) of an order, the move-out order made beside a moving-and-storage lead, and a blank New order with no customer.

What is sent

POST to your address, Content-Type: application/json, with these headers:

HeaderWhat it is
X-Webhook-Eventlead.created (or webhook.test for Send test)
X-Webhook-Deliverythis lead's delivery id. It is the same on every retry, so use it to ignore a lead you already have
Idempotency-Keythe same value as X-Webhook-Delivery
X-Webhook-Timestampwhen this try was signed, in Unix seconds
X-Webhook-Signaturev1= followed by the hex HMAC-SHA256 of timestamp.body with your signing secret

The body:

{
  "event": "lead.created",
  "id": "3b1f0c2e-6c1d-11f1-9a51-0242ac120002",
  "sentAt": "2026-11-13T15:04:05.000Z",
  "company": { "branchId": 1, "name": "Your company" },
  "lead": {
    "orderId": 12345,
    "orderNumber": "RES-249",
    "status": "NEW",
    "createdAt": "2026-11-13T15:03:58Z",
    "channel": "website",
    "leadSource": "Google",
    "customer": { "firstName": "Ann", "lastName": "Lee", "name": "Ann Lee", "phone": "6175550100", "email": "ann@example.com" },
    "moveDate": "2026-12-12",
    "moveDateDecided": true,
    "from": { "address": null, "city": "Boston", "state": "MA", "zip": "02134" },
    "to": { "address": null, "city": "Newton", "state": "MA", "zip": "02458" },
    "toZipDecided": true,
    "service": "Local Moving",
    "moveType": "RESIDENTIAL",
    "moveSize": "2 Bedroom Apartment",
    "url": "https://app2.elromco.com/orders/12345?c=99"
  }
}
  • id is the delivery id (the same as the header).
  • moveDate is YYYY-MM-DD. When the customer chose Not sure yet on your quote form (optional moving date and To ZIP), moveDate is null and moveDateDecided is false. A To ZIP not decided gives to: null and toZipDecided: false. You never get the stand-in values.
  • phone is digits only. email, phone, leadSource, service, moveSize and the addresses' fields can be null.
  • url opens the order in MoveBoard (for your staff; it needs a sign-in).

Check the signature

Your server should check every request before trusting it:

  1. Take the raw request body exactly as received (before parsing it).
  2. Compute HMAC-SHA256 of X-Webhook-Timestamp + . + body with your signing secret, as lowercase hex.
  3. Compare v1= + that hex with X-Webhook-Signature in constant time.
  4. Refuse a timestamp more than 5 minutes from your clock, so an old request can't be replayed.

Node.js:

const crypto = require("crypto");
function isGenuine(rawBody, headers, secret) {
  const ts = headers["x-webhook-timestamp"];
  const sig = headers["x-webhook-signature"] || "";
  if (!ts || Math.abs(Date.now() / 1000 - Number(ts)) > 300) return false;
  const want = "v1=" + crypto.createHmac("sha256", secret).update(`${ts}.${rawBody}`).digest("hex");
  return sig.length === want.length && crypto.timingSafeEqual(Buffer.from(sig), Buffer.from(want));
}

PHP:

$ts = $_SERVER['HTTP_X_WEBHOOK_TIMESTAMP'] ?? '';
$sig = $_SERVER['HTTP_X_WEBHOOK_SIGNATURE'] ?? '';
$body = file_get_contents('php://input');
$want = 'v1=' . hash_hmac('sha256', $ts . '.' . $body, $secret);
$ok = abs(time() - (int)$ts) <= 300 && hash_equals($want, $sig);

Answers, retries and the send log

  • Answer with any 2xx status within 10 seconds. Do slow work after you answer.
  • Anything else (another status, a redirect, no answer in time, the address not reachable) is tried again 1, 5, 15 and 40 minutes later: 5 tries over about an hour. Then it is marked Failed.
  • A redirect is never followed. Give the final address.
  • Every try is checked again: an address that now points to a private network is refused.
  • A lead is never held back or slowed down by the webhook. The customer and your office get everything as usual even when your server is down.
  • Send log on the page shows the 25 latest sends: when, which lead, Delivered / Waiting / Failed, your server's answer, the tries and the next try. Only the status of your server's answer is kept, never what it sent back.

Still stuck? A person will help.

Open a ticket from Support inside MoveBoard, or email us — we usually reply within one business day.