AivahHelp CenterGo to Aivah
⌘K
No guide matched “”

Try fewer words or contact support for help.

Contact support

Connect tools and allow safe actions

Connect an outside service through MCP, limit what Aivah can do, and test the connection privately.

Who this is forWorkspace owners and team members authorized to connect company services

You will achieveConnect the correct account with the smallest useful action set and verify one safe action in the Playground.

Before you beginReview the requirements before changing anything.

Last reviewed 10 July 2026Owner: Product EducationCurrent guide
On this page
  1. Before you begin
  2. Steps
  3. 1. Open Integrations → MCP
  4. 2. Open the correct service
  5. 3. Choose the smallest useful action set
  6. 4. Connect the correct account
  7. 5. Confirm the connection is active
  8. 6. Test one safe action privately
  9. Expected result
  10. Status meanings
  11. Usage credit impact
  12. Information stored or shared
  13. Limits and permanent actions
  14. Common problems and recovery
  15. Next step

This guide is for people who are allowed to connect company services to Aivah. You will connect one service, allow only the actions an AI employee needs, and verify the connection in a private conversation before anyone depends on it.

Before you begin

Prepare:

  • The service and account your organization has approved.
  • Permission to connect that account and approve actions.
  • One low-risk action you can use for a controlled test.
  • Instructions that tell the AI employee when to ask for confirmation.

If several sign-in methods are offered, use the method approved by your organization.

Steps

1. Open Integrations → MCP

MCP is the workspace label for connected outside tools and their allowed actions. Search for the service you need or browse the services shown for your account.

Search field in the MCP connected-tools area
Search for a service from the MCP area in Integrations.

2. Open the correct service

Open its details and check the service name before continuing. The services and actions shown can vary by account and provider.

Available connected tools in the MCP area
The MCP area shows the connected tools available to the current account.

3. Choose the smallest useful action set

Allow only the actions required for the employee's job. Do not approve every available action by default.

For any action that sends a message, creates or changes a record, books something, or otherwise changes outside information, add an instruction that requires confirmation before completion.

4. Connect the correct account

Choose the connect action, complete the outside service's sign-in and approval steps, and return to Aivah. Read the requested access before approving it.

5. Confirm the connection is active

Check the service's visible connection state and selected actions. If the screen does not show an active connection, do not assume it succeeded.

6. Test one safe action privately

Open the Playground, select the intended Agent, and test one low-risk action with non-sensitive information. Confirm both the result in Aivah and the result in the outside service.

Expected result

The intended service account shows as connected, only the required actions are enabled, and the controlled test produces the expected result without exposing private values.

Status meanings

  • Active or Connected, when shown, means Aivah currently presents the service as connected.
  • Any other state should be handled using the guidance displayed on that service's screen. This guide does not define provider-specific error or expiry states.

Usage credit impact

The guide does not define a credit formula for connected actions. Review the balance and any usage information shown in your workspace before testing or expanding use. Do not estimate a per-action cost from this article.

Information stored or shared

A connected action can exchange information between Aivah and the outside service. What is exchanged depends on the service, the account you connect, the action you allow, and the request you make.

Use test information first. Do not include private customer records unless your organization has approved that use and the specific connected action.

Limits and permanent actions

  • Available services, sign-in methods, and actions can vary.
  • An outside action can have an immediate effect in another system.
  • Aivah's connection screen does not replace your organization's access review in the outside service.
  • Require confirmation and human review for deletion, unrestricted messaging, financial changes, or other irreversible decisions.

Common problems and recovery

ProblemWhat to try
The service is not shownClear the search, confirm you are in Integrations → MCP, and check whether the service is available to your account.
Sign-in does not finishReturn to the service details, confirm you used the correct account and organization-approved method, then try the on-screen connection flow again.
The wrong account was connectedStop testing, review the visible connection, and use the available connection controls before connecting the intended account.
An action is unavailableReview the actions selected for that service. Enable only the missing action if it is approved and necessary.
The action fails in the PlaygroundConfirm the connection is active, verify the action is allowed, retry with non-sensitive test data, and check the outside service for the result.
The action has an unexpected effectStop further tests, preserve the relevant time and steps, review the outside service, and contact your administrator or Aivah support without sending secrets.

Next step

Test the AI employee in the Playground, then review privacy, consent, and safe data handling before allowing public use.

Keep going