Skip to content
For LLMsView as Markdown·

Drip ​

undefined

DetailValue
CategoryMarketing
Base URLhttps://api.getdrip.com/v2/{account_id}
AuthenticationBearer Token
Endpoints6
Connector keydrip

Using Drip in a workflow ​

  1. Go to Connections and click New Connection.
  2. Pick Drip from the marketplace.
  3. Enter your credentials (see Authentication above for what's expected).
  4. In a workflow, drop an API Call node and select this connection.
  5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints ​

EndpointSummary
GET Subscribers
GET Events
GET Campaigns
GET Workflows
GET Tags
GET Orders

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET ​

Subscribers

DetailValue
Operation IDsubscribers_0
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Drip connection from the Connection dropdown.
  3. In the Operation dropdown, select subscribers_0.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Drip API reference.

GET ​

Events

DetailValue
Operation IDevents_1
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Drip connection from the Connection dropdown.
  3. In the Operation dropdown, select events_1.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Drip API reference.

GET ​

Campaigns

DetailValue
Operation IDcampaigns_2
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Drip connection from the Connection dropdown.
  3. In the Operation dropdown, select campaigns_2.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Drip API reference.

GET ​

Workflows

DetailValue
Operation IDworkflows_3
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Drip connection from the Connection dropdown.
  3. In the Operation dropdown, select workflows_3.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Drip API reference.

GET ​

Tags

DetailValue
Operation IDtags_4
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Drip connection from the Connection dropdown.
  3. In the Operation dropdown, select tags_4.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Drip API reference.

GET ​

Orders

DetailValue
Operation IDorders_5
MethodGET
Path``

Parameters ​

No parameters.

Using this endpoint in a workflow ​

  1. Add an API Call node to your workflow.
  2. Pick your Drip connection from the Connection dropdown.
  3. In the Operation dropdown, select orders_5.
  4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns ​

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Drip API reference.