Documentation
Connecting your tools
A meeting only pays off once it becomes a task, a page or a record where your team already works. Here's what setting that up really takes. For about half the tools, it's less than you'd expect.
Three kinds of setup, and yours is probably the easy one
Every destination Jaha writes to falls into one of three groups, and the effort varies a lot between them.
Microsoft destinations (Teams, Outlook, OneDrive, SharePoint and Planner) need no authorization, because the consent your admin gave at signup already covers them. Tools with an OAuth app need one button and a permission screen. A few only issue API tokens, and for those someone has to create one and paste it in.
Microsoft tools: one button and at most one choice
Jaha is already an app inside your Microsoft 365 organization, running on the consent an admin gave once. So connecting Teams, Outlook, OneDrive, SharePoint or Planner means pressing Connect. There's no second sign-in, no token and no secret to manage.
When a destination has to be chosen, like whose OneDrive or which SharePoint site, Jaha asks Microsoft what exists in your organization and shows you the list. You pick from real sites and mailboxes instead of pasting a URL from memory, and that's what keeps a connection from failing after a meeting.
If your admin hasn't granted the permission needed to read that list, Jaha says which permission is missing and links to the page where it's granted. You won't see an empty menu that looks like an empty organization.
One-click tools
Slack, Google Drive and Docs, Notion, Jira, Linear and Zoho use OAuth: press Continue, sign in to that tool, approve the permissions it lists, and you're connected. Jaha never sees a password, and its access is exactly what you saw on the approval screen.
The permissions are kept narrow on purpose. Google Drive, for example, only asks to see and edit files the app itself created. Jaha can't read the rest of your Drive, and the approval screen says so in Google’s own words.
If a deployment hasn't set up a vendor’s OAuth app, the connect screen lets you paste a token instead of leaving you stuck. It's a fallback, and the screen shows which method you're using.
Tools that need a pasted token
HubSpot, Salesforce, Pipedrive, Asana, ClickUp, monday.com, Todoist, Trello, Confluence, Dropbox and Box use API tokens. Someone creates one in that tool and pastes it into Jaha, where it's stored encrypted and never shown again.
The connect screen for each of these shows the exact path through that vendor’s settings, with a link to the vendor’s own current help page. We don't copy their screenshots on purpose: their screens change, and an outdated picture is worse than a precise sentence.
Deciding what goes where
A rule says which meetings go to which destination: all of them, only meetings with a customer, only ones that match a keyword, or only the ones you tag. One meeting can go to several destinations, and each rule can have its own filter.
When a destination has to be named (a channel, a project, a plan or a space), Jaha asks the connected tool for the list and lets you choose. A hand-typed ID is the mistake nobody catches until a delivery fails days later, so wherever the vendor offers a list, the field is a menu.
CRM rules have one extra question worth reading twice: what to do when nobody in the meeting is a contact. Skipping suits a team whose CRM tracks customer relationships. Attaching to a named fallback record suits a team that wants every call logged. Both are valid, so Jaha asks you to choose, and colleagues are never added to a CRM either way.
What arrives
A recap turns into whatever that tool is for: a task for each action item, a page in a workspace, a message in a channel, or an activity on a CRM record. It's the content itself, so it's useful even to someone who has never opened Jaha.
One task per action item, with the owner Jaha heard on the call.
Northwind Trading: quarterly review
Thursday 12 March, 14:00
Summary
العربية
The recap as a page in the meeting’s own language, translated for anyone else who was there.
Northwind Trading: quarterly review
Posted as Jaha in the channel your team already watches. No webhook to set up.
Northwind Trading
Renewal · closing this quarter
Meeting logged · quarterly review
Matched on the two attendees who are contacts. Colleagues are never written to the CRM.
Attached to the right record. If the call wasn't with a customer, Jaha skips it instead of guessing.
These are illustrations, not screenshots. They show what arrives, drawn by hand instead of taken from a real workspace. Northwind Trading is a fictional company.
When something fails
Every delivery is recorded on its meeting: what was sent, where, when, and what the other side replied. A failure gives the cause in the vendor’s own words and says what to change, such as a project that doesn't exist, a token that's no longer accepted, or a channel the app hasn't been added to.
Once the cause is fixed, failed deliveries can be retried or sent again, and nothing is dropped without notice. If a rule keeps failing, the connection shows it so you don't have to spot it yourself.
Developers who need what each delivery sends, webhook signatures and the REST endpoints should read Connectors & API.