How to Integrate Retool with Drip

Before setting up Retool, you need two pieces of information from Drip: your API token and your account ID. Log into your Drip account at drip.com. Navigate to the top-right menu and click on your email address or avatar, then select 'User Settings'. In the settings page, find the 'API Token' section. Your API token is displayed here — if you have not generated one yet, click 'Generate' or 'Create Token'. Copy the token and store it temporarily in a secure location, such as a password manager. Do not share this token or commit it to version control, as it provides full access to your Drip account. Next, locate your Drip account ID. You can find this in the URL when browsing your Drip account — it appears as a numeric string in the path such as drip.com/account/1234567/dashboard. Alternatively, find it in your account settings under the API documentation link, which typically includes example URLs with your account ID pre-filled. Write down both the API token and the account ID — you will need both when configuring queries in Retool. The account ID is required in the path for most Drip API endpoints, which follow the pattern /v2/{account_id}/subscribers.

In Retool, open your organization homepage and navigate to the Resources tab in the left sidebar. Click '+ Create new' or '+ Add resource', scroll through the connector list, and select 'REST API'. On the configuration screen, fill in the Name field with 'Drip API' or a similarly descriptive label. In the Base URL field, enter https://api.getdrip.com — this is Drip's API base domain. For Authentication, select 'Bearer token' from the dropdown and paste your Drip API token into the token field. Next, add a default header to ensure the API receives JSON responses: click 'Add header', enter the key as Accept and the value as application/json. Add a second header with key Content-Type and value application/json, which is required for POST and PATCH requests. You do not need to add the account ID to the base URL — you will include it in individual query paths. Click 'Save resource'. Retool saves the configuration and the resource is now available to all apps and workflows in your organization. Because Retool proxies all requests server-side, your Bearer token is never transmitted to end user browsers, and you will not encounter CORS errors when calling Drip's API. If you manage multiple Drip accounts (for example, different brands or client accounts), create a separate REST API resource for each with the corresponding API token.

Open your Retool app or create a new one from the Apps tab. In the Code panel at the bottom, click '+ New query' and select your Drip API resource. Create your first query to list subscribers: set Method to GET and enter the URL path as /v2/{{ retoolContext.configVars.DRIP_ACCOUNT_ID }}/subscribers. Add URL parameters to control the response — set status to active (or unsubscribed or bounced depending on what you want to display), per_page to 100 to get the maximum results per page, and page to {{ subscribersTable.paginationOffset / 100 + 1 || 1 }} if you plan to implement pagination. Name this query getSubscribers. Create a second query to list all automation workflows: Method GET, URL path /v2/{{ retoolContext.configVars.DRIP_ACCOUNT_ID }}/workflows. Name this query getWorkflows. Create a third query to get workflow stats for a selected workflow: Method GET, URL path /v2/{{ retoolContext.configVars.DRIP_ACCOUNT_ID }}/workflows/{{ workflowsTable.selectedRow.id }}/workflow_steps — or refer to Drip's API docs for the specific stats endpoint. Run each query by clicking Run to verify the response structure before building transformers. Drip returns all responses as JSON objects with a top-level key matching the resource name (subscribers, workflows, etc.) that contains the data array.

1{
2  "method": "GET",
3  "path": "/v2/YOUR_ACCOUNT_ID/subscribers",
4  "params": {
5    "status": "active",
6    "per_page": "100",
7    "page": "{{ Math.floor(subscribersTable.paginationOffset / 100) + 1 || 1 }}"
8  }
9}

Drip's API wraps response data in a top-level key matching the resource type, and each subscriber or workflow object contains nested arrays and objects that need flattening before binding to Retool Table components. In the query editor for getSubscribers, click the 'Advanced' tab and toggle on 'Transform results'. Write a transformer that extracts the subscribers array and maps each subscriber to a flat object. Key fields to surface include id, email, status, tags (join the array to a comma-separated string), created_at, lifetime_value, and any custom fields your team tracks. Similarly, add a transformer on getWorkflows to flatten workflow objects with name, status, email_count, and created_at. After writing transformers, drag a Table component onto the canvas. Set its Data source to {{ getSubscribers.data }}. Configure columns — rename headers as needed, set the status column type to Tag for colored badges, and enable row selection. Drag a second Table for workflows and bind it to {{ getWorkflows.data }}. Add a Bar Chart component below the workflows table and configure its series to use workflow name as x-axis and a numeric metric (email count, conversion count) as the y-axis. Wire the workflows table row selection to trigger a getWorkflowStats query, and bind the chart to that query's transformed data.

1// Transformer: flatten Drip subscriber response
2const subscribers = data.subscribers || [];
3return subscribers.map(sub => ({
4  id: sub.id,
5  email: sub.email,
6  status: sub.status,
7  tags: (sub.tags || []).join(', '),
8  created: new Date(sub.created_at).toLocaleDateString(),
9  lifetime_value: sub.lifetime_value ? `$${(sub.lifetime_value / 100).toFixed(2)}` : '$0.00',
10  last_opened: sub.last_opened_email_at
11    ? new Date(sub.last_opened_email_at).toLocaleDateString()
12    : 'Never',
13  custom_fields: JSON.stringify(sub.custom_fields || {})
14}));

For a complete operations panel, marketing teams need the ability to apply tags, update custom fields, and manage subscriber status directly from Retool. Create write queries to support these operations. First, create a tag-subscriber query: Method POST, URL path /v2/{{ retoolContext.configVars.DRIP_ACCOUNT_ID }}/tags, Body type JSON with body { "tags": [{ "email": "{{ subscribersTable.selectedRow.email }}", "tag": "{{ tagInput.value }}" }] }. Create an unsubscribe query: Method POST, URL path /v2/{{ retoolContext.configVars.DRIP_ACCOUNT_ID }}/unsubscribes, body { "unsubscribes": [{ "email": "{{ subscribersTable.selectedRow.email }}" }] }. For bulk operations on multiple selected rows, use a JavaScript query that loops through the table's selectedRows array and calls the tag API for each selected subscriber. Add a Form component to the canvas with a TextInput for the tag name and two Buttons: 'Apply Tag' and 'Unsubscribe'. Wire 'Apply Tag' to trigger the tag query, and on the query's Success event handler, trigger getSubscribers to refresh the table and show a 'Tag applied' notification. For complex multi-workflow orchestration and bulk subscriber management across Drip and connected e-commerce platforms, RapidDev's team can help architect and build your complete Retool solution.

1// JavaScript query: bulk tag multiple selected subscribers
2const selectedRows = subscribersTable.selectedRows;
3const tagToApply = tagInput.value;
4
5if (!tagToApply) throw new Error('Please enter a tag name');
6if (selectedRows.length === 0) throw new Error('Please select at least one subscriber');
7
8const payload = {
9  tags: selectedRows.map(row => ({
10    email: row.email,
11    tag: tagToApply
12  }))
13};
14
15return await drip_api.trigger({
16  method: 'POST',
17  path: `/v2/${retoolContext.configVars.DRIP_ACCOUNT_ID}/tags`,
18  body: payload
19});