Integration

Pitchlane integration

Pitchlane makes personalized prospecting videos: each video in a campaign is rendered from a template using one lead's variables (for example their website and first name). List campaigns and read each campaign's variable schema and lead schema mapping, create or update a single video, import many videos at once with optional rendering, and manage webhook subscriptions for video events (created, rendered, viewed, started, finished). Authentication is a Pitchlane API key sent in the X-API-Key header.

Connect Pitchlane How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Pitchlane

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.

Webhook, 6 operations

create_campaign_webhookCreate campaign webhookPOSTSubscribes a URL to a video event in one campaign only. create_webhook does the same for all campaigns. Returns the webhook id.
create_webhookCreate webhookPOSTSubscribes a URL to a video event (for example VIDEO_RENDERED). With campaignId only that campaign's events fire it; without, events from every campaign do. Returns the webhook id.
delete_campaign_webhookDelete campaign webhookDELETEDeletes a campaign's webhook subscription, identified by its URL and trigger. For a webhook not tied to a campaign use delete_webhook.
delete_webhookDelete webhookDELETEDeletes a webhook subscription that is NOT tied to a campaign, identified by its URL and trigger. For a campaign's webhook use delete_campaign_webhook.
list_webhooksList webhooksGETLists your webhook subscriptions: id, URL, trigger, creation date and the campaign each one is limited to (null for all campaigns).
update_webhookUpdate webhookPUTUpdates a webhook subscription identified by id: its URL, trigger or campaign. For a webhook tied to a campaign, pass that campaignId; for one that is not, leave campaignId out.

Video, 3 operations

create_videoCreate videoPOSTCreates (or updates) one personalized video in a campaign from a lead's variables and returns its id and shortId. queueForRender decides whether rendering starts at once.
import_videosImport videosPOSTImports many videos into a campaign and returns how many were inserted and how many were duplicates. Videos are rendered only if queueAllVideosForRender or renderTestVideo is true. import_videos_v2 returns more detail.
import_videos_v2Import videos v2POSTImports many videos into a campaign; unlike import_videos it accepts duplicateIdentifierField and also returns upserted, invalidRows, variableIssues and testVideoQueued. Renders only if asked.

Campaign schema, 2 operations

get_campaign_schemasGet campaign schemasGETReturns both a campaign's variable schema and its lead schema mapping, each with an example payload. Read it before create_video or import_videos_v2 to know which keys to send.
get_campaign_variable_schemaGet campaign variable schemaGETReturns a campaign's variable schema (each variable's label, whether it is required, and its url or email validator) and an example variables payload for create_video.

Campaign, 1 operation

list_campaignsList campaignsGETLists all your Pitchlane campaigns with their id, name, creation date, variable schema and an example variables payload.

Lead schema mapping, 1 operation

get_campaign_lead_schema_mappingGet campaign lead schema mappingGETReturns a campaign's lead schema mapping (its keys are what goes in an import request body) and an example request payload.

Use Pitchlane from Claude Code, Cursor or Codex

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

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