Pipedrive
Manage deals, contacts, leads, activities, pipeline metadata, and CRM webhooks
Connect Pipedrive when a project needs current CRM data or must change sales records. A shared connection uses one authorized Pipedrive company account for a project. A published app can let each signed-in app user authorize their own account.
Before you connect
A Swarmz administrator must configure and enable the Pipedrive OAuth application before the connector appears. Each user still signs in to Pipedrive and approves access; the administrator's client secret is not a user's Pipedrive credential.
In the Pipedrive Developer Hub, register the callback URL shown on the Swarmz admin integration card. Configure the app scopes for the records your projects use. Read-only connections request deal, contact, activity, and lead reads. Write connections request the matching full scopes and webhook access.
Available operations
| Operation | What it does | Limit per minute |
|---|---|---|
list_deals, get_deal | Lists filtered deals or reads one deal | 30 |
create_deal, update_deal | Creates or updates one deal | 10 |
list_people | Lists people contacts | 30 |
search_people | Searches people by supported Pipedrive fields | 20 |
create_person, update_person | Creates or updates one person | 10 |
list_organizations | Lists organizations | 30 |
create_organization, update_organization | Creates or updates one organization | 10 |
list_leads | Lists Leads Inbox records | 20 |
create_lead, update_lead | Creates or updates one lead | 10 |
list_activities | Lists sales activities and follow-ups | 30 |
create_activity, update_activity | Creates, updates, or completes one activity | 10 |
list_pipelines, list_stages | Lists pipeline and stage metadata | 30 |
list_users | Lists users for owner fields | 20 |
create_webhook | Registers one HTTPS CRM-change webhook | 5 |
Webhook destinations must use HTTPS and cannot contain embedded credentials. Write operations pause for AI approval during a build.
Connect Pipedrive
Ask for a concrete workflow and state whose account it should use. For a company sales dashboard, say: “Use our shared Pipedrive connection to show open deals by stage and overdue activities.” For a multi-tenant app, say: “Let each signed-in user connect Pipedrive and manage their own leads.”
Select Connect new, choose read access, add write access only when the project will change CRM records or register webhooks, then approve access in Pipedrive. See Connector connection modes for the shared and app-user difference.
Verify Pipedrive
- List pipelines and stages, then confirm their names in Pipedrive.
- Search for a known test contact and list open deals.
- Create a disposable person and deal, then update one field on each.
- Create a test activity, mark it complete, and confirm the result in Pipedrive.
- If the project uses webhooks, register a disposable HTTPS endpoint and trigger one matching test change.
- Delete the disposable records and webhook in Pipedrive.
If reads work but writes fail, reconnect with the matching full scope and confirm that the app has that scope in the Pipedrive Developer Hub. If a refresh fails, reconnect the account; Pipedrive may replace a refresh token during successful refresh.