Webhooks and Zapier

Send signed events to other systems, verify signatures, understand retries, and connect Zapier with an API token.

Growth and Pro Last updated:

Webhooks send a signed message to another system the moment something happens — a new lead, a hire, a check-in, an approved leave. Zapier uses the same events to connect Manpower OS to thousands of apps without code.

Webhooks, API tokens and the Zapier app are included in the Growth and Pro plans and during the free Pro trial. Only admins can set them up.

Add a webhook

  1. Open Settings → Webhooks and press Add webhook.
  2. Enter the receiving URL. It must start with https:// and be reachable from the internet — private, loopback and internal addresses are refused.
  3. Pick the events to send, or choose All events.
  4. Save, then copy the signing secret. It is shown only once; use Rotate secret if you lose it.
  5. Press Send test to post a sample event and see the answer in the delivery log.

Events

EventSent when
employee.createdA worker is onboarded (recruited from a lead, or created through the API).
employee.updatedAn employee’s details change. changed lists the fields.
employee.deactivatedAn employee is deactivated.
lead.createdA lead or applicant is added — form, public apply page, import, Zapier or API.
lead.status_changedA lead moves between new, contacted, qualified, rejected and converted. Includes previous_status.
attendance.checked_inA worker checks in for today (app, kiosk or an attendance provider).
attendance.checked_outA worker checks out; includes the hours worked.
leave.requestedA worker asks for leave.
leave.approved / leave.rejectedA leave request is decided.
timesheet.approvedA worker’s timesheet for a period is approved.
payroll.run_finalizedA payroll run is locked. Totals only — never per-person pay.
document.expiringA passport, visa, permit, licence or other document reaches an expiry reminder (for example 60, 30 or 7 days).

Attendance days imported for dates more than two days ago are back-fills and do not send check-in events.

What a delivery looks like

Every event is an HTTP POST with a JSON body in the same shape:

{
  "id": "evt_01jabc...",
  "type": "lead.created",
  "version": 1,
  "created_at": "2026-10-14T07:30:00Z",
  "workspace": { "slug": "acme", "name": "Acme Manpower", "url": "https://acme.manpoweros.com" },
  "data": {
    "id": 57, "reference": "L-0057", "full_name": "Samuel Okafor",
    "email": "samuel.okafor@example.com", "status": "new",
    "passport_number": "******321", ...
  }
}

Passwords, tokens, bank details, dates of birth, selfies and check-in locations are never sent. Passport and ID numbers are masked to their last three characters. Use id to ignore an event you have already processed.

Verify the signature

Each request carries three headers:

HeaderValue
X-ManpowerOS-EventThe event type, e.g. leave.approved.
X-ManpowerOS-DeliveryA unique delivery id (dlv_…), the same on every retry.
X-ManpowerOS-Signaturet=<unix time>,v1=<hex> — HMAC-SHA256 of <t>.<raw body> with your signing secret.

Check the signature on the raw request body, before parsing it, and reject timestamps older than five minutes.

PHP

$secret = getenv('MANPOWEROS_WEBHOOK_SECRET');
$body   = file_get_contents('php://input');
$header = $_SERVER['HTTP_X_MANPOWEROS_SIGNATURE'] ?? '';

parse_str(str_replace(',', '&', $header), $sig);   // ['t' => ..., 'v1' => ...]
$expected = hash_hmac('sha256', ($sig['t'] ?? '') . '.' . $body, $secret);

if (empty($sig['v1']) || ! hash_equals($expected, $sig['v1']) || abs(time() - (int) $sig['t']) > 300) {
    http_response_code(400);
    exit;
}
$event = json_decode($body, true);
// ... handle $event['type'] and $event['data'] ...
http_response_code(200);

Node.js (Express)

const crypto = require('crypto');
const express = require('express');
const app = express();

app.post('/webhooks/manpoweros', express.raw({ type: 'application/json' }), (req, res) => {
  const header = req.get('X-ManpowerOS-Signature') || '';
  const parts = Object.fromEntries(header.split(',').map(p => p.split('=')));
  const expected = crypto.createHmac('sha256', process.env.MANPOWEROS_WEBHOOK_SECRET)
    .update(parts.t + '.' + req.body.toString('utf8'))
    .digest('hex');

  const ok = parts.v1 && parts.v1.length === expected.length &&
    crypto.timingSafeEqual(Buffer.from(parts.v1), Buffer.from(expected)) &&
    Math.abs(Date.now() / 1000 - Number(parts.t)) < 300;
  if (!ok) return res.sendStatus(400);

  const event = JSON.parse(req.body.toString('utf8'));
  // ... handle event.type and event.data ...
  res.sendStatus(200);
});

Retries and the delivery log

Answer with any 2xx status within 10 seconds. Anything else — an error status, a timeout or a redirect — is retried after 1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours, then marked failed. Redirects are never followed: use the final URL.

  • The Delivery log shows every attempt for 30 days: event, status code, attempts, time taken, the last error and the exact payload. Redeliver sends an event again.
  • After 20 failed deliveries in a row the webhook is turned off automatically and admins get a notification. Fix the receiver, then turn it back on.
  • Answering 410 Gone turns the webhook off straight away — useful when the receiving side is retired.
  • Sending never slows anyone down: events go out in the background after the page has loaded.

Connect Zapier

  1. Open Settings → API tokens & Zapier and create a token. Keep all permissions ticked for Zapier, and copy the token.
  2. In Zapier, search for Manpower OS, pick a trigger (for example New Lead) or an action (for example Create Lead).
  3. When Zapier asks you to connect, enter your workspace address — acme or acme.manpoweros.com — and paste the token.
  4. Turn the Zap on. Zapier adds its own webhook automatically; you will see it on the Webhooks page tagged Zapier, and it disappears when you turn the Zap off.

Zapier can also create leads, create employees (onboarded through the normal recruit flow, so your plan’s worker limit applies) and find an employee by employee number, email or phone.

API tokens for your own tools

The same tokens work with any HTTP client: send Authorization: Bearer <token> to https://<workspace>.manpoweros.com/api/v1. A token acts as the admin who created it, only works on its own workspace, is limited to 120 requests a minute, and stops working when revoked or when that admin is deactivated. Revoke also removes the token’s Zapier webhooks.

Was this helpful?

Related articles