Skip to main content

Drip Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to a Drip location.
drip_api.png

Drip

Create a Drip Destination​

  1. Click the + icon on the Nexset that will be sent to the Drip destination, and select the Send to Destination option from the menu.

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

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

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

Configure Using a Template​

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

  • To configure this destination using a template, 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.

    For a complete list of subscriber fields accepted by this endpoint, see the Drip Subscribers API documentation.

    Create or update a batch of subscribers

    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.

    For details on supported subscriber fields and payload structure, see the Drip Batch Subscribers API documentation.

    Delete a subscriber

    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.

    For additional information on workflow enrollment and supported request fields, see the Drip Workflows API documentation.

    Apply a tag to a subscriber

    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.

    For the request body structure required to apply a tag, see the Drip Tags API documentation.

    Remove a tag from a 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.

    For the complete request body structure and supported event fields, see the Drip Events API documentation.

    Record a batch of events

    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.

    For additional details on the batch events payload format, see the Drip Batch Events API documentation.

    Unsubscribe a batch of subscribers

    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.

    For additional payload details, see the Drip Batch Unsubscribe API documentation.

    Create or update a batch of carts

    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.
      • items — An array of cart line item objects.

    For the complete cart payload schema and supported fields, see the Drip Shopper Activity — Cart API documentation.

    Create or update a batch of orders

    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).
      • order_id — A unique identifier for the order.
      • grand_total — The total order value.
      • items — An array of order line item objects.

    For the complete order payload schema and supported action types, see the Drip Shopper Activity — Order API documentation.

    Create or update a batch of orders (Legacy)

    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.

    For payload structure details, see the Drip v2 Orders Batch Create API documentation.

    Create or update a batch of products

    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:

      • action — The product action type (e.g., viewed).
      • email — The shopper's email address.
      • product_id — A unique identifier for the product.
      • name — The product name.
      • price — The product price.

    For the complete product payload schema, see the Drip Shopper Activity — Product API documentation.

    Create a webhook

    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.

    For the webhook request body schema and the list of supported Drip event types, see the Drip Webhooks API documentation.

    Delete a webhook

    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.

Configure Manually​

Drip destinations can be manually configured to send data to any valid Drip API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Drip API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, 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. Drip endpoints use:

    • POST: For creating subscribers, recording events, applying tags, enrolling in campaigns and workflows, and creating webhooks.
    • DELETE: For deleting subscribers, removing tags, and deleting webhooks.
    • GET: Not typically used for destination operations.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Drip API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call.

The Drip API exclusively accepts JSON. Select JSON as the content format for all Drip destination endpoints. Drip requires all API requests to use HTTPS and include a Content-Type: application/json header, which Nexla applies automatically.

API Endpoint URL​

  1. Enter the URL of the Drip API endpoint to which you want to send the Nexset data in the URL field. All Drip REST API v2 endpoint URLs begin with https://api.getdrip.com/v2/ and most are account-scoped, following the pattern https://api.getdrip.com/v2/{'{account_id}'}/resource. For delete operations, include the resource ID at the end of the URL.

The Drip v3 Shopper Activity endpoints use the pattern https://api.getdrip.com/v3/{'{account_id}'}/shopper_activity/resource/batch. Refer to the Drip API Reference for the complete URL structure of each endpoint.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include any headers already present in the credentials. The Authorization header (HTTP Basic Auth with your Drip API token) and Content-Type header are handled automatically by Nexla.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Drip destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

Batch mode is recommended for high-volume Drip operations such as subscriber imports, event imports, and shopper activity syncs. The Drip batch endpoints (e.g., batch subscribers, batch events, batch carts, batch orders) are designed to accept arrays of records and are significantly more efficient than single-record endpoints for bulk data operations.

  1. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings—click on an algorithm listed below to view instructions for configuring these settings.

Property Inside JSON Object

  1. Enter the name of the JSON property that should contain the batched records in the Property Name field.
  2. If any additional properties should be included in the request, enter the properties in the Other Props field in JSON format.

Code

  1. Enter the code that will be used to create the batched request in the code editor below the Grouping Algorithm field.

Response Webhook​

Optional

Nexla can automatically send the response received from the Drip API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Drip API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Drip API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Drip API using the current settings.

Save & Activate the Destination​

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