How to Integrate Retool with Pipedrive

Start by locating your Pipedrive personal API token. Log in to your Pipedrive account and navigate to Settings (your profile icon in the top right) → Personal preferences → API. Your personal API token is displayed on this page — copy it. Before creating the resource, store your API token securely in Retool. Go to your Retool instance's Settings tab (in the left sidebar) → Configuration Variables → Create Variable. Name it PIPEDRIVE_API_TOKEN and mark it as Secret. Paste your API token as the value and save. Now navigate to the Resources tab in Retool and click Add Resource. Select REST API from the resource type list. Name the resource 'Pipedrive API'. In the Base URL field, enter https://api.pipedrive.com. This is the base URL for Pipedrive's v1 API — you'll add /v1/ to each query path. Pipedrive authenticates via an API token passed as a query parameter named api_token. In the Default URL Parameters section, add: Key = api_token, Value = {{ retoolContext.configVars.PIPEDRIVE_API_TOKEN }}. Also add a default header: Key = Content-Type, Value = application/json. Click Save Changes. Test the resource by creating a quick query with path /v1/pipelines — you should receive a list of your Pipedrive pipelines.

Create the foundational queries for your pipeline dashboard. First, create getPipelines with Method GET and path /v1/pipelines to retrieve all pipelines with their IDs and names. Add a Dropdown component named dropdown_pipeline and bind its options to {{ getPipelines.data.data.map(p => ({ label: p.name, value: p.id })) }}. Create getStages with Method GET and path /v1/stages and URL parameter: Key = pipeline_id, Value = {{ dropdown_pipeline.value }}. This returns all stages in the selected pipeline with their IDs, names, and order positions. Create getDeals with Method GET and path /v1/deals. Add URL parameters: Key = pipeline_id, Value = {{ dropdown_pipeline.value }}, Key = stage_id, Value = {{ dropdown_stage.value || '' }}, Key = status, Value = open, Key = limit, Value = 100, Key = start, Value = {{ (pagination.pageNumber - 1) * 100 || 0 }}. The deals endpoint returns deal objects including the deal's stage ID, owner, value, expected close date, and activity counts. For each deal, Pipedrive also returns person_id and org_id references. To show person and organization names alongside deals, either fetch them separately or use the include_fields parameter to get basic contact information inline. Create a JavaScript transformer to flatten and enrich the deals response with calculated fields like days_in_stage and days_until_close.

1// JavaScript transformer — flatten Pipedrive deals for table display
2const deals = data?.data || [];
3const now = new Date();
4
5return deals.map(deal => {
6  const expectedClose = deal.expected_close_date
7    ? new Date(deal.expected_close_date)
8    : null;
9  const stageChanged = deal.stage_change_time
10    ? new Date(deal.stage_change_time)
11    : new Date(deal.add_time);
12  const daysInStage = Math.floor((now - stageChanged) / (1000 * 60 * 60 * 24));
13  const daysUntilClose = expectedClose
14    ? Math.floor((expectedClose - now) / (1000 * 60 * 60 * 24))
15    : null;
16
17  return {
18    id: deal.id,
19    title: deal.title,
20    stage: deal.stage_id,
21    stage_name: deal.stage_id ? `Stage ${deal.stage_id}` : 'Unknown',
22    owner: deal.owner_name || deal.user_id?.name || 'Unassigned',
23    value: deal.value
24      ? `$${deal.value.toLocaleString('en-US', { minimumFractionDigits: 0 })}`
25      : '$0',
26    currency: deal.currency,
27    person: deal.person_name || deal.person_id?.name || 'N/A',
28    organization: deal.org_name || deal.org_id?.name || 'N/A',
29    expected_close: deal.expected_close_date || 'Not set',
30    days_until_close: daysUntilClose !== null
31      ? (daysUntilClose < 0 ? `${Math.abs(daysUntilClose)}d overdue` : `${daysUntilClose}d`)
32      : 'No date',
33    days_in_stage: daysInStage,
34    activities_count: deal.activities_count || 0,
35    status: deal.status
36  };
37});

