Skip to main content

Replace credentials for AI agent tools and connectors

AI agent tools and connectors use credentials you saved in Assembled to call your other systems: custom APIs, MCP servers, database connectors, and custom actions. Use these steps to replace each of those credentials. This is separate from reconnecting your helpdesk.

If you're here because of the November 13, 2026 security incident: Replace every credential saved in your tools and connectors, in production and in any sandbox setups. Reconnecting your helpdesk doesn't update these. For more about the incident, see November 13, 2026 security incident.

Who does this

  • An Assembled admin who can edit your tools and connectors.
  • An admin or engineer for each system your tools connect to, who can create and revoke credentials there.

Before you start

  • List every API, MCP server, database connector, and custom action your AI agents use, in production and in any sandbox setups.
  • For each one, find who can create a replacement credential in that system.

Steps

  1. In each connected system, create a replacement API key, token, or password.
  2. In Assembled, go to Configure > Tools and connectors and replace each saved credential with its new one.
  3. Test each affected tool or action to confirm it works with the new credential.
  4. Once each one works, revoke the old credential in the system that issued it. If you already updated a credential since the incident, revoke the old one rather than replacing it again.
  5. After your helpdesk is reconnected, test a real AI agent handoff to confirm it reaches your team. You don't need to redeploy your AI agent for handoffs to work again.

How to confirm it's working

  • Each tool and action you tested returns the results you expect.
  • A test conversation hands off to your team as expected.
  • The admins for each connected system confirm the old credentials are revoked.

When you'll see data

Test each tool or action right after you save its new credential.

Restoring missed data

There's no data to backfill for tools and connectors. If you see conversations that were affected while a credential was out of date and you'd like help reviewing them, contact Support.

Things to watch for

  • Replace custom action tokens too. Old tokens in custom actions can keep failing with 401 errors even after your helpdesk is reconnected.
  • Include sandbox setups. Replace credentials in sandbox tools and actions as well as production.
  • Test before you revoke. Confirm each tool works with its new credential, then revoke the old one.
  • Your Assembled API keys are different. API keys your team created in Assembled to call our API don't need to change. This article covers credentials for other systems that you saved in Assembled.
  • Ask about model provider keys. If you supplied your own AI model provider key, contact Support for instructions for your account.

Need help?

If a tool or action still fails after you replace its credential, contact our Support team and include the error text you see. Please don't send keys, tokens, or passwords by email or chat.

Still have questions?