Integration

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.

Connect Drip How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

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

create_or_update_subscriberCreate or update subscriberPOSTCreates or updates a Drip subscriber.
delete_subscriberDelete subscriberDELETEDeletes a subscriber and all associated data.
fetch_subscriberFetch subscriberGETFetches a single subscriber by ID, email, or user_id.
list_subscribersList subscribersGETLists subscribers in a Drip account with filters.
unsubscribe_subscriberUnsubscribe subscriberPOSTGlobally unsubscribes a subscriber from all Drip mailings.

Tag, 3 operations

apply_tagApply tagPOSTApplies one or more tags to a subscriber.
list_tagsList tagsGETLists all tags configured in the Drip account.
remove_tagRemove tagDELETERemoves a tag from a subscriber.

Campaign, 2 operations

fetch_campaignFetch campaignGETFetches a single email-series campaign.
list_campaignsList campaignsGETLists email-series campaigns in a Drip account.

Campaign subscriber, 2 operations

remove_subscriber_from_campaignRemove subscriber from campaignPOSTRemoves a subscriber from one or all email-series campaigns.
subscribe_to_campaignSubscribe to campaignPOSTSubscribes a user to an email-series campaign.

Event, 2 operations

track_eventTrack eventPOSTRecords a behavioural event for a subscriber.
track_events_batchTrack events batchPOSTBatches up to 1000 event records in one call.

Workflow subscriber, 2 operations

remove_subscriber_from_workflowRemove subscriber from workflowDELETERemoves a subscriber from a workflow.
start_subscriber_in_workflowStart subscriber in workflowPOSTStarts a subscriber in a Drip workflow.

Account, 1 operation

list_accountsList accountsGETLists Drip accounts the authenticated user can access.

Broadcast, 1 operation

list_broadcastsList broadcastsGETLists broadcasts (one-off emails) in the account.

Custom field, 1 operation

list_custom_fieldsList custom fieldsGETLists all custom-field identifiers configured in the account.

Workflow, 1 operation

list_workflowsList workflowsGETLists 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.