INTEGRATION · WEBHOOKS

One integration, any destination.

Subscribe to the events that matter — recommendation created, experiment started, competitor change detected, rank shift past a threshold — and route them into any tool that can receive a POST. Filtering, configurable retries, HMAC signatures, and test endpoints included.

Watch 2-min demo ▸

◉ EVENT-TYPE FILTERING◉ HMAC SIGNED◉ CONFIGURABLE RETRIES

WHY WEBHOOKS

Native integrations cover the common tools. Webhooks cover the rest.

Slack, Jira, Asana, WordPress — native integrations cover the tools most growth teams already run. Webhooks cover everything else: Zapier, Make, Linear, ClickUp, Monday, custom internal tools, your proprietary deploy pipeline, a notification system you wrote on a weekend. If it can receive a POST, it can consume Optimize Pilot events.

◆ CAPABILITIES

Every event type, configurable payload.

EVENT CATALOG

A dozen event types. Filter to what you care about.

Subscribe to recommendation.created, recommendation.implemented, experiment.started, experiment.completed, experiment.auto_promoted, competitor.change_detected (with severity threshold), rank.shift (with delta threshold), accessibility.critical_issue, schema.validation_failure, and more. Mix and match per endpoint.

Recommendation lifecycle events
Experiment lifecycle + auto-promotion events
Competitor change events with severity filter
Rank shift events with delta threshold
Accessibility + schema validation events

PRODUCT VISUAL — PLACEHOLDER

RELIABILITY

Signed, retried, verifiable.

Every event is HMAC-SHA256 signed with a per-endpoint secret so your receiver can verify authenticity. Failures retry with configurable backoff. Test endpoints let you confirm delivery before going live.

HMAC-SHA256 signatures with per-endpoint secrets
Configurable retries on delivery failure
Test endpoint sends a sample of each event type
Per-endpoint delivery log with replay action

PRODUCT VISUAL — PLACEHOLDER

CUSTOMIZATION

Shape the payload to your downstream tool.

Default JSON payload is verbose (good for debugging), but you can configure a trimmed version per endpoint — drop fields you don't need to keep the payload lean for the downstream tool. Great for sending straight to a Zap.