Add write operations to make your Pipedrive dashboard actionable, not just a read-only view. Create a query named updateDealStage with Method PATCH and path /v1/deals/{{ table_deals.selectedRow.id }}. Set the request body to JSON: { "stage_id": {{ dropdown_newStage.value }} }. Add a Dropdown component named dropdown_newStage with options bound to {{ getStages.data.data.map(s => ({ label: s.name, value: s.id })) }}. Add a Button named btnMoveStage with an event handler that triggers updateDealStage. On success, trigger getDeals to refresh the table and show a success notification. Create a query named addNote with Method POST and path /v1/notes. Set the JSON body to: { "content": "{{ textArea_note.value }}", "deal_id": {{ table_deals.selectedRow.id }} }. Add a Text Area component and a Save Note button to let users add notes to deals directly from the dashboard. Create addActivity with Method POST and path /v1/activities. Set the body: { "subject": "{{ textInput_activitySubject.value }}", "type": "{{ select_activityType.value }}", "due_date": "{{ datePicker_dueDate.value }}", "deal_id": {{ table_deals.selectedRow.id }}, "user_id": {{ select_assignee.value }} }. Add a modal (Modal component) that opens when a user clicks 'Log Activity', containing the activity form fields. Trigger addActivity on form submit, then close the modal and refresh the deals table on success.

1// PATCH body for moving a deal to a new stage
2// Used in updateDealStage query (JSON body)
3{
4  "stage_id": {{ dropdown_newStage.value }},
5  "status": "open"
6}

Create queries for pipeline performance reporting. Query Pipedrive's pipeline statistics endpoint: create getPipelineStats with Method GET and path /v1/pipelines/{{ dropdown_pipeline.value }}/deals/summary. This endpoint returns aggregate totals including total_count, total_value, and total_count_by_stage. Create getDealsTimeline with Method GET and path /v1/deals/timeline. Add URL parameters: Key = start_date, Value = {{ dateRange.start.toISOString().split('T')[0] }}, Key = interval, Value = month, Key = amount, Value = 6, Key = field_key, Value = close_time, Key = pipeline_id, Value = {{ dropdown_pipeline.value }}. This returns a monthly breakdown of deals closed over the past 6 months — perfect for a Chart component. Add Stat components to your dashboard header showing total pipeline value (sum of all open deal values), average deal size, and win rate calculated from Pipedrive's statistics data. Create a Chart component for deal count by stage. Bind its data to a transformer that maps pipeline stage data to bar chart format, with stage name on the X-axis and deal count + total value on Y-axes. For RapidDev-style comprehensive sales operations dashboards that combine Pipedrive pipeline data with marketing attribution from HubSpot or Google Ads, Retool's multi-resource architecture allows you to join data sources in JavaScript queries for a complete revenue operations view.

1// JavaScript transformer — format pipeline summary for stats display
2const summary = data?.data || {};
3const stages = summary.weighted_values_total || {};
4const values = summary.values_total || {};
5
6// Calculate total pipeline value across all stages
7const totalValue = Object.values(values).reduce((sum, stageData) => {
8  return sum + (parseFloat(stageData?.value || 0));
9}, 0);
10
11const totalCount = Object.values(values).reduce((sum, stageData) => {
12  return sum + (parseInt(stageData?.count || 0));
13}, 0);
14
15return {
16  total_value: `$${totalValue.toLocaleString('en-US', { minimumFractionDigits: 2, maximumFractionDigits: 2 })}`,
17  total_count: totalCount,
18  avg_deal_size: totalCount > 0
19    ? `$${(totalValue / totalCount).toLocaleString('en-US', { minimumFractionDigits: 2, maximumFractionDigits: 2 })}`
20    : '$0.00',
21  currency: summary.currency || 'USD'
22};