Connect an integration

Connect an account with an outside service for yourself or for the organization, choose which projects may use it, and name it so the agent knows which one you mean.

Connecting an app takes a minute and a login at the service you are connecting. When you are done the account is stored, and for an organization account you have also chosen which projects may use it.

Connect an app

Pick where it belongs

The Integrations screen you start on decides who holds the account. Open Integrations in your own settings for an account only your Tendo will use. Open Settings › Organization › Integrations for one the workspace shares. Both screens work the same way.

Find the app

Type the service’s name into the search field above the directory. The filters beside it narrow the grid to All, Connected, Enabled or MCP servers, and Load more at the bottom brings in the next page. Open the app’s card. It opens as a page of its own, with a link back to the directory.

Press Connect

Connect is the one action in the app’s header. If the app already has an account here, the same button reads Add account.

Authorize in the provider's window

A window opens over the page. It belongs to Pipedream, which holds the account on Auttendo’s behalf, not to Auttendo, so expect to see Pipedream’s name in it. The details you give the provider never pass through Auttendo. Sign in and approve what the provider asks for. When the window closes, the new account is listed on the app’s page.

Answer Use in

On the organization’s page, the first time an app gets an account, Auttendo asks which projects may use it, in a dialog titled after the app: Use Gmail in, for Gmail. Nothing is preselected. Tick the projects whose agent should have it, or tick Every Project, now and later so projects created later get it too, then press Done.

Not now writes nothing and leaves the app off in every project. You can switch it on for a project later.

In your own settings there is no question to answer: an account you connect for yourself is on for your Tendo straight away.

Name the account

Every account gets a generated two-word name, such as “Silver Planes”, so none is ever nameless. Give it a better one before you connect a second account of the same service. When there are two, the agent has to be told which one a call is for, and “Client ads” answers that where “Silver Planes” does not.

On the app’s page, press the account’s name in its row, type over it and press Save, or Cancel to keep the old one. Clearing the field and saving puts the provider’s own name back.

Connect from inside a conversation

You do not have to leave the work to connect something. When the agent needs an app that is not connected, it says so and puts a button in its reply. The button opens the same Pipedream window, and once you have authorized, the conversation carries on from where it stopped.

If the app is connected for the workspace but switched off in this project, the button reads Enable instead. One press switches it on here, which takes editor rights on the project.

Add an MCP server

The directory lists a library of ready-made MCP servers as cards, and those connect like any other app, with no address to paste. For a server that is not in the library:

Open the dialog

Press Connect MCP server on the directory.

Fill in the server

Enter the Server URL and a Display name you will recognise. Under Advanced, choose how the credential is sent: as an authorization header, as a custom header, or as a query parameter. The dialog tells you that a query parameter is not encrypted.

Adding a server on the organization’s page takes an owner or an admin. A server address plus a token is a capability for the whole workspace, so it asks more than connecting an app does.

Disconnect

Removing an account takes it away from everything that used it. Work that relied on it does not move over to another account of the same service; the agent tells you it is blocked rather than routing around it.

If you only want one project to stop using an app, switch it off in that project instead. The account stays connected and every other project keeps working. What a project’s agent may use shows where.

Troubleshooting

The app is connected, but nothing happens in a project

Connecting and switching on are two separate decisions, and a shared project starts with every app off. Open the project’s settings, go to Integrations, open the app and switch it on there. You need editor rights on the project.

The agent says the app is read-only here

The project’s access mode for that app allows reads, and the agent tried to write. It will not work around the setting. Change the mode under Access in this Project on the app’s page in the project’s Integrations settings, if the project should be allowed to write.

The agent asks which account to use

The service has more than one account, and the agent never picks one for you. Name the account in the conversation. To settle it for good, narrow the project to one account under Access in this Project › Accounts, which starts at Any account.

Integrations — who holds an account, what the agent may do with it, and when it asks first.
What a project’s agent may use — switching apps on per project, choosing accounts and granting resource access.
Tendo — the agent that uses the accounts you connect for yourself.