Webhooks
Set up outbound webhook endpoints so your systems react to Pivotal events.
Webhooks let Pivotal push events to your own systems the moment something happens. A customer flips to at-risk, your warehouse loads a row. A task is completed, your QBR tool updates the slide. Pivotal handles the delivery, signing, retries, and replay; you handle what to do with the payload.
This page covers the end-user setup of an endpoint inside Pivotal. For the developer spec (event catalog, payload shapes, signature verification), open the Webhooks overview.
Endpoints live at Admin > Developer > Webhooks. The page is split into Live and Test so you can wire a staging URL alongside production without crossing them.
Click Add endpoint, paste your URL, pick the events to subscribe to, and save. Pivotal sends a webhook.ping event right away so you can confirm it arrived before anything real flows through.
Pivotal fires around twenty event types across four objects: customer, contact, onboarding, task. Subscribing to all of them is the wrong default. Pick by use case:
customer.updated, onboarding.updated, task.updated. The updated events fire on any change, so you snapshot the latest state.customer.at_risk, customer.churned, onboarding.delayed. State flips only, low volume.customer.created, customer.updated, scoped to the fields you care about (set the field filter in the endpoint config).task.completed, phase.changed. Drive funnel charts off these.The full event list with example payloads is in the Webhooks overview.
Every delivery is a POST with three Pivotal-specific headers:
The body is JSON: { id, type, created_at, data }. The data object is the full record at the time of the event. Pivotal signs the payload with the endpoint secret shown on the endpoint page; verify it in your handler before trusting the body.
Every endpoint has a Deliveries tab listing the last 90 days of attempts. Each row shows the status code, response time, and payload. If a delivery failed (or you broke your handler and want to re-send the last hour), select the rows and click Replay in the action bar. Pivotal re-POSTs each one to the same endpoint, with the same body and a new delivery id.
Retries are automatic for the first 24 hours after a delivery fails (5xx or timeout) with exponential backoff. After 24 hours, the delivery is marked permanently failed and you replay manually.
Updating the URL on an existing endpoint affects new deliveries only. To re-send the historical events to the new URL, open Deliveries, filter to the window you care about, select all, and click Replay.
Email help@pivotal.app with a screenshot of where you got stuck and the customer or onboarding id from the URL.