Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Pipedrive

Synchronize deals, people, organisations and leads, with key sales triggers.

CategoryCRM
AuthenticationOAuth 2.0
Version0.9.0
Published scopes9 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Pipedrive with Flows360

Synchronize deals, people, organisations and leads, with key sales triggers.

Use the Pipedrive connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 30 actions and 14 triggers.

Available actions

  • Add Follower
  • Retrieve a Note
  • Create Note
  • Add Labels to Person
  • Add Product to Deal
  • Attach File
  • Create Activity
  • Update Activity
  • Plus 22 additional declared actions.

Available triggers

  • New Person
  • New Deal
  • New Activity
  • New Note
  • Updated Person
  • Updated Deal
  • Plus 8 additional declared triggers.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Pipedrive
  • Package: @activepieces/piece-pipedrive@0.9.0
  • Exact artifact digest: sha256:5b85d45dcbfcc774729dc2d7222587f91377a90df76e560cdd837bc85f1d9883
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Add Follower (add-follower), Adds a follower to a deal, person, organization or product. Classification: read.
  • Retrieve a Note (get-note), Finds a note by ID. Classification: read.
  • Create Note (create-note), Creates a new note. Classification: read.
  • Add Labels to Person (add-labels-to-person), Adds existing labels to an existing person. Classification: read.
  • Add Product to Deal (add-product-to-deal), Adds a product to a deal. Classification: read.
  • Attach File (attach-file), Uploads a file and attaches it to a deal,person,organization,activity or product. Classification: read.
  • Create Activity (create-activity), Creates a new activity. Classification: read.
  • Update Activity (update-activity), Updates an existing activity. Classification: read.
  • Create Deal (create-deal), Creates a new deal. Classification: read.
  • Update Deal (update-deal), Updates an existing deal. Classification: read.
  • Create Lead (create-lead), Creates a new lead. Classification: read.
  • Update Lead (update-lead), Updates an existing lead. Classification: read.
  • Create Organization (create-organization), Creates a new organization. Classification: read.
  • Update Organization (update-organization), Updates an existing organization. Classification: read.
  • Create Person (create-person), Creates a new person. Classification: read.
  • Update Person (update-person), Updates an existing person. Classification: read.
  • Create Product (create-product), Creates a new product. Classification: read.
  • Update Product (update-product), Updates an existing product. Classification: read.
  • Find Deals Associated With Person (find-deals-associated-with-person), Finds multiple deals related to a specific person. Classification: read.
  • Find Product (find-product), Finds a product by name Classification: read.
  • Find Products (find-products), Finds a product or products by name or product code. Classification: read.
  • Find Notes (find-notes), Finds notes by Deal, Lead, Person, or Organization ID. Classification: read.
  • Retrieve a Product (get-product), Finds a product by ID. Classification: read.
  • Find Organization (find-organization), Finds an organization. Classification: read.
  • Find Person (find-person), Finds a person. Classification: read.
  • Find Deal (find-deal), Finds a deal by any field. Classification: read.
  • Find Activity (find-activity), Finds an activity by subject. Classification: read.
  • Find User (find-user), Finds a user by name or email. Classification: read.
  • Find Lead (find-lead), Finds leads by title. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Person, webhook.
  • New Deal, webhook.
  • New Activity, webhook.
  • New Note, webhook.
  • Updated Person, webhook.
  • Updated Deal, webhook.
  • Updated Deal Stage, webhook.
  • New Lead, webhook.
  • New Organization, webhook.
  • Updated Organization, webhook.
  • Activity Matching Filter, polling.
  • Deal Matching Filter, polling.
  • Person Matching Filter, polling.
  • Organization Matching Filter, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects44
Supported actionsNot published
Triggers14

Authentication

Authentication method: OAuth 2.0

Required scopes

baseadmincontacts:fullusers:readdeals:fullactivities:fullleads:fullproducts:fullwebhooks:full

Authentication profiles

connection · oauth2

OAuth scopes: base, admin, contacts:full, users:read, deals:full, activities:full, leads:full, products:full, webhooks:full

Supported objects

