Apps and connections

Connect your apps

Connecting an app lets Sanaf work inside the tools your business already uses, with the account you sign in with. Before you start Only an owner or a manager can connect, change or disconnect an app. A member can see what is connected but cannot change it. Connect an app 1. Open Integrations in the left rail. The Apps tab opens first. 2. Find the app under Common business apps, scroll the full list, or type its name in the search box. 3. Press Connect on the app's card. 4. Sign in to the app and approve access. You come back to Integrations with a message that the app is connected and Sanaf can use it now. Some apps need no sign-in at all. Their card says No sign-in needed and the button reads Add instead of Connect. Apps that use a key rather than a sign-in say API key on the card. If the app you want is not in the list, you can add it yourself as an API or an MCP server. See Connect your own systems. Connect a second account of the same app You can connect the same app more than once, for example two mailboxes. Open the app under Connected and press Add another account. To tell the accounts apart, open one, go to Settings and give it an Account label. Choose what Sanaf may do with each tool Every app gives Sanaf a set of tools, such as "send an email" or "create a contact". You decide, tool by tool, how Sanaf uses them. 1. Open the app under Connected, then open the account. 2. On the Tools tab, find the tool. You can search the list. 3. Pick one of these for the tool: - Always allow: Sanaf uses it without asking. - Ask for confirmation: Sanaf asks a person each time before using it. - Never allow: Sanaf cannot use it. - Follow trust level: the default. Sanaf follows its normal approval rules for that kind of action. Use Set all tools to apply one choice to every tool at once. Some actions, such as spending money, always ask for approval, whatever you choose here. Learn how the app is set up On an app's screen, a section such as What Gmail looks like from here holds a short note Sanaf wrote about how your account is organised. Sanaf reads it every time it uses the app. Press Learn it now or Learn it again after something changes, such as a renamed team or a new permission. It uses a few read-only calls and one short model call. Turn off, lock or disconnect an app Open the account and go to Settings: - Enable integration turns the app on or off. Off keeps the sign-in but puts the tools out of Sanaf's reach. - Lock integration means only an owner can change the connection or its tool settings. - Disconnect integration removes the connection and its tool settings. Sanaf loses access right away. This does not cancel the access inside the app itself, so remove it there too if you want it gone on both sides. Related - How approvals work - An app will not connect or stopped working - Connect your own systems (MCP servers and APIs)

Connect your own systems (MCP servers and APIs)

Use this when a tool your business relies on is not in the app list, such as your own software or a service built for your team. What you can add - MCP server: a remote MCP (Model Context Protocol) server, connected by its URL. It brings its own tools with it. - API: any REST API, described once with its base URL, the methods Sanaf may use and your credentials. Only an owner or a manager can add, change or remove one of these. Add an MCP server 1. Open Integrations and press Add custom. 2. Choose MCP server and press Next. 3. Fill in a Name and the Server URL. 4. Pick the Transport your server uses: http or sse. 5. Pick the Authentication: None, Bearer token, API key in a header or Basic (user:password). For a header key, type the exact Header name the server expects, such as x-api-key. 6. Paste the key and press Connect. The server must be reachable over HTTPS from the internet. A server running on your own computer cannot be reached. Add an API 1. Open Integrations, press Add custom, choose API and press Next. 2. Fill in a Name and the Base URL. Sanaf's requests stay inside this address and cannot go outside it. 3. Tick the Allowed methods: GET, POST, PUT, PATCH or DELETE. 4. Pick the Authentication and paste the token. 5. Add a Documentation URL if you have one, then press Add API. Keys and tokens are stored encrypted, sent with each request and never shown again. What Sanaf may do Everything you add is listed on the Your systems tab of Integrations. - MCP server tools all ask a manager before they run, until you change that. - API reads (GET) run on their own. Anything that changes your data asks a manager first, until you change that. To change it, press Tools and permissions on the system and pick Always allow, Ask for confirmation, Never allow or Follow trust level for each tool. Check the connection Press Check connection on the system. For an MCP server this runs the real handshake and shows how many tools Sanaf gets and their names. For an API it makes one GET request to the base URL with your credential and shows the result. An MCP server's tools appear on its Tools and permissions screen only after a check has reached it, so run a check after adding one. Turn off or remove a system Open Tools and permissions, then Settings, to switch the system on or off. Off keeps the credential and your choices but puts the tools out of reach. To remove it completely, press Remove on the Your systems tab. Related - Connect your apps - How approvals work - An app will not connect or stopped working

Use API keys and the Sanaf MCP server

