One inbound URL for tools that don't have a native Pulse360 connector — Segment, Mixpanel, Delighted, Jira, and anything reachable via Zapier or Make. Send a small JSON payload and Pulse360 updates the matching account's health score. A separate read-only URL below lets those same tools pull alerts back out.
Sign up to provision your own webhook URL and secret token.
Sign up1. Your webhook URL
https://getpulse360.com/api/webhooks/e18a50af705141e2b172e8c6f0e727094a88f972ff64bf93Created 7/2/2026, 8:28:00 AM · Treat it like a password — anyone with this URL can write metrics to your accounts.
2. Wire up a tool
Pick the closest example and adapt it — every source sends the same shape: which account, which of the 5 health metrics, and a 0–100 score.
In Zapier: trigger on "New Survey Response" in Delighted, add a Formatter step to scale the 0–10 NPS score to 0–100, then a "Webhooks by Zapier → POST" action pointed at your URL above.
{
"metric_type": "sentiment",
"score": 90,
"source": "delighted",
"account_name": "Acme Corp",
"event_name": "nps_response"
}3. Try it now
Send a one-off event straight from this page against a real account, no Zapier or curl required.
4. Map a tool's native payload (optional)
Paste a real sample payload from a tool that can POST directly to a URL — Segment, most modern SaaS — and get a dedicated URL that auto-translates its fields into a health metric. Removes the Zapier/Make step above for tools that support this.
No mappings yet — map a tool's payload below to get its own dedicated URL.
5. Pull alerts out (for Zapier/Make)
A separate, read-only token — independent from the write URL above — for automations that poll Pulse360 instead of pushing into it. Returns the same 5 alert types shown in the bell menu (health drop, no contact, renewal window, urgent ticket, champion departed), each with an alert_type field to filter on downstream.
No read token yet.
Recent events
No events received yet — send a test event above or wire up a tool to see activity here.