Appearance
Drip
undefined
| Detail | Value |
|---|---|
| Category | Marketing |
| Base URL | https://api.getdrip.com/v2/{account_id} |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | drip |
Using Drip in a workflow
- Go to Connections and click New Connection.
- Pick Drip from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
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
| Detail | Value |
|---|---|
| Operation ID | subscribers_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Drip connection from the Connection dropdown.
- In the Operation dropdown, select
subscribers_0. - 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
| Detail | Value |
|---|---|
| Operation ID | events_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Drip connection from the Connection dropdown.
- In the Operation dropdown, select
events_1. - 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
| Detail | Value |
|---|---|
| Operation ID | campaigns_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Drip connection from the Connection dropdown.
- In the Operation dropdown, select
campaigns_2. - 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
| Detail | Value |
|---|---|
| Operation ID | workflows_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Drip connection from the Connection dropdown.
- In the Operation dropdown, select
workflows_3. - 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
| Detail | Value |
|---|---|
| Operation ID | tags_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Drip connection from the Connection dropdown.
- In the Operation dropdown, select
tags_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
| Detail | Value |
|---|---|
| Operation ID | orders_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Drip connection from the Connection dropdown.
- In the Operation dropdown, select
orders_5. - 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.