Connecting your tools
Sanaf works inside the apps you already run. You connect an app by signing in to it from the console, you decide per tool what it may do without asking, and you can disconnect it on its own at any time. Nothing is connected by default.
Last updated 2026-09-24.
How a connection works
You connect an app once, from the console, by signing in to it the way you would sign in to anything. We never see your password, and Sanaf uses the connection only for work you have given it.
A connection belongs to the employee it was made for. Sanaf and each of its agents have their own, so connecting your books for the bookkeeping agent does not hand them to the one answering support.
Some apps need no sign-in at all, such as a public search or a news feed. Those are added rather than connected.
Adding a connection
- 1
Open Integrations for the employee that needs it
Start from the work rather than the app. The question is always what this job needs, not what Sanaf could theoretically reach. The common business apps are listed first, and every other app is a search away.
- 2
Sign in to the app
You are sent to the app to sign in, and you approve what it asks for there. When you come back the app is connected and Sanaf reads it once to learn how your account is set up.
- 3
Set what each tool may do
Every tool of the connection follows your approval rules by default. You can set one to always allowed, always asked about, or never, without changing the others.
- 4
Check the first run
Give the job something small that uses the new app and read the work log afterwards. If the scopes are wrong, this is where you find out rather than three weeks later.
Two accounts of the same app
This is common and it is supported: two inboxes, two ad accounts, two books. Each is its own connection with its own tool settings, and the work log names the account it acted in.
When a tool has no API
Some tools have no API worth the name. Sanaf can sign in and work in the page itself as part of a job, which is slower and more fragile than an API and is treated accordingly: it asks more often, and it says in the work log that it was working in the browser.
Your own systems can be added too: an MCP server or a REST API, described once in the console under Your systems. Every tool one of them brings in asks before it acts until you say otherwise.
If a tool you need is not in the integrations directory, tell us. The directory on this site lists every app it works in today, with the jobs it does there.
Revoking
Disconnect an app from the console and it stops immediately. Disconnecting one connection never affects another, which is the whole reason they are separate.