Integration

Cymbal integration

Cymbal is a marketing platform for live-event venues and promoters (email, SMS, ads, landing pages) that syncs with ticketing providers. Its Partners API lets you push events, ticket orders, cart events (which drive abandoned-cart automations) and contacts with their email and SMS opt-ins into an organization, read email and SMS campaign analytics (recipients, opens, clicks, attributed tickets and revenue) and list landing pages with their public URL and publication status. Uploads are queued and answer with an acknowledgement, not the created record; orders, cart events and contacts carry personal data. Authentication is a partner API token created for the organization in the Cymbal manager (Settings, Integrations) and sent in the Cymbal-Partner-API-Key header; a 403 means the token was revoked.

Connect Cymbal How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Cymbal

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.

Campaign analytics, 1 operation

list_campaign_analyticsList campaign analyticsGETAgents: ask firstLists the organization's email and SMS campaigns with their analytics: recipients, opens, unique link clickers, unsubscribes, undelivered, attributed tickets sold and attributed revenue (in cents). Paged.

Cart event, 1 operation

create_cart_eventsCreate cart eventsPOSTAgents: ask firstUploads up to 100 cart events (a person who started buying tickets: personal data) that drive Cymbal's abandoned-cart automations, which can message those people. Returns any rejected entries.

Contact, 1 operation

create_contactCreate contactPOSTAgents: ask firstCreates a contact (personal data) and subscribes or unsubscribes them to email or SMS marketing via opt_ins: true subscribes, false unsubscribes, left out leaves it unchanged. Acts on a real person; answers code 0.

Event, 1 operation

create_eventsCreate eventsPOSTAgents: ask firstUploads events (shows) into the Cymbal organization for its marketing; queued, answers code 0 and success, no id. Each needs id, url, name, image_url, start_datetime and location. Changes real data.

Order, 1 operation

create_ordersCreate ordersPOSTAgents: ask firstUploads ticket orders with their customers (personal data) and marketing opt-ins; an opt-in true subscribes that customer to email or SMS marketing. Queued; answers code 0, no id. Acts on real people.

Page, 1 operation

list_pagesList pagesGETAgents: ask firstLists the organization's landing pages with type (presale, drop, other), status, public URL, publish and schedule dates, and the presale code and event or the drop time. Paged; poll it, there is no webhook.

Use Cymbal from Claude Code, Cursor or Codex

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

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