Introduction
Webhooks let RecordsKeeper.AI send real-time event data to your application - no polling required. When something happens (e.g., a record is created, a payment is received), we deliver a JSON payload to your endpoint so you can trigger workflows in your CRM, analytics, or internal systems.
Main body
Where to manage webhooks
From the left menu, open Widgets & Integration → API & Webhook Integration, then choose the Webhooks tab.
Here you’ll see all webhooks with columns for Webhook Name, Last Event Sent, Listening To (number of subscribed events), Last 7 Days activity, Created On, and Actions (enable/disable, overflow menu).
You can also switch to Overview for delivery trends (Successful/Failed), Response time (min/avg/max), and Recent Errors & Warnings to troubleshoot issues quickly.
Create a webhook (step-by-step)
Click Create Webhook (top right of the Webhooks tab).
In the Create Webhook modal, provide:
Webhook Name - A clear label (e.g., “Website Events → Zapier”).
Endpoint URL - Your HTTPS endpoint that will receive POST requests.
Description - Optional context for teammates.
(Optional) Add Basic Authentication
Toggle Protect webhook URL with basic authentication, then set a Username* and Password*. These are included via theAuthorizationheader for each delivery.Choose API version
Use API Version to lock payload shape to a specific version, keeping your integration stable during future updates.Select events to send
Use Select multiple events to send to subscribe (e.g., record.created, user.signup, payment.received). You can update this list later.Click Create Webhook.
A confirmation dialog displays your Webhook Secret. This secret is used to sign payloads so you can verify requests on your server. Copy or Download it now - it won’t be shown again. If you lose it, create a new secret/webhook and rotate in your app.
Securing and validating deliveries
HTTPS required: Host your endpoint on HTTPS to protect data in transit.
Signature verification: Use the Webhook Secret to validate the signature header on each request before processing the payload.
Basic Auth (optional): Add an extra layer by requiring username/password on the endpoint.
Managing webhooks after creation
Enable/Disable with the toggle in Actions to pause or resume deliveries.
Update subscriptions to add/remove events as your use case evolves.
Monitor health on the Overview page:
Successful/Failed counts and Response time trends surface delivery issues fast.
Recent Errors & Warnings highlights common problems (invalid API key, unknown parameters, resource not found, permission denied, rate limit exceeded, invalid input). Use these messages to fix your endpoint or event handling.
Pointers (good practices)
Create one webhook per destination/workflow (and per environment) for easier isolation and rollback.
Store the secret in a secure vault and rotate it periodically.
Return 2xx quickly from your endpoint—do heavy work asynchronously to avoid timeouts and retries.
Log delivery IDs and signatures on your side to trace and replay when needed.
When troubleshooting, check Last Event Sent, recent failures, and your server logs together.
Conclusion
With webhooks, RecordsKeeper.AI pushes events to your systems the moment they happen. Set up a named endpoint, secure it (HTTPS + signature, optional basic auth), select the events you care about, and use the dashboard to monitor performance and resolve issues. This keeps your integrations fast, reliable, and easy to maintain.