What is live today
Webhook events are live for contacts (added, changed or deleted) and deals (added or moved to another stage). Every subscription returns an HMAC signing secret. A dedicated
call.completed event is coming soon; until then every call sends contact.updated for the caller.How the pieces fit
Two directions matter. Events flow out of AiSky into your automation tool, and your agent reaches into your systems during a live conversation. Most teams use both.Consume AiSky events in Zapier, Make, or n8n
The events delivered today arecontact.created, contact.updated, contact.deleted, deal.created and deal.stage_changed. A dedicated call.completed event is coming soon; until then every call sends contact.updated for the caller. Each automation tool exposes a generic webhook trigger, so the setup is the same three moves: create the trigger, register its URL with AiSky, then verify the signature.
1
Create a webhook trigger and copy its URL
Add a catch-all webhook trigger in your tool and copy the URL it generates.
2
Register the URL as a AiSky subscription
Create the subscription in Settings → Webhooks & API in the app, or through the MCP server (the
smartalex_ webhook tools). Point it at the URL from step 1 and choose the event, for example contact.updated. The response includes an HMAC-SHA256 signing secret. It is shown once, so store it in your tool’s secret manager immediately.3
Verify every delivery
Reject any payload whose signature does not match. Use the snippet below in a Zapier Code step, a Make custom function, or an n8n Code node before you act on the event.
Verify the HMAC signature
Each delivery is signed with HMAC-SHA256 over the raw request body, using the secret returned when you created the subscription. Recompute the digest and compare it in constant time.The exact signature header name and the full JSON payload shape for each event are confirmed at the moment you create the subscription (and in the Developer Portal). Wire the verification against those values rather than hardcoding assumptions.
Call your own endpoints during a call (Custom HTTP Tools)
This surface is fully live and is often more useful than one-way events, because it runs while the caller is still on the line. With the Power Tools add-on (a rate on request, included on Enterprise), you give an agent a Custom HTTP Tool that makes an HTTPS request to an endpoint you own, then speaks the result back. Common patterns:- A caller asks about an order. The agent calls your
/orders/lookupendpoint and reads the status aloud. - A caller wants to book. The agent posts to your scheduling endpoint and confirms the slot in the same breath.
- A qualified lead comes in. The agent pushes the details to your CRM’s inbound webhook before the call ends.
Drive your account from an AI client (MCP)
The MCP server lets Claude, Cursor, or any MCP client operate the account, including creating the webhook subscriptions above. Connect it once:Example automations
Once events are flowing, these wire up in minutes:contact.updated: after a call, append a row to a spreadsheet, post to Slack, or create a follow-up task in your CRM.deal.stage_changed: notify the deal owner and update the matching record in your pipeline tool.contact.created: enrich the contact and drop it into an email sequence.
Coming soon
A native AiSky app for Zapier, Make, and n8n (prebuilt triggers and actions, no manual webhook wiring) is on the roadmap, alongside a TypeScript SDK. The public REST API is already live. A dedicatedcall.completed event is coming soon too. Nothing on this page will need to change: the events and Custom HTTP Tools you build on now carry straight over.
Related
Get started with MCP
Connect an AI client and manage webhook subscriptions.
Custom HTTP Tools
Let an agent call your own HTTPS endpoints mid-call.
Add-ons and Power Tools
What the a rate on request Power Tools add-on unlocks.
Build with AiSky
Every integration surface in one place.