ObjectReadWriteNotes
Add Follower Yes No Adds a follower to a deal, person, organization or product.
Retrieve a Note Yes No Finds a note by ID.
Create Note Yes No Creates a new note.
Add Labels to Person Yes No Adds existing labels to an existing person.
Add Product to Deal Yes No Adds a product to a deal.
Attach File Yes No Uploads a file and attaches it to a deal,person,organization,activity or product.
Create Activity Yes No Creates a new activity.
Update Activity Yes No Updates an existing activity.
Create Deal Yes No Creates a new deal.
Update Deal Yes No Updates an existing deal.
Create Lead Yes No Creates a new lead.
Update Lead Yes No Updates an existing lead.
Create Organization Yes No Creates a new organization.
Update Organization Yes No Updates an existing organization.
Create Person Yes No Creates a new person.
Update Person Yes No Updates an existing person.
Create Product Yes No Creates a new product.
Update Product Yes No Updates an existing product.
Find Deals Associated With Person Yes No Finds multiple deals related to a specific person.
Find Product Yes No Finds a product by name
Find Products Yes No Finds a product or products by name or product code.
Find Notes Yes No Finds notes by Deal, Lead, Person, or Organization ID.
Retrieve a Product Yes No Finds a product by ID.
Find Organization Yes No Finds an organization.
Find Person Yes No Finds a person.
Find Deal Yes No Finds a deal by any field.
Find Activity Yes No Finds an activity by subject.
Find User Yes No Finds a user by name or email.
Find Lead Yes No Finds leads by title.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Person Yes No webhook trigger declared by the pinned package.
New Deal Yes No webhook trigger declared by the pinned package.
New Activity Yes No webhook trigger declared by the pinned package.
New Note Yes No webhook trigger declared by the pinned package.
Updated Person Yes No webhook trigger declared by the pinned package.
Updated Deal Yes No webhook trigger declared by the pinned package.
Updated Deal Stage Yes No webhook trigger declared by the pinned package.
New Lead Yes No webhook trigger declared by the pinned package.
New Organization Yes No webhook trigger declared by the pinned package.
Updated Organization Yes No webhook trigger declared by the pinned package.
Activity Matching Filter Yes No polling trigger declared by the pinned package.
Deal Matching Filter Yes No polling trigger declared by the pinned package.
Person Matching Filter Yes No polling trigger declared by the pinned package.
Organization Matching Filter Yes No polling trigger declared by the pinned package.

Triggers

New Person · Webhook

Triggers when a new person is created

New Deal · Webhook

Triggers when a new deal is created.

New Activity · Webhook

Triggers when a new activity is added

New Note · Webhook

Triggers when a new note is created.

Updated Person · Webhook

Triggers when a person is updated.

Updated Deal · Webhook

Triggers when a deal is updated.

Inputs

  • filter_by · string
  • filter_by_field_value · object
  • field_to_watch · string
Updated Deal Stage · Webhook

Triggers when a deal's stage is updated.

Inputs

  • stage_id · string
New Lead · Webhook

Triggers when a new lead is created.

New Organization · Webhook

Triggers when a new organization is created.

Updated Organization · Webhook

Triggers when an existing organization is updated.

Activity Matching Filter · Poll

Trigges when an activity newly matches a Pipedrive filter for the first time.

Inputs

  • filterId · string
Deal Matching Filter · Poll

Trigges when a deal newly matches a Pipedrive filter for the first time.

Inputs

  • filterId · string
  • status · string
Person Matching Filter · Poll

Triggers when a person newly matches a Pipedrive filter for the first time.

Inputs

  • filterId · string
Organization Matching Filter · Poll

Triggers when an organization newly matches a Pipedrive filter for the first time.

Inputs

  • filterId · string

Setup

Setup

  1. Add the Pipedrive connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.

OAuth scopes

  • base
  • admin
  • contacts:full
  • users:read
  • deals:full
  • activities:full
  • leads:full
  • products:full
  • webhooks:full
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-pipedrive@0.9.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 30 actions and 14 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Pipedrive connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-pipedrive@0.9.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com