Integration

WhatConverts integration

WhatConverts tracks marketing leads (phone calls, web forms, chats, emails, text messages, transactions and more) back to the source, medium, campaign and keyword that produced them. An agent can list leads filtered by date range, lead type, status, quotable state, quote or sales value, contact phone or email, spam or duplicate flags and marketing attribution, read one lead with its call details, recording links, transcriptions and lead analysis, and, with an agency key, list and read the accounts and their profiles. Creating and editing leads, and creating, editing or deleting accounts and profiles, are not exposed. Authentication is HTTP Basic with the API token as username and the API secret as password, generated under Integrations, API Keys (a profile key, or an agency master account key). Each key allows 10,000 requests per day.

Connect WhatConverts How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with WhatConverts

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.

Account, 2 operations

get_accountGet accountGETGet one account by account_id (from list_accounts): name, creation date and its profiles. Needs an agency master account key.
list_accountsList accountsGETList the accounts of an agency, with the profiles of each, 25 per page by default (up to 250). Needs an agency master account key.

Lead, 2 operations

get_leadGet leadGETGet one lead by its lead_id (from list_leads): type, status, attribution (source, medium, campaign, keyword), contact, call details, recording links, transcriptions and lead analysis.
list_leadsList leadsGETList leads, newest first, 25 per page by default (up to 2500, page with page_number). start_date defaults to the current date (UTC); a date range covers at most 400 days.

Profile, 2 operations

get_profileGet profileGETGet one profile of an account by profile_id (from list_profiles): its name and creation date. Needs an agency master account key.
list_profilesList profilesGETList the profiles of one account (account_id from list_accounts), 25 per page by default (up to 250). Needs an agency master account key.

Use WhatConverts from Claude Code, Cursor or Codex

Connect WhatConverts in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its WhatConverts 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 WhatConverts

Create your workspace
Sign up free. Nothing to install.
Connect WhatConverts once
Add your WhatConverts 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.