Kimi Code + CallMiner

Kimi Code runs the task; the CallMiner connector supplies only the operations and resources allowed by the account you authorize. The Composer selects Kimi Code, asks for CallMiner access before sending, and keeps both choices in one task draft.

Sign in to send. You only pay for what you use.

Connect CallMiner using the Connectors control before sending. Authorization opens separately and your draft stays here.

How the combination works

Kimi Code plans and executes. CallMiner supplies authorized app access.

Kimi Code supplies a repository-focused coding loop for reading large code contexts, editing files, and running validation in a cloud workspace.

Better intelligence for better experiences. The industry leader in AI-powered conversation intelligence to supercharge your contact center and improve customer experience (CX).

  • Kimi Code

    Owns the task loop, model calls, cloud computer, tool choices, progress and final result.

  • CallMiner connector

    Supplies the currently exposed operations for the authorized CallMiner account. It does not promise every feature in the CallMiner product.

  • Permission boundary

    The connected identity, granted provider scopes, organization policy, resource sharing and the task's explicit instruction all constrain what Kimi Code can do.

Setup and first task

Connect one CallMiner account and verify one known resource.

The Composer preselects Kimi Code with Kimi K3. Start read-only when possible, then expand to write operations only after the account and resource boundary are clear.

01

Open the Kimi Code Composer

The Composer above carries Kimi Code, Kimi K3, and CallMiner. Add a precise target and expected result; the draft stays on this page during sign-in or connector authorization.

02

Authorize the intended CallMiner account

Review the CallMiner account, workspace and permissions on the authorization screen. Your organization's policies or administrator approval may limit which resources the connection can access.

03

Run and verify a bounded task

Name one CallMiner resource you can already access and ask the agent to check whether a read operation is available. If it is, retrieve and summarize that resource without changing it. If it is not, ask the agent to explain the missing operation or permission. Open the same resource in CallMiner and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.

Access, cost and limits

What to verify before scaling Kimi Code + CallMiner

Repository work that benefits from Kimi Code's coding workflow and long-context model options.

Establish with the first run

  • Kimi Code and Kimi K3 remain selected after sign-in.
  • CallMiner shows the intended connected account before the task is sent.
  • The returned data matches one known source resource, with write actions excluded until separately authorized.

Still depends on your setup

  • A catalog listing does not guarantee every CallMiner website feature is available as an agent operation.
  • OAuth scopes do not replace organization policy, resource sharing or a precise task instruction.
  • Total task cost can include model tokens, active computer time, paid tools, connectors and the provider's own plan or quota.

Verification and recovery

Check CallMiner itself before trusting the result.

Open the same resource in CallMiner and compare it with the agent's result. Check the account, resource identifier and current content before using the output for another task.

  • Connection troubleshooting

    If CallMiner access fails, check the connected identity, resource sharing and requested permissions. Reconnect an expired or revoked account in connector settings. If the connection is healthy but an operation is unavailable, changing accounts may not resolve it.

  • Writes need explicit scope

    Name the target record and exact allowed change. A request to summarize, analyze or draft does not authorize sending, publishing or deleting.

  • Re-check current state

    For decisions or follow-up writes, open the resource in CallMiner and check its current state. A successful earlier read may already be stale.

Common questions

Run a bounded CallMiner task with Kimi Code.

Open the Composer