Skip to content
Publish & Sync

Change safely

Tell the rest of the stack what happened.

Signed webhooks for content created, updated, approved and published; for facts changing; for health issues opening; for source synchronization completing; and for releases publishing.

Webhooks

  • content.created / updated / approved / published
  • fact.changed and health.issue.created
  • source.sync.completed and release.published
  • Signed, retried, deduplicable

How it helps

What Webhooks gives you

1

Signed and replayable

Every delivery is signed and carries an event ID, so a consumer can verify it and deduplicate it.

2

fact.changed is the interesting one

It is the event that lets a customer's own systems react to a product truth changing, not just to a page being edited.

3

Retries with a dead letter

Failed deliveries retry with backoff and end up somewhere visible rather than silently disappearing.

Give your content a memory. Give your AI the full picture.

Connect a repository read-only and see what has been sitting inside it — every headline, claim and near-duplicate paragraph, with the file and field each one came from.

Keep Git and your existing stack Read-only to start Narraxio runs on Narraxio