Sayli works better when it knows your meetings and where your work lands. Connect a few tools once, and the right context shows up on the call and the right note shows up after it.
There are two kinds of connections. Some Sayli reads to help you live. Some Sayli writes to once the call is done. Most connect once per organization. Google Calendar connects per user, so each person sees their own schedule.
Every connection uses OAuth or a token you control. You can disconnect any of them at any time.
Read to help
These give Sayli the context it needs while you are on the call.
Sayli sees what is next and who is in the room.
Google DrivePull documents from Drive into what Sayli can cite.
MCP connectionsLet Sayli pull from your own tools through MCP tool calls.
Jira & ConfluenceSurface the right issue or page while you talk.
Personal access tokensA token you mint and revoke for programmatic access.
Write what you ask
These put the outcome of the call where your team already looks.
Send a summary or an action item to the right channel.
Your CRMLog the call and update the deal after you hang up.
WebhooksPost call events to any endpoint you run.
Sayli as an MCP serverRead your meetings and notes from your own MCP client.
Google Calendar is the one connection each person makes for themselves. It takes a minute and changes what Sayli knows on every call. See Google Calendar.