Webhooks

Push live updates from your NOAN project to any endpoint, so everything you build on the API stays in sync the moment a fact changes.

Until now, keeping something you built in sync with your NOAN facts meant polling the API on a schedule and hoping you caught changes quickly. Webhooks flip that around: NOAN pushes the change to you the moment it happens.

How it works

Configure a webhook in Settings, under Your Project, then Integrations:

• Turn webhooks on and set the endpoint URL that should receive events.
• Optionally require a valid TLS certificate on your endpoint with "Verify Endpoint Certificate".
• Watch deliveries land in the live log, each with its HTTP status, event type, any error, and a timestamp.

Events fire whenever your fact base or workspace changes, for example a fact updated, a note created, or a contact's tags changing. Each event names what changed so your endpoint can act on exactly the right thing.

What it means for building on the API

This is the piece that makes the fact layer a true control plane for everything you run on top of it.

• Event-driven, not polling. Your app reacts the instant a fact changes instead of asking "anything new?" on a timer. Less latency, fewer wasted calls.
• Change once, propagate everywhere. Update a fact in NOAN and every surface you've deployed on the API, a website, an app, an agent, can be refreshed or re-grounded immediately, so they all move to the new truth at the same moment.
• Close the loop. The API already lets you read and write facts; webhooks add notify. Read, write, and now react, the full cycle for keeping agents and products grounded on live company truth.
• Real patterns it unlocks: rebuild or revalidate a page when its source fact changes, invalidate a cache, re-ground a running agent, or kick off a downstream workflow the second the underlying fact moves.

The net effect: your facts stop being a thing you fetch and become a thing that tells you when it changed, so what you build stays correct without you babysitting it.