Drip Data Source

The Drip connector enables you to ingest subscriber profiles, campaign data, broadcast records, workflow configurations, tags, events, and account metadata from your Drip account into Nexla. Follow the instructions below to create a new data flow that ingests data from a Drip source in Nexla.

Drip

Create a New Data Flow

1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

2. Select the Drip connector tile from the list of available 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.

3. In Nexla, Drip data sources can be created using pre-built endpoint templates, which expedite source setup for common Drip API endpoints. Each template is designed specifically for the corresponding Drip endpoint, making source configuration easy and efficient.
   • To configure this source using a template, follow the instructions in Configure Using a Template.

   Drip sources can also be configured manually, allowing you to ingest data from Drip endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
   • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Drip endpoints. Each template is designed specifically for the corresponding Drip API endpoint, making data source setup easy and efficient.

Endpoint Settings

• 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.

For a complete reference on broadcast fields returned by this endpoint, see the Drip API documentation for Fetch a Single Email Campaign.

Get User

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.

Additional information on Drip webhooks is available in the Drip Webhooks API documentation.

List Workflows

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.

Endpoint Testing

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

• To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

• If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually

Drip data sources can be manually configured to ingest data from any valid Drip API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Drip sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom request parameters.

API Method

1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

2. Select the API method that will be used for calls to the Drip API from the Method pulldown menu. The most common methods are:

   • GET: For retrieving data from the Drip API (used by all Drip read endpoints)
   • POST: For sending data to the API or triggering actions

API Endpoint URL

3. Enter the URL of the Drip API endpoint from which this source will fetch data in the Set API URL field. All Drip REST API v2 and v3 endpoint URLs begin with https://api.getdrip.com/. This should be the complete URL including the protocol and any required path parameters.

Drip API endpoints are account-scoped. Most endpoints require your account ID in the URL path, following the pattern https://api.getdrip.com/v2/{'{account_id}'}/resource. The account ID is the numeric value configured in your credential and found in the URL of your Drip dashboard. Reference the Drip API Reference for full endpoint documentation.

Date/Time Macros (API URL)

Optional

Optionally, the API URL can be customized using macros—all macros added to the API URL will be converted into values when Nexla executes the API call. Macros are dynamic placeholders that allow you to create flexible API endpoints that can adapt to different time periods or data requirements.

Macros are particularly useful when querying Drip endpoints that support date-based filtering parameters, such as filtering subscribers or events by a date range.

1. To add a macro, type { at the appropriate position in the API URL (within the Set API URL field), and select the desired macro from the dropdown list.

   • {now} – The current datetime
   • {now-1} – The datetime one time unit before the current datetime
   • {now+1} – The datetime one time unit after the current datetime
   • custom – Datetime macros can reference any number of time units before or after the current datetime—for example, enter (now-4) to indicate the datetime four time units before the current datetime

2. Select the format that will be applied to datetime macros from the Date Format for Date/Time Macro pulldown menu. This format will be applied to the base datetime value of the macro—i.e., the value of {now} in {now-1}.

3. Select the datetime unit that will be used to perform mathematical operations in the included macro(s) from the Time Unit for Operations pulldown menu—for example, for the macro {now-1}, when Day is selected, {now-1} will be converted to the datetime one day before the current datetime.

Lookup-Based Macros (API URL)

Optional

Column values from existing lookups can also be included as macros in the API URL. Lookup-based macros allow you to reference data from previously configured data sources or lookups, enabling dynamic API endpoints that can adapt based on existing data.

Lookup-based macros are useful when you need to create Drip API endpoints that reference specific subscriber IDs, campaign IDs, or other parameters sourced from other Nexla data sources in your environment.

1. To include a lookup column value macro, select the relevant lookup from the Add Lookups to Supported Macros pulldown menu.

2. Type { at the appropriate position in the API URL, and select the lookup column-based macro from the dropdown list. Lookup-based macros are automatically populated into the macro list when a lookup is selected in the Add Lookups to Supported Macros pulldown menu.

Path to Data

Optional

If only a subset of the data returned by the Drip API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response. This is particularly useful when Drip API responses contain metadata, pagination information, or wrapper objects that you don't need for your analysis.

For example, most Drip list endpoints return an array of records wrapped inside a named property (e.g., $.subscribers[*], $.campaigns[*], $.workflows[*]). By entering the path to the relevant array, you can configure Nexla to treat each element of the returned array as a record.

Path to Data is essential when working with Drip API responses, as Drip wraps all response arrays inside named properties. Without specifying the correct JSON path, Nexla will treat the entire response object as a single record rather than individual items.

• To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

  • For responses in JSON format enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $.subscribers[*] to access an array of subscriber objects within the response).
  Path to Data Example:

  For the Drip subscribers endpoint, the API response wraps subscriber records inside a subscribers property. To extract each subscriber as an individual record, enter $.subscribers[*] as the path to data. Use the same pattern for other Drip resources: $.campaigns[*], $.workflows[*], $.broadcasts[*], etc.

Autogenerate Path Suggestions

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

• To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

• Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

  

Metadata

If metadata is included in the Drip API response but is located outside of the defined path to relevant data, you can configure Nexla to include this data as common metadata in each record. This is useful when you want to preserve important contextual information that applies to all records, such as pagination state or request timestamps, alongside the main data.

Metadata paths are particularly useful for preserving Drip API response context like total counts, pagination links, or account-level summary statistics that apply to all records in the response.

• To specify the location of metadata that should be included with each record, enter the path to the relevant metadata in the Path to Metadata in Response field.

  • For responses in JSON format, enter the JSON path to the object or array that contains the metadata.

Request Headers

Optional

• If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2). Additional headers may be required for API versioning or custom request requirements.

  You do not need to include any headers already present in the credentials. The Authorization header (HTTP Basic Auth with your API token) is handled automatically by Nexla based on your Drip credential configuration. Drip requires all API calls to use HTTPS and communicate exclusively in JSON.

Endpoint Testing

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

• To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

• If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source

1. Once all of the relevant steps in the above sections have been completed, 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.