Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Drip

E-commerce CRM for B2B marketers

CategoryMarketing
Authenticationcustom
Version0.5.0
Published scopes0 published scopes
Last updatedSeptember 29, 2026

Overview

Connect Drip with Flows360

E-commerce CRM for B2B marketers

Use the Drip connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 4 actions and 2 triggers.

Available actions

  • Apply a tag to subscriber
  • Add a subscriber to a campaign
  • Create or Update Subscriber
  • Custom API Call

Available triggers

  • New Subscriber
  • Tag Applied

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Drip
  • Package: @activepieces/piece-drip@0.5.0
  • Exact artifact digest: sha256:4b2276f83c8c47847422a22f4aaccd9b9e41052fb8796f785282341d347b2ae5
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

SECRET TEXT. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Apply a tag to subscriber (apply_tag_to_subscriber), Apply a tag to a subscriber Classification: read.
  • Add a subscriber to a campaign (add_subscriber_to_campaign), Add a subscriber to a campaign (Email series) Classification: read.
  • Create or Update Subscriber (upsert_subscriber), Create or Update Subscriber Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Subscriber, webhook.
  • Tag Applied, webhook.

Verification

Runtime execution evidence is managed separately from package metadata.

Capability summary

Authenticationcustom
Supported objects6
Supported actions4
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • API Key Required · protected credential

Supported objects

ObjectReadWriteNotes
Apply a tag to subscriber Yes No Apply a tag to a subscriber
Add a subscriber to a campaign Yes No Add a subscriber to a campaign (Email series)
Create or Update Subscriber Yes No Create or Update Subscriber
Custom API Call Yes No Make a custom API call to a specific endpoint
New Subscriber Yes No webhook trigger declared by the pinned package.
Tag Applied Yes No webhook trigger declared by the pinned package.

Supported actions

Apply a tag to subscriber · Read

Apply a tag to a subscriber

apply_tag_to_subscriber · Risk: low · Retry: safe

Inputs

  • account_id · string · Required
  • subscriber · string · Required, Email of the subscriber
  • tag · string · Required, Tag to apply
Add a subscriber to a campaign · Read

Add a subscriber to a campaign (Email series)

add_subscriber_to_campaign · Risk: low · Retry: safe

Inputs

  • account_id · string · Required
  • campaign_id · string · Required
  • subscriber · string · Required, Email of the subscriber
  • tags · array · Optional, Tags to apply to subscriber
  • custom_fields · object · Optional, Custom field data about the subscriber
Create or Update Subscriber · Read

Create or Update Subscriber

upsert_subscriber · Risk: low · Retry: safe

Inputs

  • account_id · string · Required
  • subscriber · string · Required, Email of the subscriber
  • tags · array · Optional, Tags to apply to subscriber
  • custom_fields · object · Optional, Custom field data about the subscriber
  • first_name · string · Optional
  • last_name · string · Optional
  • zip · string · Optional, Postal code in which the subscriber resides
  • country · string · Optional, The country in which the subscriber resides
  • state · string · Optional, The region in which the subscriber resides
  • city · string · Optional, The city in which the subscriber resides
  • phone · string · Optional, The subscriber's primary phone number
  • address · string · Optional, The subscriber's mailing address
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New Subscriber · Webhook

Triggers when a subscriber is created in your Drip account.

Inputs

  • account_id · string
Tag Applied · Webhook

Triggers when a tag is applied.

Inputs

  • account_id · string

Setup

Setup

  1. Add the Drip connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-drip@0.5.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 4 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Runtime execution evidence is managed separately from package metadata.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Drip connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-drip@0.5.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com