Skip to main content
ElromcoMoveBoard

Integrations

Webhooks — send events to your own server or Zapier

Send new leads, order changes, booked and cancelled orders, jobs and their crews, payments, tasks and notes to your own server (or Zapier, Make, n8n) the moment they happen, signed, retried, with a log and Resend.

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

Webhooks send what happens in MoveBoard to an address on your own server (or a "catch hook" of Zapier, Make or n8n) about a minute after it happens, as JSON, signed so your server can tell it really came from MoveBoard.

Nothing is sent until an admin adds an endpoint. A company that never adds one sends nothing.

Before you start

Only your company's admins can see and change webhooks, because they send your customers' names, phone numbers, emails and payments to another server. They are set per branch: each branch has its own endpoints (up to 10).

Add an endpoint

  1. Go to Settings › Integrations › Webhooks, tab Endpoints.
  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. Give it a name if you like (Zapier, our CRM…).
  4. Leave All events on, or turn it off and tick the events this endpoint should get.
  5. Press Add endpoint. Its signing secret is shown once. Copy it and give it to your developer. After that the page only shows its first and last letters.
  6. Choose an event beside Send test and press it. A test event (marked "test": true) goes to your address now, and the page says what your server answered. It carries your branch's newest real record of that kind when there is one, so your developer sees real data in the real shape.

On each endpoint: Edit (address, name, events), Switch off / Switch on, New secret (it asks first; the old secret stops signing at once), Remove (nothing more is sent; what was sent stays in the log for 30 days) and Log.

The original New-lead webhook has its own tab and works exactly as before (New-lead webhook). The Events and signing tab shows this guide's tables and code on the page.

The events

EventWhendata.objectAlso in data
lead.createda new lead comes in (website, lead provider, AI receptionist or the office)orderchannel: website, lead_provider, ai_receptionist or office
customer.createda new customer is madecustomer
order.updatedanything on an order changes: details, dates, prices, addresses, status, paymentsorder
order.status_changedan order's status changesorderfrom, to (the status before and after)
order.assignedan order is assigned to a salespersonorder
order.bookedan order is bookedorderfrom
order.cancelledan order is cancelledorderfrom
job.scheduleda job is put on the schedule: one event for each day of an order when it is bookedjob
job.rescheduleda booked order's moving date changes: one event for each of its jobsjob
job.crew_assigneda crew is assigned to a job on Dispatchjob
job.status_changeda job's status changes (en route, arrived, loading, on the way, unloading, payment, completed)jobfrom, to
job.completeda job is completedjob
payment.receiveda payment is taken on an order: deposit, card, cash, cheque, invoicepayment
payment.refundeda payment is refundedpayment (the refund)
payment.faileda card charge on an order did not go through (declined, or not charged)payment_attemptorder_id
task.createda task is madetask
task.completeda task is completedtask
note.createda note is written: by the office, the crew or the customernote

One save can raise several events (booking an order raises order.status_changed, order.booked, order.updated and one job.scheduled per day). Take only the ones you need.

What is sent

POST to your address, Content-Type: application/json, User-Agent: MoveBoard-Webhook/1.0, with these headers:

HeaderWhat it is
X-Webhook-Eventthe event type, e.g. order.booked
X-Webhook-Event-Idthe event's id. The same on every retry and every Resend, on every endpoint — use it to ignore an event you already have
Idempotency-Keythe same value as X-Webhook-Event-Id
X-Webhook-Deliverythis endpoint's delivery of the event: the same on its retries, a new one for a Resend
X-Webhook-Timestampwhen this try was signed, in Unix seconds
X-Webhook-Signaturev1= followed by the hex HMAC-SHA256 of timestamp.body with the endpoint's signing secret

The body:

