Integration

Pingback integration

Pingback is a marketing automation platform (forms, CRM, email newsletters, a blog, segmented lists, automations); this API manages its contacts, called subscribers. Create a subscriber with name, phone, status and custom fields, look one up by email, update their name, phone, status (free, paid or unsubscribed) or custom fields, and add them to or remove them from segmentation lists. These changes can start the automations set up in the account, which may email or message the subscriber. Subscriber records are personal data. The API has no route to list subscribers, segmentation lists or custom fields: Pingback says to ask its support for their ids. Authentication is an API key generated in Pingback under the profile menu, Account information, API Key tab (Pro or Ultra plan; one key per account), sent in the x-api-key header; the API allows 5 requests per second.

Connect Pingback How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Pingback

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.

Subscriber, 3 operations

create_subscriberCreate subscriberPOSTCreates a subscriber from an email, with optional name, phone (E.164), status, custom fields and segmentation lists. Can start the account's automations, which may email or message the subscriber. Answers 409 if the email already exists.
get_subscriberGet subscriberGETReturns one subscriber of your channel by email address: name, phone, status, custom fields, segmentation list ids, and blacklist, unsubscribe, creation and update dates. Personal data.
update_subscriberUpdate subscriberPUTUpdates the subscriber with this email: name, phone (E.164), status, custom fields. Can start the account's automations, which may email them. Custom fields: vendor documents {id, value}, one client sends {label, value}; not verified which works.

Add subscriber, 1 operation

add_subscriber_to_segmentation_listsAdd subscriber to segmentation listsPOSTAdds the subscriber with this email to one or more segmentation lists, used to target email. Can start the account's automations, which may email the subscriber. Returns one membership record per list; 404 if the subscriber or a list is missing.

Remove subscriber, 1 operation

remove_subscriber_from_segmentation_listRemove subscriber from segmentation listDELETERemoves the subscriber with this email from one segmentation list; the subscriber stays in the account. Can start the account's list-removal automations, which may email them. Returns the removed membership record.

Use Pingback from Claude Code, Cursor or Codex

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

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