Integrations

An integration is an account with an outside service that gives an agent something it can do — who holds it, which projects may use it, and how far the agent may go with it.

An integration is an authenticated account with an outside service, and it is what lets an agent do something outside your workspace: read a calendar, draft a campaign, file an issue, publish a page. Without one, an agent works with what the workspace already holds. With one, it works in the tools your team already uses.

Thousands of services are available. The directory is read live from the provider every time you open it, so it shows whatever is on offer that day, not a list someone keeps by hand.

Yours or the organization’s

An integration always belongs to a person or to the organization, never to a project. Which one decides who can use it.

Your own live in your settings. They sign in with your own account, only your Tendo can use them, and nobody else in the workspace can see them. Connecting your Gmail for yourself puts it nowhere near a shared project.

The organization’s live under Settings › Organization › Integrations. They are connected once for the whole workspace and then switched on project by project. Connecting and switching on are separate decisions: an app connected for the workspace does nothing in a project until that project turns it on.

Every Integrations screen is the same searchable directory, with the built-in toolkits pinned to the top of the grid.

Three kinds

Apps you connect. You sign in with the provider, or paste a key, and the account is stored for you. A card marked Personal app means each person authorizes their own account; Team app means one shared key serves everyone who uses it.
MCP servers. Services that offer their own tools to agents. A set of ready-made ones sits in the directory as cards, and you can add others by URL. They get the same cards, switches and approvals as everything else.
Built-in toolkits. A few come with Auttendo and need no setup at all. They are at the top of the directory the first time you look.

Per-project control

A new shared project starts with every app off. Its agent can use nothing until someone switches an app on in that project, and doing that takes editor rights on the project, not organization admin.

The organization’s page for an app has a switch of its own, On for every Project. It is only a default: a project’s own switch is applied after it and wins either way.

Tendo works the other way round. Apps you connect in your own settings are on for it unless you switch them off.

What a project’s agent may use walks through every place a project is switched on.

More than one account

Two Gmail inboxes, three Shopify stores, a test and a live Stripe account: all supported. Each account gets a name, and you can change it to one you will recognise later.

When a service has more than one account, a call has to say which one it means. The agent never guesses and never falls back to the other account. Tell it in the conversation, or narrow the project to the accounts it should use, and the question goes away.

What the agent may do

Each app has an access mode per project: Read only, Read and write or Full access. The same account can be read-only for one team and writable for another.

A channel inside a project can only narrow that. It can switch an app Off for that channel or leave it on Same as Project, but it can never switch on something the project has off.

When a call falls outside the mode, the agent does not look for a way around it. It tells you the app is read-only here and stops.

Approvals

The last yes on anything irreversible stays with a person. The agent asks before deleting, cancelling, refunding, archiving or revoking; creating and updating go through without a question. A paid data lookup also asks before it spends, once its estimate reaches about a hundred credits, and the question states the figure.

The question appears in the conversation, so everyone in it sees what was asked, and any editor of the conversation can answer. The product records who did. Deny lets the request lapse and the card stays as a record.

Approve always stops the question coming back for that one kind of call in that channel. It never widens the access mode: a pre-approved delete is still refused while the app is set to Read and write. The access panel lists what now runs without asking, and Ask again takes it back. A paid lookup never offers Approve always, because the next one will cost a different amount.

Resource access

For some services an account is not specific enough. A GitHub account signs the agent in, but it does not say which repository the agent may touch. Resource access is a project’s permission to use one particular resource through an integration. GitHub, Sanity and Vercel have it.

Granting and selecting are different acts. When you ask the agent to work on a repository, or it picks one for a task, it is choosing among what a person has already granted. Selecting grants nothing. Only a person grants access, in the project’s settings, and only a person takes it away. An agent cannot widen its own access, and asking it to will not work.

Remove a grant and anything relying on it loses access immediately.

MCP servers

MCP servers have their own filter in the directory, beside the apps. There is a library of ready-made ones, from Context7, which needs nothing, to Notion, Linear and Stripe, which ask you to sign in with the provider. DataForSEO is included with Auttendo, so there is no key to paste. For anything else, Connect MCP server adds a server by its URL.

Adding one for the whole organization takes an owner or an admin. A server address plus a token is a capability for the entire workspace, so it is held to a higher bar than connecting an app.

Connect an integration — the steps, from finding the app to choosing its projects.
What a project’s agent may use — switching apps on per project, choosing accounts, and granting resource access.
Tendo — your own agent, and the only one that uses your own integrations.
Projects — where the organization’s integrations are put to work.