Which event means "this changed"

Embed
Preview of the card
<a href="https://forumulate.com/reference/webhook-events"><img src="https://forumulate.com/reference/_api/public/orgs/046a9bc0-d530-43ae-9bae-af7945008cda/spaces/8042f004-e3d9-445f-b7a4-b6c1f86836e6/pages/f9d92473-b489-4d9f-8b8f-46ec00ec0987/social-card.svg?v=3e7ae33eec8b" alt="Which event means &quot;this changed&quot;" width="600" height="315"></a>

Events are named after what backs a piece — page.*, topic.* — while /items calls all of them items. They are the same things. This page is the mapping.

Ask the API for it

GET /api/orgs/{orgId}/webhooks/events
{
  "events": ["page.created", "page.published", "page.updated", "…"],
  "catalog": [
    { "event": "page.published", "item": "page", "subscribe": true,
      "means": "A page's content changed for readers. Fires on EVERY publish, not only the first." }
  ]
}

item is the kind the same piece carries in /items. subscribe marks the events a content sync actually wants.

The short answer

A blog post, a forum thread, a changelog entry and a roadmap card are all topics. A documentation page, an FAQ answer and a careers posting are all pages.

Renames

Renaming a published page changes the address readers are sent to and publishes nothing. That used to reach no subscriber at all, so a synced copy elsewhere kept pointing at an address that only redirected. page.updated carries { pageId, from, to }.

Ordering

Deliveries are at-least-once and unordered. sequence in the body increases per organization, so a stale delivery is discardable rather than damaging, and X-Forumulate-Delivery is the key to deduplicate a repeat on.

The Forumulate teamUpdated