An API key lets software you run talk to Sanaf: an AI assistant that speaks MCP, an automation tool, a script or a form on your website. This is the opposite direction from connecting your apps. Here, other software asks Sanaf to do something. Make a key Only an owner or a manager can make or revoke a key. 1. Open Settings > API keys. 2. Under Make a key, fill in What it is for, for example "Zapier" or "my laptop". Each live key needs its own name. 3. Under Which employee it may reach, leave Any employee in this workspace or pick Only Sanaf. 4. Press Make the key. 5. Copy the key right away. It is shown only once. If you lose it, revoke it and make another. A key looks like emp_<workspace>_<secret>. The list shows each key's name, a short label, which employee it reaches and when it was last used. It never shows the key again. Connect an MCP client Add a server in your MCP client (Claude, Cursor or anything that speaks MCP) with: - URL: https://employees.sanafai.com/api/mcp - Header: Authorization: Bearer <your key> Your client then gets four tools: - list_employees: the AI employees in the workspace, with their id and whether they are live. - ask_employee: give Sanaf a task or question. Takes employeeId, message and an optional chatId to continue a thread. Returns a chat id and a run id. - get_reply: read every message in that chat so far. Takes employeeId and chatId. - list_work: what Sanaf did recently, from its work log. Takes employeeId and an optional limit (20 by default, 50 at most). Send a task over REST For anything that does not speak MCP, send one POST: curl -X POST https://employees.sanafai.com/api/v1/messages \ -H "Authorization: Bearer <your key>" \ -H "Content-Type: application/json" \ -d '{"employeeId":"...","text":"Chase the overdue invoices"}' Leave out employeeId if the key reaches only one employee. Add chatId to continue an earlier conversation. The answer is 202 with employeeId, chatId, runId and status: "working". It does not wait for the reply, because Sanaf may take a while or wait for someone's approval. Read the reply with get_reply over MCP. What a key can and cannot do - A key only reaches its own workspace, and a key made for one employee cannot reach another. - Sanaf's approval rules still apply. Anything that needs a person's yes waits for it. - A refused key gets a 401 that says why: no key sent, not a key, no matching key, or a revoked key. - A 503 means we could not check the key just then. Nothing was lost, so send the same request again. - The full developer reference is at https://employees.sanafai.com/docs/api. Revoke a key Press Revoke next to the key, then confirm with Yes, revoke and the key's name. It stops working right away and cannot be switched back on. Related - Connect your apps - How approvals work - Check the work log and reports

Install skills and automations from the marketplace

The Marketplace is where you give Sanaf new abilities without writing them yourself: skills it follows when the moment comes, and automations it runs on a schedule. What you will find Open Marketplace in the left rail. The page has four sections: - Featured: bundles we put together, one per kind of work. A bundle installs several skills at once. - Skills: procedures Sanaf follows, such as how to handle a type of request. - Picks from skills.sh: community skills we read and would install ourselves. - Automations: recurring work Sanaf does on a schedule, without being asked. Use Search the Marketplace at the top, or Browse all beside a section. The full skills list has three tabs: By Sanaf, Picks from skills.sh and Search skills.sh. Only an owner or a manager can install. Sanaf must be hired first. Install a skill or a bundle 1. Open the skill to read it first. You see its instructions and any files that come with it. 2. Press Install skill, or Install bundle on a bundle card. 3. The button changes to Installed. Press it to go to Sanaf's Skills screen. Every skill is a starting point. Once installed, you can edit it on the Skills screen like any skill you wrote. Installing the same skill twice does nothing new. Community skills from skills.sh Skills from skills.sh are written by people outside Sanaf, so read them before you install. Each one shows where it comes from and its install count on skills.sh. A skill whose security audit says high risk cannot be installed here. A skill changes how Sanaf does a job. It does not give Sanaf access to anything new and does not change what needs your approval. Install an automation 1. Open the automation. You see What it does and Apps it needs. 2. Under When, pick the time, and the days or day of the month if the automation asks for them. Times are in your workspace's time. 3. Under Where it posts, choose The console chat or a Slack channel Sanaf has been added to. 4. Press Install automation. If an app it needs is not connected yet, you can still install. The automation will report that it cannot reach the app until you connect it on the Integrations screen. Press Connect beside the app to go there. After installing, the automation appears on the Routines screen, where you can change its schedule, pause it or remove it. Each run is ordinary work, so it uses credits like any other task. Suggest or share something At the top of the Marketplace you can publish a skill of your own on skills.sh, or tell us what you would like to see here. Related - Give Sanaf skills - Schedule recurring work - Connect your apps