Connecting your tools
Sanaf works inside the apps you already run. A connection is made per app, scoped to the job that needs it, and revocable on its own. Nothing is connected by default, and connecting an app does not grant a job access to it.
Last updated 2026-09-04.
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. The token is encrypted at rest and Sanaf uses it only inside a job you have given it.
Two things are separate on purpose: connecting an app, and a job being allowed to use it. Connecting your books does not let the support job read them. You grant the app to the job, which is why a connection can be broad while a job stays narrow.
Adding a connection
- 1
Open the job that needs it
Start from the job rather than the app. The question is always what this job needs, not what Sanaf could theoretically reach.
- 2
Sign in to the app
You are sent to the app to sign in, and you approve the scopes it asks for there. We never see your password, and the token comes back encrypted.
- 3
Grant it to the job
Choose which jobs may use the connection. A connection with no job attached does nothing, which is the safe default rather than an oversight.
- 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, and each is granted to the jobs that should see it. Sanaf names the account in the work log so there is no doubt which one 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.
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
Revoke a connection from the console and it stops immediately, for every job. Revoking one connection never affects another, which is the whole reason they are separate.