How Do You Connect Multiple Accounts of the Same App in Macha?

To connect a second account of an app you already use in Macha, open the Connectors page, click + Add Another on the connected app, and give the new instance its own name, such as "Production Zendesk" and "Sandbox Zendesk". Macha then suffixes each tool with the account name (zendesk_get_ticket__production and zendesk_get_ticket__sandbox), so every agent knows which account it's acting on.

Watch it

How many accounts of the same app can you connect?

Connectors aren't one-per-app. If your company runs two Google Workspace accounts, one for the main company and one for a separate team, you can connect both, name each one, and give your agents access to either or both. The same goes for two Zendesk instances (production and sandbox), two Stripe accounts for different entities, or separate accounts per product line. Multi-instance connectors are included in Macha's single plan, so there's no extra charge for the second account.

How does the agent know which account a tool belongs to?

The obvious worry with two of the same app is confusion about which account the agent is acting on. Macha handles it automatically: when you assign more than one instance of the same connector to an agent, it adds a suffix to the tool names and prefixes each tool description with the account, for example "[Account: Production]".

So if you name your two Google accounts "Google Main Company" and "Google Europe Team," you don't get one ambiguous "Read Google Doc" tool. You get two, one labeled for each account. Nothing needs configuring beyond giving each instance a distinct name.

How should you name connected accounts?

The clearer the name, the more reliably the agent picks the right account. "Google Workspace 1" and "Google Workspace 2" tell the model nothing. "Google Main Company" and "Production Zendesk" tell it what each account is for. You can also use the names in the agent's instructions: "Always use Google Main Company for internal documents and Google Europe Team for anything related to that team. If unsure, search both."

When is connecting two accounts useful?

• Scope an agent to one account. A support agent for Brand A only gets Brand A's Zendesk tools, so it can't touch Brand B's tickets.
• Give one agent both. A reporting agent can read across both Zendesk instances to produce a combined view.
• Keep things tidy after a merger. Two help desks from an acquisition can both live in Macha, with agents scoped per brand or shared as needed.

The principle is the same as everywhere else in Macha: you decide which tools, and now which accounts, each agent can use.

Frequently asked questions

Can I connect two accounts of the same app? Yes. Click "+ Add Another" on the Connectors page, name each instance, and assign agents to either or both.

How does the agent tell the accounts apart? Macha suffixes the tool names by account (for example zendesk_get_ticket__production) and adds the account name to each tool description, so each tool clearly belongs to one account.

Can one agent use both accounts? Yes. Give it tools from both, or scope it to just one.

Does this work for Zendesk, Stripe, etc.? Yes. It applies to connectors generally, so two Zendesk instances or two Stripe accounts work the same way.

Connect your accounts: add a second instance of any app and scope your agents per account. $50 of free usage, no credit card required. Start free.