Skip to main content
amaiko orchestrating Sally.io
Sally.io

The AI orchestration layer for Sally.io

Your meetings, answered in chat.

What it does

Find the meeting

By subject, attendee, date range or a topic that came up — Sally's search runs across appointments and summaries.

Decisions and to-dos

The summary comes with key facts, decisions and action items, so "what did we agree with Acme" is one question.

The exact words

When the summary is not enough, the transcript is there with timestamps — quote the passage, not the whole call.

Only what you may see

Your Sally rights decide: your own meetings plus recordings shared with you. amaiko stores none of it.

Try asking

Summarize my last two Sally meetings with Acme, including open items.
List all open action items from this week's Sally meetings, grouped by owner.
In which meeting did we decide on the Postgres migration, and why?

Frequently asked questions

Can amaiko read my Sally.io meeting notes?
Yes. The Sally.io specialist connects to Sally's MCP connector and reads appointments, summaries, key facts, decisions, to-dos and transcripts of the meetings your Sally user can see. It is read-only and changes nothing in Sally.
How does amaiko connect to Sally?
Each user connects their own Sally account from the chat with a one-time login at Sally (OAuth). The connection covers one Sally company account; a Sally admin has to enable the MCP connector for the company first.
Does this replace amaiko's own notetaker?
No. The notetaker records and summarizes meetings amaiko attends; this specialist reads what Sally recorded. Both can be used side by side.

Bring your whole stack into one teammate

Add the specialists you need, when you need them — amaiko runs them all from Microsoft Teams.