What We Fixed
Changing a contract’s pipeline stage (by dragging on the board, using the stage
selector, or via the API) delivered no webhook to subscribed integrations
(Zapier, Make, or custom endpoints). The stage change saved correctly and
automations still ran, but the “Contract stage changed” webhook never fired, so
integrations that relied on it silently received nothing and had to poll for
updates instead.
The event fired internally on a stage change didn’t match any event customers
could subscribe to, so the delivery layer rejected it. Now:
- The “Contract stage changed” (
contractsStageUpdated) webhook fires on
every contract pipeline stage move, keyed to the contract — existing
subscriptions start working with no reconfiguration. - The contract pipeline-status events
(contractPipelineStatusesCreated/Updated/Deleted) are now
registered and deliverable as documented.