Integration

Zapier integration

Trigger Zapier automations (Zaps) via webhook. Send JSON, XML, or form-encoded data to a Zapier webhook catch URL to start any Zap. Supports POST, PUT, and GET. Send an array of JSON objects to trigger the Zap once per object. No authentication required - the webhook URL itself serves as the secret. Maximum payload size 10MB (2MB for Catch Raw Hook). Append /silent/ to a Catch Raw Hook URL for an empty response.

Connect Zapier How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Zapier.Built from the 1 Zapier tool below, on the connection you add once.

Common Zapier use cases

custom triggers
external integration
API integration
event-driven automation

What you can do with Zapier

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.

trigger_webhookTrigger webhookPOSTTriggers a Zap via its webhook catch URL with custom data.

Zapier API rate limits

4,000 requests per minute

20,000 requests every 5 minutes per user (1,000 requests every 5 minutes per Zap on legacy webhook routes). Exceeding returns 429. No rate-limit response headers are provided; retry any non-200 response using exponential backoff.

These are the limits Zapier documents, not ones LiveContext measured. They can change and often depend on your plan, so check the Zapier documentation for current values.

Use Zapier from Claude Code, Cursor or Codex

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

Create your workspace
Sign up free. Nothing to install.
Connect Zapier once
Zapier needs no credential, so its tools work immediately.
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.

Zapier integration FAQ

What can you do with the Zapier integration?

LiveContext exposes 1 operation on Zapier, covering webhook. Common uses include custom triggers, external integration and API integration.

What are the Zapier API rate limits?

Zapier documents 4,000 requests per minute. 20,000 requests every 5 minutes per user (1,000 requests every 5 minutes per Zap on legacy webhook routes). Exceeding returns 429. No rate-limit response headers are provided; retry any non-200 response using exponential backoff. Limits are set by Zapier and can depend on your plan.