What can you do with the Drip integration?

LiveContext exposes 20 operations on Drip, covering subscriber, tag, campaign and campaign subscriber. Common uses include Conversion exit, Tag picker UI and Send reporting.

LiveContext

All integrations

Drip integration

Email marketing automation platform for ecommerce. Manage subscribers, track behavioral events, send broadcasts and email-series campaigns, run multi-step workflows, and tag/segment customers. Build personalised lifecycle marketing, abandoned-cart automations, and win-back journeys against the Drip REST API v2.

20 toolsOAuthAPI docs

Connect Drip How integrations work

Common Drip use cases

Conversion exit
Tag picker UI
Send reporting
Audience export
User signup sync
GDPR/CCPA erasure
Campaign discovery
Compliance opt-out
Profile inspection
Workflow discovery

What you can do with Drip

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, 5 operations

POSTcreate_or_update_subscriber
Creates or updates a Drip subscriber.
DELETEdelete_subscriber
Deletes a subscriber and all associated data.
GETfetch_subscriber
Fetches a single subscriber by ID, email, or user_id.
GETlist_subscribers
Lists subscribers in a Drip account with filters.
POSTunsubscribe_subscriber
Globally unsubscribes a subscriber from all Drip mailings.

Tag, 3 operations

POSTapply_tag
Applies one or more tags to a subscriber.
GETlist_tags
Lists all tags configured in the Drip account.
DELETEremove_tag
Removes a tag from a subscriber.

Campaign, 2 operations

GETfetch_campaign
Fetches a single email-series campaign.
GETlist_campaigns
Lists email-series campaigns in a Drip account.

Campaign subscriber, 2 operations

POSTremove_subscriber_from_campaign
Removes a subscriber from one or all email-series campaigns.
POSTsubscribe_to_campaign
Subscribes a user to an email-series campaign.

Event, 2 operations

POSTtrack_event
Records a behavioural event for a subscriber.
POSTtrack_events_batch
Batches up to 1000 event records in one call.

Workflow subscriber, 2 operations

DELETEremove_subscriber_from_workflow
Removes a subscriber from a workflow.
POSTstart_subscriber_in_workflow
Starts a subscriber in a Drip workflow.

Account, 1 operation

GETlist_accounts
Lists Drip accounts the authenticated user can access.

Broadcast, 1 operation

GETlist_broadcasts
Lists broadcasts (one-off emails) in the account.

Custom field, 1 operation

GETlist_custom_fields
Lists all custom-field identifiers configured in the account.

Workflow, 1 operation

GETlist_workflows
Lists automation workflows in the account.

Drip API rate limits

3,600 requests per hour

3,600 requests/hour on standard endpoints; 50 requests/hour on batch endpoints (each batch carries up to 1000 records).

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

Use Drip from Claude Code, Cursor or Codex

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

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

Drip integration FAQ

What can you do with the Drip integration?: LiveContext exposes 20 operations on Drip, covering subscriber, tag, campaign and campaign subscriber. Common uses include Conversion exit, Tag picker UI and Send reporting.
What are the Drip API rate limits?: Drip documents 3,600 requests per hour. 3,600 requests/hour on standard endpoints; 50 requests/hour on batch endpoints (each batch carries up to 1000 records). Limits are set by Drip and can depend on your plan.