{
  "id": "6f1c2a8e-6c1d-11f1-9a51-0242ac120002",
  "type": "order.status_changed",
  "api_version": "v1",
  "occurred_at": "2026-11-14T15:04:05.000Z",
  "company_id": 2,
  "branch_id": 1,
  "test": false,
  "data": {
    "from": "CAN_BOOK_ONLINE",
    "to": "BOOKED",
    "object": { "id": 12345, "number": "RES-249", "status": "BOOKED", "move_date": "2026-12-12", "customer": { "id": 881, "first_name": "Ann", "last_name": "Lee", "email": "ann@example.com", "phone": "6175550100", "other_phone": null }, "…": "…" }
  }
}
  • id is the event id (the same as X-Webhook-Event-Id). occurred_at is when it happened (UTC); data.from / data.to are as they were then.
  • data.object is the record as it is when the event is sent (about a minute later), in the same shape as MoveBoard's API. Every field is always there (null when empty).
  • company_id is your MoveBoard company, branch_id the branch the event happened in.

The objects

data.object has the same fields as MoveBoard's REST API answers for that record, so one name means one thing everywhere. Times are UTC (…Z), dates YYYY-MM-DD, money a number. Jobs, payments, tasks and notes also carry the order's customer (id, first_name, last_name, email, phone).

  • order: id, number, external_id, status, branch_id, customer (id, first_name, last_name, email, phone, other_phone), move_date, move_type, size (description, cu_ft), crew, trucks, estimate (min, max), paid, assigned_to (id, name), lead_source, created_at, updated_at, booked_at, status_changed_at.
  • customer: id, first_name, last_name, email, phone, other_phone, branch_id, account_id, orders, created_at, updated_at.
  • job (one day of a booked order): id, order_id, order_number, order_status, branch_id, date, service, arrival_window (from, to, the branch's clock), crew_arrives_at, status (NOT_ASSIGNED, ASSIGNED, RECEIVED, EN_ROUTE, ARRIVED, LOADING, TO_DESTINATION, UNLOADING, PAYMENT, COMPLETED), crew_needed, trucks_needed, crew (user_id, name, foreman, driver, status), trucks, customer.
  • payment: id, order_id, order_number, date, amount, kind (DEPOSIT or REGULAR), status (PROCESSED, PENDING, REFUND…), method (CREDIT_CARD, CASH, CHECK…), description, customer.
  • payment_attempt: id, order_id, order_number, amount, status (declined or not_charged), message (the processor's words), created_at, customer.
  • task: id, title, notes, due_at, status (open or completed), priority, kind, assigned_to (id, name), order_id, completed_at, created_at, created_by, customer.
  • note: id, content, audience (who it is for: office, crew, dispatch, customer), created_at, updated_at, created_by (id, name), order_id, customer.

Subscriptions made by apps (Zapier)

An app with an API key (Settings › Integrations › API keys) can add and remove its own subscriptions (POST /api/v1/webhooks, DELETE /api/v1/webhooks/{id}): Zapier adds one when you switch a Zap on and removes it when you switch the Zap off. They show on the Endpoints tab marked Added by an app (up to 100 per branch, apart from your own 10), are signed and retried the same way, and are removed when their address answers 410 Gone.

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 the endpoint's 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));
}

Python:

import hashlib, hmac, time

def is_genuine(raw_body: bytes, headers, secret: str) -> bool:
    ts = headers.get("X-Webhook-Timestamp", "")
    sig = headers.get("X-Webhook-Signature", "")
    if not ts or abs(time.time() - int(ts)) > 300:
        return False
    want = "v1=" + hmac.new(secret.encode(), ts.encode() + b"." + raw_body, hashlib.sha256).hexdigest()
    return hmac.compare_digest(sig, 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);

Zapier, Make and n8n "catch hooks" take the events without checking the signature; check it in a code step if you need to.

Answers, retries, Resend and switching off

  • 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, the same body every time. Then it is marked Failed.
  • A redirect is never followed. Give the final address. Every try checks the address again: one that now points to a private network is refused.
  • Log on an endpoint shows its 50 latest deliveries: when, which event, Delivered / Waiting / Failed, your server's answer, the tries and the next try. Payload shows the exact body sent. Resend sends the same event again now (same event id, new delivery id). Only the status of your server's answer is kept, never what it sent back. Events are kept 30 days.
  • An endpoint whose every try fails for 5 days is switched off, and the branch's admins get an email saying why. An answer of 410 Gone switches it off at once (Zapier's way of saying "stop"). Fix your server, press Switch on, then Resend what it missed.
  • Nothing in MoveBoard waits for your server: a save, a booking or a payment is never slowed or held back by a webhook.

Still stuck? A person will help.

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