Integration

SalesLens integration

SalesLens is an AI call-analysis tool for sales teams. Send a conversation for analysis, either as a recording SalesLens downloads from a URL or as a text transcript, attributed to an employee and optionally a category, conversation type and contact; and look up the company name, the employees (their external ids) and the evaluation categories to use. Reading analysis results, conversations and webhooks needs SalesLens OAuth 2.0, available only on request to SalesLens, so those routes are not exposed. Authentication is an API token created by the account owner in the Integration tab of SalesLens, sent as is in the Authorization header (no Bearer prefix).

Connect SalesLens How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in SalesLens.Built from the 5 SalesLens tools below, on the connection you add once.

What you can do with SalesLens

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Category, 1 operation

list_categoriesList categoriesGETList the company's evaluation categories (id, title, language). Each category has its own questions for scoring a conversation; pass its id as categoryId when uploading.

Company, 1 operation

get_companyGet companyGETGet the name of the company the API token belongs to.

Conversation recording, 1 operation

upload_conversation_recordingUpload conversation recordingPOSTSend a call recording for AI analysis: SalesLens downloads it from downloadRecordUrl and analyses it for the employee (employeeExternalId from list_employees). Returns the stored conversation details.

Conversation transcript, 1 operation

upload_conversation_transcriptUpload conversation transcriptPOSTSend a conversation transcript (text) for AI analysis, attributed to an employee (employeeExternalId from list_employees). Returns the stored conversation details.

Employee, 1 operation

list_employeesList employeesGETList the company's employees (id, externalId, firstName, lastName). Pass externalId as employeeExternalId when uploading a conversation.

Use SalesLens from Claude Code, Cursor or Codex

Connect SalesLens in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SalesLens operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect SalesLens

Create your workspace
Sign up free. Nothing to install.
Connect SalesLens once
Add your SalesLens connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.