Connectors, delivery and the API

Connect knowledge sources like Google Drive, SharePoint, Notion, Confluence and Jira, and Jaha answers from inside them with citations. Each connector has its own sharing class and answer scope, so connecting a source never lets more people hear what's in it.

On customer calls, Jaha comes in prepared: recent CRM activity, open items and the commitments from the last meeting are already loaded when the call starts.

Rules decide what each tool gets after a meeting: the summary to your CRM, action items to Jira or Asana, the recap to a Slack channel, full notes to Notion. Each rule sets where it sends, what to include, and which meetings it covers. If a send fails, Jaha tries again later, and destinations with problems are flagged before anything is lost.

Not every case needs a standing rule. From any meeting, anyone with send permission can choose connected destinations and exactly what to send (the summary, the actions or everything) for that meeting only. One-off sends go through the same delivery process as rules, with the same health checks, retries and receipts.

Every meeting keeps a delivery history: what was sent, where, when, and by which rule or person. When a CRM record looks wrong three weeks later, the history answers “what did we send” at a glance.

Everything the dashboard shows is available through a scoped REST API: meetings, transcripts, insights, tasks and usage, with scopes per key and rate limits by plan. Webhooks send meeting lifecycle events to your systems as they happen, and on Business and above a live streaming API follows a meeting while it's running.

The full interactive reference, with keys and a console to try requests, is in the dashboard once you sign in.