Integration

GenPage integration

GenPage builds a personalized landing page for every lead. Push leads into a campaign (single, batch or a workspace import), follow the queued job and read back each lead's page link; search and read leads, run paid enrichments, group leads into audiences linked to campaigns, give a campaign a design from a template or from GenPage's AI builder, publish or unpublish it, and read campaign analytics, form submissions, credits, templates, brandings and variables. API access needs a Pro plan or higher; AI generation and enrichments spend the account's credits. The API allows 120 requests per minute per key (HTTP 429 beyond). API-token management routes and the Zapier-only test and lead-creation routes are not exposed. Authentication is a GenPage API key (starts with sk-proj-, created in the dashboard and bound to one workspace) sent as a Bearer token.

Connect GenPage How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with GenPage

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.

Lead, 6 operations

get_leadGet leadGETReturns one lead with every field: contact and company data, personalized page link, all variables (including enrichment results), audiences and pending enrichments.
import_leads_to_workspaceImport leads to workspacePOSTImports leads into a workspace without a campaign (link them later through an audience). Usually queued with a job_id; with sync true and nothing else, answers with the result.
list_job_leadsList job leadsGETLists the leads a job created or updated, each with its personalized page link (genpage_url). Answers HTTP 503 NO_LEADS while the job has produced none yet: retry.
search_leadsSearch leadsGETSearches a workspace's leads by name, email or company, filtered by campaign, audience or page engagement; returns up to 100 with their personalized page link.
upsert_leadUpsert leadPOSTCreates or updates one lead in a campaign as a queued job and returns its job_id; poll get_job_status, then list_job_leads for the page link.
upsert_leadsUpsert leadsPOSTCreates or updates leads in a campaign in one queued job and returns its job_id; poll get_job_status, then list_job_leads for each lead's page link.

Audience, 3 operations

create_audienceCreate audiencePOSTCreates an audience (a named segment of leads) in a workspace, optionally filled with leads at once. Returns its audience_id.
delete_audienceDelete audiencePOSTDeletes an audience for real. Only the segment is removed: its leads stay in the workspace and remain findable with search_leads.
list_audiencesList audiencesGETLists the workspace's audiences (named segments of leads) with their lead counts. Audience 0 is the built-in Default Audience holding every lead in no audience of its own.

Audience campaign link, 2 operations

link_audience_to_campaignLink audience to campaignPOSTLinks an audience to a campaign so its leads get that campaign's personalized pages.
unlink_audience_from_campaignUnlink audience from campaignPOSTDetaches an audience from a campaign. Only the link goes; the audience, its leads and pages already generated stay.

Audience lead, 2 operations

add_leads_to_audienceAdd leads to audiencePOSTAdds existing leads to an audience. Leads already in it are skipped; returns how many were added and the new lead count.
remove_leads_from_audienceRemove leads from audiencePOSTRemoves leads from an audience. The leads themselves are kept in the workspace.

Campaign, 2 operations

create_campaignCreate campaignPOSTCreates an empty campaign. It has no page design yet: apply one with apply_template or generate_page_design, then publish_pages, or its pages render blank.
list_campaignsList campaignsGETLists the campaigns of a workspace (id, name, slug). A campaign holds the page design and branding its leads' personalized pages are built from.

Page, 2 operations

publish_pagesPublish pagesPOSTPublishes a campaign's draft design: it goes live at once for every page of the campaign, including pages generated earlier, replacing what was live.
unpublish_pagesUnpublish pagesPOSTTakes a campaign's pages offline: every generated link then shows a not-live-yet page. The design stays as a draft and can be published again.

Page design, 2 operations

generate_page_designGenerate page designPOSTHas GenPage's AI builder design or edit a campaign's page from a prompt; returns a run_id to poll with get_page_generation_status. Spends credits.
get_page_designGet page designGETReturns a campaign's current page design (HTML and CSS) and its state: has_design, is_live (published) and has_unpublished_changes.

Template, 2 operations

apply_templateApply templatePOSTCopies a template's design onto a campaign, overwriting its current draft design. No credits. Publish with publish_pages to put it live.
list_templatesList templatesGETLists page templates a campaign can use: workspace templates built in the dashboard and GenPage's premade ones. Pass template_id to apply_template.

Api key, 1 operation

verify_api_keyVerify api keyGETChecks the API key: returns the account it belongs to and the workspace_id it is bound to (empty for older keys that may act on every workspace of the account).

Branding, 1 operation

list_brandingsList brandingsGETLists the brandings (logo, colours, fonts) of a workspace, to pick a branding_id for create_campaign. Brandings are built in the GenPage dashboard.

Campaign analytics, 1 operation

get_campaign_analyticsGet campaign analyticsGETReturns page performance per campaign: share of generated pages visited, share of visitors who clicked, time on page, visits and clicks. All campaigns unless campaign_ids[] is set.

Campaign lead, 1 operation

list_campaign_leadsList campaign leadsGETLists a campaign's leads newest first; pass created_after or last_lead_id from the previous call to get only new ones. Up to 100 per call.

Credits, 1 operation

get_creditsGet creditsGETReturns the workspace's credit position: remaining credits in the account pool, this workspace's usage and cap, the plan identifier and the renewal date.

Form submission, 1 operation

list_form_submissionsList form submissionsGETLists recent form submissions on the generated pages, newest first. Without workspace_id it covers every workspace the key can reach. Up to 100 per call.

Lead enrichment, 1 operation

enrich_leadsEnrich leadsPOSTResearches existing leads (LinkedIn profile, company or person AI analysis, recent posts); returns a job_id for get_job_status. Spends credits per lead and type.

Lead job, 1 operation

get_job_statusGet job statusGETReturns a lead job's status (pending, processing, step_linkedin, step_import, completed or error) with processed and total rows. Once completed, call list_job_leads.

Page design run, 1 operation

get_page_generation_statusGet page generation statusGETReturns the status of an AI design run: queued, running, success, error or cancelled. On success read the result with get_page_design.

Variable, 1 operation

list_workspace_variablesList workspace variablesGETLists a workspace's lead variables (columns): defaults such as first_name, email, company_name, company_domain, linkedin_profile_url, and custom ones. Use them as keys in lead values.

Workspace, 1 operation

list_workspacesList workspacesGETLists the workspaces the API key can reach (one for a workspace-bound key). Its id is the workspace_id every other tool needs.

Use GenPage from Claude Code, Cursor or Codex

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

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