Drip is an ecommerce CRM and marketing automation platform built for B2C online retailers. It manages subscriber lists, targeted email campaigns, multi-step automations, and shopper activity (cart events, orders, product interactions), with native Shopify, WooCommerce, and BigCommerce integrations. Its REST API exposes subscribers, campaigns, broadcasts, workflows, events, tags, and webhooks.
Power end-to-end data operations for your Drip API with Nexla. Our bi-directional Drip connector is purpose-built for Drip, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Drip or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Drip workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
Drip authenticates API requests using HTTP Basic Authentication with your personal API token as the username and an empty string as the password. Before creating a credential in Nexla, you will need your Drip API token and your numeric Drip account ID.
Your API token is a personal credential tied to your Drip user account. It grants access to all Drip accounts associated with your user and is required for every API request.
Click your avatar or account name in the upper-right corner of the dashboard to open the user menu.
Select User Settings from the dropdown.
On the User Info tab, locate the API Token section.
If a token has already been generated, it is displayed here. To create a new token, click Generate a New API Token.
Important
Generating a new API token immediately invalidates the previous token. Any existing integrations using the old token will stop authenticating until they are updated with the new token.
Copy the API token and store it securely. This token serves as the HTTP Basic Auth username in every request Nexla sends to the Drip API.
Your API token is personal and should be treated like a password. Do not share it publicly or commit it to source control. For additional details, see the Drip Help Center article on API Tokens.
The account ID is a numeric identifier for a specific Drip account. It is required by all account-scoped API endpoints, including subscribers, campaigns, broadcasts, workflows, tags, events, and shopper activity.
Examine the URL in your browser's address bar. After logging in it will follow the format https://www.drip.com/XXXXXXXX/dashboard where XXXXXXXX is your numeric account ID.
Copy this numeric value. You will enter it in the Account ID field when configuring the Nexla credential.
If your Drip user has access to multiple Drip accounts, each account has its own unique account ID. Verify that the account ID you copy belongs to the specific Drip account whose data you intend to integrate with Nexla.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Drip uses HTTP Basic Authentication for all API requests. The API token is provided as the username, and the password is left blank. This is the authentication method required by the Drip API for private integrations.
Enter your Drip API token in the API Token field. This is the token retrieved from User Settings > User Info in your Drip account. Nexla transmits this value as the HTTP Basic Auth username in all requests made to the Drip API.
Leave the Password (leave blank) field empty. Drip's authentication scheme requires only the API token as the username—no password value is needed. The field exists for compatibility with the standard HTTP Basic Authentication format.
Enter your numeric Drip account ID in the Account ID field. This value is referenced by all account-scoped Drip API endpoints. As described in the Prerequisites section, the account ID can be found in the URL of your Drip dashboard.
The Account ID is a shared global setting for this credential. It is used automatically in all data sources and destinations created with this credential. Ensure it corresponds to the Drip account whose data you want to access through Nexla.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Drip connector tile, then select the credential that will be used to connect to the Drip account, and click Next; or, create a new Drip credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Drip endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.
Fetch an Account
Retrieves the full details of a specific Drip account by account ID, including account name, configuration, and billing information. Use this endpoint to confirm account connectivity or retrieve account-level metadata for reporting purposes.
No additional parameters are required for this endpoint. The account ID configured in your Drip credential is used automatically to identify which account to retrieve.
The response is extracted from $.accounts[0], returning a single account object with all available account attributes.
This endpoint is useful for validating that your credential is correctly configured and that Nexla has access to the expected Drip account before building more complex data flows.
Fetch a Single Email Campaign
Retrieves the details of a single email campaign (broadcast) by its unique ID for the specified account. Use this endpoint when you need to pull metadata and configuration for a specific broadcast, such as its status, subject, scheduled send time, and associated statistics.
Enter the unique identifier of the broadcast to retrieve in the Broadcast ID field. To find a broadcast ID:
Log in to your Drip account and navigate to Campaigns > Broadcasts.
Open the desired broadcast. The broadcast ID appears in the URL as a numeric segment (e.g., https://www.drip.com/ACCOUNT_ID/broadcasts/BROADCAST_ID).
Alternatively, use the List Broadcasts template first to retrieve a list of all broadcasts and their IDs.
The Broadcast ID field is optional. If left blank, the endpoint may return an empty or error response, so providing a valid broadcast ID is recommended.
Returns details about the authenticated Drip user associated with the API token in the credential, including name, email, time zone, and account access information. Use this endpoint to verify which user identity is being used for API calls or to retrieve user profile data.
No additional parameters are required. This endpoint automatically uses the API token from your credential to identify and return the authenticated user.
The response is extracted from $.user, returning a single user object.
List Accounts
Returns a list of all Drip accounts associated with the authenticated user. Use this endpoint when your Drip user has access to multiple accounts and you need to enumerate them, or to retrieve account IDs for use in other endpoints.
No additional parameters are required. The response is extracted from $.accounts[*], returning an array where each element represents a distinct Drip account.
Each account record includes the account ID, name, and associated configuration. The account ID values returned here can be used to configure account-scoped data sources.
List Broadcasts
Returns a list of all email campaigns (broadcasts) in the account. Broadcasts in Drip are one-time email sends to a segment or your full list—distinct from multi-email series campaigns. Use this endpoint to inventory your broadcast history, track send status, or feed broadcast metadata into downstream reporting systems.
No additional parameters are required. The response is extracted from $.broadcasts[*], returning an array of broadcast objects, each containing fields such as name, status, subject, scheduled send time, and performance metrics.
To retrieve a single broadcast by ID, use the Fetch a Single Email Campaign template instead.
List All Single-Email Campaigns
Returns a paginated list of single-email campaigns (broadcasts) in the account with optional filtering by status and configurable sorting. This template supports pagination and is suited for accounts with large numbers of broadcasts. Use this endpoint when you need to pull a filtered or sorted subset of broadcasts for analysis or integration.
Optionally, enter a value in the Status field to filter broadcasts by their current status. Supported values include:
draft — Broadcasts that have been created but not yet scheduled or sent.
scheduled — Broadcasts that are scheduled for future delivery.
sent — Broadcasts that have been delivered.
Optionally, enter a field name in the Sort by field to control the sort order of results. Common values include created_at and updated_at.
Optionally, enter a value in the Sort direction field to control the sort order direction. Use asc for ascending or desc for descending order.
This template uses paginated fetching with a page size of 100 records per page and will automatically fetch additional pages until all matching records are retrieved.
The response data is extracted from $.broadcasts[*]. Leaving the Status, Sort by, and Sort direction fields blank will return all broadcasts in the account's default order. For additional filter and sort options, see the Drip Broadcasts API documentation.
List Campaigns
Returns a list of all email series campaigns in the account. Email series (also called drip campaigns) are multi-step automated email sequences triggered by subscriber actions or enrollment. Use this endpoint to retrieve campaign metadata, including names, statuses, and associated configuration.
No additional parameters are required. The response is extracted from $.campaigns[*], returning an array of campaign objects.
Each campaign record includes the campaign ID, name, status, and step count. The campaign IDs returned here can be used with the List subscribers in a campaign endpoint to retrieve subscriber enrollment data.
List subscribers in a campaign
Returns a list of all subscribers currently enrolled in a specific email series campaign. Use this endpoint to audit campaign enrollment, analyze subscriber progress through a series, or sync campaign membership data with an external CRM or analytics platform.
Enter the unique identifier of the campaign in the Campaign Id field. This field is required. Campaign IDs can be obtained by using the List Campaigns template or by navigating to the campaign in your Drip account and reading the numeric ID from the URL.
The response is extracted from $.subscribers[*], returning an array of subscriber profile objects.
List Subscribers
Returns a list of all subscribers in the account. Subscriber records include email addresses, names, custom field values, tags, subscription status, and behavioral data. Use this endpoint to export your full contact list, sync subscriber profiles to a data warehouse, or analyze audience composition.
No additional parameters are required. The response is extracted from $.subscribers[*], returning an array where each element is a complete subscriber profile.
Drip accounts with large subscriber lists may return a significant volume of data. For large accounts, consider using Nexla's scheduling options to run this source incrementally. Additional details on subscriber fields are available in the Drip Subscribers API documentation.
Fetch a subscriber
Fetches a single subscriber's full profile by their Drip subscriber ID or email address. The response includes all profile fields, tags, custom field values, and subscription status. Use this endpoint when you need to retrieve a specific subscriber's complete record for lookup or synchronization purposes.
Enter the subscriber's Drip ID or email address in the Id Or Email field. This field is required. Either value can be used interchangeably to identify the subscriber.
The response is extracted from $.subscribers[0], returning a single subscriber object.
List Custom Fields
Returns a list of all custom field identifiers defined in the account. Custom fields in Drip store subscriber-specific data such as purchase history attributes, preferences, or demographics beyond the default profile fields. Use this endpoint to discover available custom fields before mapping subscriber data or designing automation workflows.
No additional parameters are required. The response is extracted from $.custom_field_identifiers[*], returning an array of custom field identifier strings.
List Event Actions
Returns a list of all event actions available in the account. Event actions are the named custom events that can be recorded for subscribers to trigger automations, segment audiences, or track behavioral signals. Use this endpoint to enumerate the events defined in your account before recording or analyzing event data.
No additional parameters are required. The response is extracted from $.event_actions[*], returning an array of event action objects.
List Goals
Returns a list of all goals (conversions) defined in the account. Goals in Drip track when subscribers complete a desired outcome, such as making a purchase or completing a form. Use this endpoint to retrieve goal definitions and track conversion performance across your marketing programs.
No additional parameters are required. The response is extracted from $.goals[*], returning an array of goal objects.
List Tags
Returns a list of all tags defined in the account. Tags in Drip are used to segment subscribers and trigger workflow automations based on behavior, lifecycle stage, or marketing activity. Use this endpoint to audit your tag taxonomy or to map Drip tags to fields in a connected system.
No additional parameters are required. The response is extracted from $.tags[*], returning an array of tag values.
List Webhooks
Returns a list of all webhooks configured in the Drip account. Webhooks allow Drip to push event notifications to an external URL when subscriber or account events occur. Use this endpoint to audit existing webhook subscriptions or to verify webhook configuration before making changes.
No additional parameters are required. The response is extracted from $.webhooks[*], returning an array of webhook configuration objects, each including the target URL and associated events.
Returns a list of all workflows in the account. Workflows in Drip are visual automation sequences composed of triggers, actions, and decision branches that run automatically based on subscriber behavior or data conditions. Use this endpoint to retrieve workflow metadata for auditing, reporting, or integration with external project management or analytics tools.
No additional parameters are required. The response is extracted from $.workflows[*], returning an array of workflow objects, each including the workflow ID, name, status, and associated triggers.
Workflow IDs returned by this endpoint can be used with destination endpoints such as Enroll a subscriber in a workflow when sending data back to Drip.
Fetch a workflow
Fetches the detailed configuration for a single workflow, including its triggers, step actions, and current status. Use this endpoint when you need to inspect a specific automation's logic, validate its configuration, or extract its step details for documentation or comparison purposes.
Enter the unique identifier of the workflow in the Workflow Id field. This field is required. Workflow IDs can be obtained using the List Workflows template or by navigating to the workflow in your Drip account and reading the ID from the URL.
The response is extracted from $.workflows[0], returning a single workflow object with full configuration details.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Drip data sources can also be manually configured to ingest data from any valid Drip API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
All Drip REST API v2 and v3 endpoint URLs begin with https://api.getdrip.com/, and most are account-scoped, following the pattern https://api.getdrip.com/v2/{'{account_id}'}/resource. Drip wraps all list responses inside a named property, so set Path to Data accordingly—for example, $.subscribers[*], $.campaigns[*], or $.workflows[*]. The Authorization header (HTTP Basic Auth) is applied automatically; Drip requires all API calls to use HTTPS and communicate exclusively in JSON.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Drip data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Drip destination, and select the Send to Destination option from the menu. Select the Drip connector from the list of available destination connectors, then select the credential that will be used to connect to the Drip account, and click Next; or, create a new Drip credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Drip endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Create or update a subscriber
Creates a new subscriber or updates an existing one (upsert by email address). This is the core operation for syncing contact data into Drip from external CRM systems, form submissions, data warehouses, or other sources. If a subscriber with the provided email address already exists, their profile is updated; otherwise, a new subscriber record is created.
No additional template parameters are required. Each record in the Nexset is sent as a JSON body to the Drip subscribers endpoint. Ensure your Nexset includes at minimum an email field, as Drip uses the email address as the unique subscriber identifier for upsert operations.
Common Nexset fields that map to Drip subscriber properties include:
email — Required. The subscriber's email address.
first_name and last_name — The subscriber's name.
tags — An array of tag strings to apply to the subscriber.
custom_fields — A JSON object of key-value pairs for any custom field identifiers defined in the account.
Records are sent individually (not batched) by default. For high-volume contact syncs, consider using the Create or update a batch of subscribers template instead.
Batch creates or updates multiple subscribers in the account in a single API call. This template is the recommended approach for high-volume contact sync scenarios, such as importing contacts from a CRM migration, synchronizing a data warehouse subscriber list with Drip, or processing bulk form submissions.
No additional template parameters are required. Records are automatically grouped into batch payloads before being sent to the Drip batch subscribers endpoint.
Each record in the Nexset should include at minimum an email field. Drip uses the email address to determine whether to create a new subscriber or update an existing one.
This template operates in batch mode, grouping multiple records into a single API call for efficiency. Nexla handles batching automatically based on your record batching settings.
Permanently deletes a subscriber from the Drip account. This endpoint is typically used for GDPR or CCPA compliance erasure requests, removing a contact from Drip when a deletion request is received from a CRM or consent management platform. Deletion is irreversible and removes all of the subscriber's data from the account.
Enter the subscriber's Drip ID or email address in the Id Or Email field. This field is required. Either the numeric Drip subscriber ID or the subscriber's email address can be used to identify the subscriber to delete.
:::warning Important
Deleting a subscriber permanently removes all of their data from Drip, including their profile, tags, custom field values, and engagement history. This action cannot be undone.
:::
Subscribe to an email series campaign
Subscribes a person to a specific email series campaign (drip sequence). Use this endpoint to enroll subscribers into a nurture sequence, onboarding series, or other automated multi-email campaign based on data from an external source such as a CRM, e-commerce platform, or event trigger system.
Enter the unique identifier of the email series campaign in the Campaign Id field. This field is required. Campaign IDs can be found by navigating to the campaign in your Drip account and reading the numeric ID from the URL, or by using the Drip List Campaigns data source template.
Each record in the Nexset should include the subscriber's email address and any additional fields required to create or update the subscriber profile at enrollment time.
For the complete list of fields supported in the request body for campaign subscription, see the Drip Campaigns API documentation.
Enroll a subscriber in a workflow
Enrolls a subscriber into a specific Drip workflow to trigger an automation sequence. Use this endpoint to start subscribers on a workflow based on external signals—such as a purchase event from an ecommerce platform, a stage change in a CRM, or any behavioral trigger captured in a data warehouse.
Enter the unique identifier of the workflow in the Workflow Id field. This field is required. Workflow IDs can be found by navigating to the workflow in your Drip account and reading the ID from the URL, or by using the Drip List Workflows data source template.
Each record in the Nexset should include the subscriber's email address. Additional subscriber fields can also be included to create or update the subscriber profile at enrollment time.
Applies a tag to a subscriber in Drip. Tags are used in Drip for audience segmentation and as triggers for workflow automations. Use this endpoint to tag subscribers based on external events or data conditions—such as tagging a customer as a high-value buyer after a purchase threshold is reached in an ecommerce platform.
No additional template parameters are required. Each record in the Nexset should include the subscriber's email address and the name of the tag to apply, structured as required by the Drip tags endpoint JSON body format.
If the specified tag does not already exist in the account, Drip will create it automatically when applied to the first subscriber.
Removes a tag from a subscriber, reversing a segmentation label or lifecycle state change. Use this endpoint when external data signals indicate a subscriber should exit a tagged segment—such as removing a "cart-abandoner" tag after a purchase is confirmed in an ecommerce system.
Enter the subscriber's Drip ID or email address in the Id Or Email field. This field is required.
Enter the exact name of the tag to remove in the Tag field. This field is required. The tag name must match exactly (case-sensitive) as it exists in the Drip account.
Record a single event
Records a single custom event for a subscriber in real time. Events in Drip can trigger workflow automations, update subscriber scores, and be used for segmentation. Use this endpoint for real-time, low-latency event tracking scenarios—such as recording a page view, product interaction, or support ticket creation from an external system.
No additional template parameters are required. Each record in the Nexset should include the subscriber's email address, the event action name, and any optional event properties, structured as required by the Drip events endpoint JSON body format.
For high-volume event recording, consider using the Record a batch of events template to send multiple events in a single API call.
Batch records multiple custom events for subscribers in the account in a single API call. Use this template for high-volume event tracking scenarios such as importing historical event data, processing bulk behavioral signals from an analytics platform, or syncing event logs from an ecommerce system.
No additional template parameters are required. Records are automatically grouped into batch payloads before being sent to the Drip batch events endpoint.
Each record in the Nexset should include at minimum the subscriber's email address and the event action name. Optional event properties can also be included.
Batch unsubscribes multiple subscribers from the account in a single API call. Use this endpoint to process bulk opt-out lists, synchronize unsubscribe events from an external email suppression list, or enforce global unsubscribes received through a consent management platform.
No additional template parameters are required. Records are automatically grouped into batch payloads. Each record in the Nexset should include the subscriber's email address to identify the subscriber to unsubscribe.
Unsubscribed subscribers are marked as unsubscribed in Drip and will no longer receive email communications from the account. Their subscriber record and data are retained.
Batch creates or updates multiple shopping cart records in the account using Drip's Shopper Activity API (v3). Cart activity data enables Drip to trigger cart abandonment workflows, personalize email content, and update subscriber lifecycle stages based on shopping behavior. Use this endpoint to sync cart data from your ecommerce platform into Drip.
No additional template parameters are required. Records are automatically grouped into batch payloads and sent to the Drip shopper activity cart endpoint.
Each record in the Nexset should represent a single cart event and include relevant cart fields, such as:
email — The shopper's email address.
action — The cart action type (e.g., created, updated).
cart_id — A unique identifier for the cart.
cart_url — The URL of the cart page for use in abandonment emails.
Batch creates or updates multiple order records in the account using Drip's Shopper Activity API (v3). Order data enables Drip to trigger post-purchase workflows, segment customers by purchase behavior, calculate lifetime value, and personalize subsequent communications. Use this endpoint to sync order data from your ecommerce platform or order management system into Drip.
No additional template parameters are required. Records are automatically grouped into batch payloads and sent to the Drip shopper activity order endpoint.
Each record in the Nexset should represent a single order event and include relevant order fields, such as:
email — The shopper's email address.
action — The order action type (e.g., placed, updated, paid, refunded).
Batch creates or updates multiple order records using the legacy Drip v2 Orders API endpoint. This template is provided for compatibility with integrations originally built against the v2 API. For new integrations, use the Create or update a batch of orders template (v3 Shopper Activity API) instead.
No additional template parameters are required. Records are automatically grouped into batch payloads and sent to the Drip v2 batch orders endpoint.
Each record in the Nexset should be structured according to the Drip v2 Orders API schema.
Batch creates or updates multiple product records in the account using Drip's Shopper Activity API (v3). Product data enables Drip to enrich email content with product recommendations, personalize post-purchase sequences, and power product-based segmentation. Use this endpoint to sync your product catalog from an ecommerce platform or product information management (PIM) system into Drip.
No additional template parameters are required. Records are automatically grouped into batch payloads and sent to the Drip shopper activity product endpoint.
Each record in the Nexset should represent a single product event and include relevant product fields, such as:
Creates a new webhook subscription in the Drip account so that Drip pushes event notifications to a specified external endpoint when subscriber or account events occur. Use this endpoint to programmatically configure webhook subscriptions, such as when setting up new Nexla webhook data sources or provisioning integrations at scale.
No additional template parameters are required. Each record in the Nexset should include the webhook target URL and the events to subscribe to, structured according to the Drip webhooks endpoint JSON body format.
Removes an existing webhook subscription from the Drip account. Use this endpoint for clean teardown of webhook integrations, rotation of webhook URLs, or decommissioning of outdated notification subscriptions.
Enter the unique identifier of the webhook to delete in the Webhook Id field. This field is required. Webhook IDs can be obtained using the Drip List Webhooks data source template or from the Drip account settings.
Drip destinations can also be manually configured to send data to any valid Drip API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Drip REST API v2 endpoints use the base URL https://api.getdrip.com/v2/ and are mostly account-scoped, following the pattern https://api.getdrip.com/v2/{'{account_id}'}/resource; include the resource ID or email address at the end of the URL for delete operations. The v3 Shopper Activity batch endpoints (carts, orders, products) follow the pattern https://api.getdrip.com/v3/{'{account_id}'}/shopper_activity/resource/batch. The Drip API exclusively accepts JSON—select JSON as the Content Format for all Drip destination endpoints. The Authorization header (HTTP Basic Auth) and Content-Type: application/json header are applied automatically. Batch endpoints (e.g., batch subscribers, batch events, batch carts, batch orders) are recommended for high-volume operations; the default batch size is 100.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Drip endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Drip until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
