Webhooks

A common question is whether Revnator can push events to your systems. This page explains the current options for keeping an external system in sync with Revnator.

Outbound webhooks

Revnator does not yet offer user-configurable outbound webhooks — there is no setting today to register a URL and receive event callbacks. Until that ships, use one of the patterns below.

Polling the API

The most reliable way to detect changes is to poll the relevant list endpoint on a schedule. List endpoints return records newest-first, so you can page through recent activity and stop once you reach records you have already seen. Respect the pagination cap of 50 records per page.

1curl "https://app.revnator.com/api/v1/contacts?limit=50" \
2  -H "X-Revnator-API-Key: rvn_live_your_key_here"
Copy

The analytics endpoint

For periodic summaries rather than individual records, GET /api/v1/analytics?period=7d|30d|90d returns rollups for contacts, deals, emails, and tasks in a single call — a lightweight way to keep a dashboard fresh.

The MCP server

If your goal is to let an AI assistant act on Revnator data on demand, the MCP server (@revnator/mcp) is usually a better fit than a polling loop — the assistant queries Revnator live whenever it needs to.

Triggering AI on demand

To act when something changes on your side — for example a new lead in another system — POST that contact to /api/v1/contacts and then call POST /api/v1/ai/trigger to score it immediately, rather than waiting for the hourly background agent.