StackOSWork, organized
LibraryWorkflowsAgentsOrchestratorsIntegrationsArticles

Pipedrive CRM provider contract for organizations, people, deals, activities, and notes.

2 listed actions1 capability groups

Connection facts

What the Pipedrive connector actually exposes.

These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.

Connection method
oauth-or-api-token
Setup
Register a Pipedrive app with the fixed StackOS callback and deals:read plus search:read app scopes, then use Connect with Pipedrive. For private personal integrations, the supported personal API token method remains available.
Capability groups
Pipeline Management
Action boundaries
2 read actions

Action catalog

Actions listed for Pipedrive.

Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.

2 matching actions

Pipeline ManagementReads data

List Pipedrive Deals

List bounded Pipedrive deal context for pipeline review.

Pipeline ManagementReads data

Search Pipedrive Deals

Search bounded Pipedrive deal context for pipeline review.

Direct answer

How does the Pipedrive integration work?

People continue using Pipedrive as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.

  1. 01Your requestStart in your AI
  2. 02StackOS planExpands the steps
  3. 03PipedriveDoes its bounded part
  4. 04Checked resultKeeps the proof

More from GTM And RevOps

Related integrations.

See the plugin →

Common questions

Pipedrive and StackOS.

What can the Pipedrive integration do in StackOS?

The current catalog includes 2 Pipedrive actions across Pipeline Management. The exact actions used depend on the workflow and approval rules.

Does StackOS replace Pipedrive?

No. Pipedrive remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.