Mr. AIMr. AI Help Center

Connect business systems and use Live Tools safely

Distinguish Connected Systems, API Keys, Outbound Events and Builder Live Tools before authorizing an integration.

On this pageHow can Mr. AI work with data in another business system?Common questionsWhen should the AI use a Live Tool?Live reads and external changesCheck the result

How can Mr. AI work with data in another business system?

Mr. AI separates a Connected System, which owns access to that system, from a Live Tool, which reads approved data or performs an explicitly authorized write. Configure infrastructure in Integrations and the tool’s conversation use in Conversation Builder.

Open this task in Mr. AI ↗

Connected Systems and Live Tools controls
Connected Systems and Live Tools controls. Actual interface with synthetic examples; names, counts and prices are illustrative. Availability can vary by account. Select the image to enlarge it.
  1. 1

    Open Settings, then Integrations, and review Connected Systems.

  2. 2

    Use the provider’s supported connection flow and inspect the permissions before authorizing it.

  3. 3

    Open Conversation Builder, then Live Tools, to configure the operation and its eligible stages.

  4. 4

    Validate required fields and use an appropriate controlled Test.

  5. 5

    Review any separate approval for an external write Test before authorizing a real side effect.

  6. 6

    Inspect Technical Activity for connection failures and the business-usage timeline for customer-facing use.

  • API Keys authenticate the specific API capability they were created for; a chat-only System API key is not a general integration credential.
  • Outbound Events notify an external destination about supported business events.
  • Opening a setup link or selecting a stage does not authorize a write or grant access to another account.

Common questions

Is every connected URL a Google connection?

No. Use the explicit supported provider flow; a hostname alone does not establish an OAuth connection.

Does Auto Apply & Publish approve external write Tests?

No. These are separate permissions.

Where do I change the business action?

Use the Action in Builder for business intent and the Live Tool for the authorized external operation.

Design the conversation journey

Connect your application with the System API

Build & Manage with AI

When should the AI use a Live Tool?

Reading current information and making an external change are different operations.
1. Read live information from a connected system when the relevant tool is available. 2. An external change needs the required permission and confirmation; reviewing a proposal is not executing it.
  • State the operation’s purpose, when to use it and when not to use it.
  • Specify required inputs, their source and the minimum useful result fields. Ask for missing information before execution.
  • Use stage eligibility to limit where the tool can run. A selected tool with missing fields has not executed.
  • Treat external text as returned data, not instructions that can override account rules.

Live reads and external changes

Is a read Test the same as a write Test?

No. A write Test can create a real external effect and needs its separate authorization. Auto Apply & Publish does not grant that authorization.

What if a write times out?

Inspect its recorded result and Technical Activity. Do not repeat an uncertain external write blindly; a timeout is not proof the destination did nothing.

Check the result

Test a read tool first and inspect returned facts. Any write needs clear authorization and a defined scope.

Was this article helpful?

Your feedback helps us review and improve these guides.