Integration

LeadTable integration

LeadTable is a lead management platform for agencies. With it an agent can list and create customers and their tables (campaigns), create, read, search, update, move and re-status leads, attach and download lead files, register and remove event webhooks, add portal pages to customers and send WhatsApp messages to leads. Leads are personal data. Inbound webhook tokens, customer-login magic links and pre-authenticated file links are not returned. Authentication sends two headers: the agency's API key (generated in LeadTable's settings) in x-api-key and the agency account email in email.

Connect LeadTable How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with LeadTable

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.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

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

Lead, 5 operations

create_leadCreate leadPOSTAgents: ask firstCreates a lead in a table from question and answer pairs and returns its id. Leads are personal data. Set notifications to true to also run the table's automations; leave it out to run none.
get_leadGet leadGETAgents: ask firstReturns one lead (personal data): contact name, email, phone, status, source, description, history, funnel data and its profile (leadData: answers by column name, by question title, and as title and value rows).
list_table_leadsList table leadsGETAgents: ask firstLists the leads of one table, page by page: contact name, email, phone, status, source, history and dates (personal data). Profile answers are not included: call get_lead for them.
move_leadsMove leadsPOSTAgents: ask firstMoves or copies one or more leads from one table to another (mode move or copy). toCustomerID must own the target table. Map old statuses to new ones with statusReplacement, or set one newStatus.
search_leads_by_emailSearch leads by emailGETAgents: ask firstFinds leads by email address across all the agency's customers (matched in lowercase), page by page. Returns contact name, email, phone, status, source and description: personal data.

Table, 4 operations

create_tableCreate tablePOSTAgents: ask firstCreates a table (campaign) for a customer and returns its id. Statuses come from status (a new status template), else statusTemplateID, else the agency's first status template; with no template at all it fails (404).
create_table_from_templateCreate table from templatePOSTAgents: ask firstCreates a table (campaign) for an active customer from an agency table template (from list_table_templates), which sets its statuses, views and automations. Returns the new table id and name.
get_tableGet tableGETAgents: ask firstReturns one table (campaign): name (occupation), archived and inactive flags, creation date, owning customer and agency ids and stats (lead counts, status counts, WhatsApp message counts).
list_tablesList tablesGETAgents: ask firstLists one customer's tables (campaigns), page by page, each with id, name (occupation), archived flag, dates, lead counts and stats. A table id feeds list_table_leads, create_lead and get_table.

Customer, 3 operations

create_customerCreate customerPOSTAgents: ask firstCreates a customer in the agency when a customer slot is free and returns its id. It can also create customer logins (people who may sign in to the customer's portal) and attach portal pages.
get_customerGet customerGETAgents: ask firstReturns one customer: name, description, archived and inactive flags, creation date, owning agency id and stats (lead counts, status counts, table count, WhatsApp message counts).
list_customersList customersGETAgents: ask firstLists the agency's customers, page by page, each with id, name, archived flag, creation date and stats. A customer id feeds get_customer, list_tables and create_table.

Lead file, 3 operations

download_lead_fileDownload lead fileGETAgents: ask firstDownloads one file attached to a lead and stores it as a file. Pass the blobURL from list_lead_files as fileID.
list_lead_filesList lead filesGETAgents: ask firstLists the files attached to a lead: file name, size, MIME type, upload date and blobURL. Pass a blobURL as fileID to download_lead_file.
upload_lead_fileUpload lead filePOSTAgents: ask firstUploads one file and attaches it to a lead. The file then appears in list_lead_files.

Webhook, 3 operations

create_webhookCreate webhookPOSTAgents: ask firstRegisters a URL that LeadTable calls with JSON on one event (topic) for a table, a customer or the whole agency. Returns externalHookId: keep it for delete_webhook.
delete_webhookDelete webhookDELETEAgents: ask firstRemoves a webhook by the externalHookId that create_webhook returned; LeadTable stops calling its URL. To remove one by its URL instead, use delete_webhook_by_url.
delete_webhook_by_urlDelete webhook by urlDELETEAgents: ask firstRemoves a webhook by its URL and layer, for one whose externalHookId is unknown: give campaignID for a table webhook or customerID for a customer webhook. LeadTable stops calling the URL.

Customer page, 2 operations

add_customer_pageAdd customer pagePOSTAgents: ask firstCopies a page from a page template onto a customer's portal and returns the new page instance id. Take pageInstanceID and the page's variables from list_page_templates; give a value for every variable.
remove_customer_pageRemove customer pageDELETEAgents: ask firstDeletes a page instance from a customer's portal; this cannot be undone. The page must belong to that customer and to your agency.

Agency, 1 operation

get_agencyGet agencyGETAgents: ask firstReturns the agency the API key belongs to: id, account email, domain, creation date and aggregated stats (customer and table counts, lead counts per status, WhatsApp message counts).

Credentials, 1 operation

verify_credentialsVerify credentialsGETAgents: ask firstChecks that the API key and agency email of the connection are valid and returns auth true when they are. Use it to test a LeadTable connection.

Lead description, 1 operation

update_lead_descriptionUpdate lead descriptionPUTAgents: ask firstOverwrites a lead's description with the given text; the previous description is replaced, not appended to. Returns the updated lead (personal data).

Lead field, 1 operation

set_lead_fieldSet lead fieldPUTAgents: ask firstSets one profile answer on a lead: updates the answer to the question, or adds the question when the lead lacks it. Other fields are kept. Returns the updated lead (personal data).

Lead status, 1 operation

change_lead_statusChange lead statusPOSTAgents: ask firstSets a lead's status. The status must belong to the table's status template (ids from list_status_templates). Set sendMails to true to also run the table's automations; leave it out to run none.

Page template, 1 operation

list_page_templatesList page templatesGETAgents: ask firstLists the agency's page templates with their pages: page instance id, name and the variables each page needs. Use them in add_customer_page or in pages on create_customer.

Status template, 1 operation

list_status_templatesList status templatesGETAgents: ask firstLists the agency's reusable status templates, sorted by name, each with its statuses (id, name, color) and its inbox status id. Status ids feed change_lead_status; template ids feed create_table.

Table template, 1 operation

list_table_templatesList table templatesGETAgents: ask firstLists the agency's table templates, newest first, page by page, each with id, name and icon. Pass a template id to create_table_from_template.

Webhook sample, 1 operation

get_webhook_sampleGet webhook sampleGETAgents: ask firstReturns one shortened test sample of what a webhook topic sends for a table (not the full live body), as a one-item list. Samples carry lead contact data (personal data).

Whatsapp message, 1 operation

send_whatsapp_messageSend whatsapp messagePOSTAgents: ask firstSends a WhatsApp text message to a real person: a lead (leadID) or an unassigned conversation (unassignedConversationID), give exactly one. The customer needs a WhatsApp number; the 24-hour window applies.

Use LeadTable from Claude Code, Cursor or Codex

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

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