Integration

DigitalPilot integration

DigitalPilot identifies the companies visiting a website (reverse IP lookup) and ties each visit to the campaign that drove it. Read a workspace's visit reports (overview by company, channel, UTM, target-account visits, daily dashboard) and one company's raw visit activity, list and stage captured leads, manage lead stages, target-account lists and their domains, find people at a company and reveal or validate an email address (billed in workspace credits), and manage the workspace's webhooks. CSV and Excel report downloads are not offered (each read returns JSON). API access needs the Max plan. Authentication is the workspace's API key, sent in the x-api-key header; every route also takes the workspace id, which the API calls a tag.

Connect DigitalPilot How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with DigitalPilot

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.

Target account, 5 operations

add_target_accountAdd target accountPOSTAdds a company domain to the workspace's default target-account list, so its visits are tracked as a target account.
add_target_account_to_listAdd target account to listPOSTAdds a company domain to one target-account list of the workspace.
list_target_accountsList target accountsGETLists the target-account domains of the workspace across all its lists, paginated, with their count.
list_target_accounts_in_listList target accounts in listGETLists the target-account domains of one target-account list, paginated, with their count.
remove_target_accountRemove target accountDELETERemoves a company domain from one target-account list of the workspace.

Lead stage, 4 operations

create_lead_stageCreate lead stagePOSTAdds a custom lead stage, placed between Qualified and Converted. Stage names must be unique.
delete_lead_stageDelete lead stageDELETEDeletes a custom lead stage; its leads move to New. The default stages (New, Qualified, Converted, Unqualified, Lost) cannot be deleted.
list_lead_stagesList lead stagesGETLists the workspace's lead stages in pipeline order: New, Qualified, custom stages, Converted, Unqualified, Lost. Use a stage id with update_lead or list_leads.
update_lead_stageUpdate lead stagePUTRenames a custom lead stage or changes its order among the custom stages (always between Qualified and Converted). Default stages cannot be changed. Leave a field out to keep it.

Target account list, 4 operations

create_target_account_listCreate target account listPOSTCreates a target-account list in the workspace and returns its list_id.
delete_target_account_listDelete target account listDELETEDeletes a target-account list from the workspace.
list_target_account_listsList target account listsGETLists the workspace's target-account lists with their list_id, name, number of accounts and dates.
update_target_account_listUpdate target account listPUTRenames a target-account list.

Webhook, 4 operations

create_webhookCreate webhookPOSTRegisters a webhook: DigitalPilot then POSTs the chosen events (target-account visits, high-intent visits, captured leads) to the url. The docs do not say how a signing secret is set for it.
delete_webhookDelete webhookDELETEDeletes a webhook of the workspace, named by its id or its url (give one).
list_webhooksList webhooksGETLists the workspace's webhooks: id, url, subscribed events, whether a signing secret is configured, and dates. The secret itself is not returned.
update_webhookUpdate webhookPUTUpdates a webhook of the workspace, sent as webhookURL and subscriptions (the docs do not say how the webhook to update is matched; the body names it only by its url).

Lead, 2 operations

list_leadsList leadsGETLists the leads captured in the workspace (forms and Meta lead ads), with email, channel, stage, the submitted form fields (personal data) and time. Works only when lead capture is enabled for the workspace.
update_leadUpdate leadPUTMoves a captured lead to another stage. When the lead has a Facebook lead id or fbclid, DigitalPilot also sends a lead-stage event to Meta's Conversions API.

Channel report, 1 operation

get_channel_reportGet channel reportGETReturns the workspace's visit metrics grouped by traffic channel (unique visitors, sessions, high-intent sessions, activities) with totals, for the last days or a date range.

Contact, 1 operation

search_contacts_by_domainSearch contacts by domainPOSTFinds people working at a company (personal data: name, position, seniority, department, LinkedIn, phone), 10 per call, at no credit cost. Emails stay null until reveal_contact_email unlocks them. Read-only.

Contact email, 1 operation

reveal_contact_emailReveal contact emailPOSTUnlocks the email of a contact found by search_contacts_by_domain and adds the contact to the Lead Center. Costs 2 credits for a decision maker, else 1; already unlocked emails are free. Answers 402 without unlocking when credits are short.

Dashboard report, 1 operation

get_dashboard_reportGet dashboard reportGETReturns the workspace's daily time series and totals of accounts, unique visitors, sessions, high-intent sessions, leads and assisted attribution for a date range.

Email address, 1 operation

validate_emailValidate emailPOSTValidates an email address (format, typos, disposable domain, MX records, then the mailbox itself). Costs 1 workspace credit per completed validation; answers 402 when the balance is below 1.

Target account report, 1 operation

get_target_account_visits_reportGet target account visits reportGETReturns visit and engagement metrics of the workspace's target accounts (domains on its target-account lists), for the last days or a date range, optionally for one list or channel.

Utm report, 1 operation

get_utm_reportGet utm reportGETReturns the workspace's visit metrics grouped by UTM source and medium, with totals, for the last days or a date range.

Visit activity, 1 operation

list_domain_activitiesList domain activitiesGETLists the raw visit activities of one company domain in the workspace, paginated: each with its visitor_id, session_id, time and params (channel, high_intent). Dates are read in the workspace timezone.

Visitor company report, 1 operation

get_overview_reportGet overview reportGETLists the companies (domains) that visited the workspace's website, paginated, with unique visitors, sessions, channels and a high-intent flag, for a date range.

Webhook delivery, 1 operation

test_webhook_deliveryTest webhook deliveryPOSTSends one sample event payload as a real HTTP POST to a URL and reports each delivery (ok, status). Use it to check a receiver before or after create_webhook.

Use DigitalPilot from Claude Code, Cursor or Codex

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

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