Pipedrive
CRM & salesAPI keyConnection test available
Create deals in Pipedrive (API token).
OCNORA ships 61 typed Pipedrive operations and 1 trigger. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Pipedrive
- Authentication
- API key
- Credential
- the Pipedrive API token, or {"api_token": "…"}the Pipedrive API token
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
- Prerequisites
- The token's user must be an admin: creating a webhook is an admin action in Pipedrive, and a regular user's token can read deals and still fail to publish. Publishing also needs MANTLE_APP_PUBLIC_BASE_URL set to a URL Pipedrive can reach.
Prerequisites are taken from the connection notes in this provider’s node contracts; each node’s reference page says which apply to it.
What you can do with Pipedrive
Operations, grouped by what they do to your data, plus 1 trigger that start a run.
Create and send 8
Read and search 36
Delete and cancel 8
Other operations 2
A sample Pipedrive workflow
- 1Eventtrigger.pipedrive_eventStart a run when a Pipedrive record is created, changed or deleted — a deal, person, organization, activity, lead and more.
- 2Get Activitypipedrive.get_activityRead one activity with GET /api/v2/activities/{id}.
- 3Add Product To Dealpipedrive.add_deal_productAttach a product line to a deal with POST /api/v2/deals/{id}/products. Pipedrive requires a product, a unit price and a quantity.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 61
- Add Product To DealAttach a product line to a deal with POST /api/v2/deals/{id}/products. Pipedrive requires a product, a unit price and a quantity.pipedrive.add_deal_product
- Attach FileUpload a file with POST /api/v1/files and link it to a deal, person, organization, activity, product or lead. The bytes travel as base64, which is the shape every Mantle download node emits.pipedrive.attach_file
- Change Deal StageMove a deal to another pipeline stage with PATCH /api/v2/deals/{id}. Read the stage ids first with Pipedrive: List Stages.pipedrive.change_deal_stage
- Create ActivityBook an activity — a call, meeting or task — with POST /api/v2/activities, optionally attached to a deal, lead, person or organization.pipedrive.create_activity
- Create DealCreate a deal in Pipedrive.pipedrive.create_deal
- Create LeadCreate a lead in the Leads Inbox with POST /api/v1/leads. Pipedrive needs a title and either a person or an organization to attach it to.pipedrive.create_lead
- Create NoteAdd a note with POST /api/v1/notes. The content is HTML, and the note has to hang off a deal, person, organization, lead or project.pipedrive.create_note
- Create OrganizationCreate an organization with POST /api/v2/organizations. A name is required.pipedrive.create_organization
- Create PersonCreate a person with POST /api/v2/persons. Pipedrive needs a name; an email or phone is sent as its primary entry.pipedrive.create_person
- Create ProductAdd a product to the catalogue with POST /api/v2/products. Prices go in `fields` as Pipedrive's prices array.pipedrive.create_product
- Delete ActivityDelete one activity with DELETE /api/v2/activities/{id}.pipedrive.delete_activity
- Delete DealDelete one deal with DELETE /api/v2/deals/{id}.pipedrive.delete_deal
- Delete FileDelete one file with DELETE /api/v1/files/{id}.pipedrive.delete_file
- Delete LeadDelete one lead with DELETE /api/v1/leads/{id}.pipedrive.delete_lead
- Delete NoteDelete one note with DELETE /api/v1/notes/{id}.pipedrive.delete_note
- Delete OrganizationDelete one organization with DELETE /api/v2/organizations/{id}.pipedrive.delete_organization
- Delete PersonDelete one person with DELETE /api/v2/persons/{id}.pipedrive.delete_person
- Delete ProductDelete one product with DELETE /api/v2/products/{id}.pipedrive.delete_product
- Get ActivityRead one activity with GET /api/v2/activities/{id}.pipedrive.get_activity
- Get Current UserRead the user the API token belongs to with GET /api/v1/users/me, together with the company id, name and domain the token is bound to.pipedrive.get_current_user
- Get DealRead one deal with GET /api/v2/deals/{id}, including its custom fields when you name their hashes.pipedrive.get_deal
- Get FileRead one file's metadata with GET /api/v1/files/{id} — name, size, type and what it is attached to, not its bytes.pipedrive.get_file
- Get LeadRead one lead with GET /api/v1/leads/{id}. A lead id is a UUID, not a number.pipedrive.get_lead
- Get NoteRead one note with GET /api/v1/notes/{id}.pipedrive.get_note
- Get OrganizationRead one organization with GET /api/v2/organizations/{id}.pipedrive.get_organization
- Get PersonRead one person with GET /api/v2/persons/{id}.pipedrive.get_person
- Get PipelineRead one pipeline with GET /api/v2/pipelines/{id}.pipedrive.get_pipeline
- Get ProductRead one product with GET /api/v2/products/{id}.pipedrive.get_product
- Get StageRead one stage with GET /api/v2/stages/{id}.pipedrive.get_stage
- Get UserRead one user with GET /api/v1/users/{id}.pipedrive.get_user
- List ActivitiesPage through activities with GET /api/v2/activities, narrowed by owner, linked record, done state or a saved filter.pipedrive.list_activities
- List Activity FieldsList the field definitions for activities with GET /api/v2/activityFields. Read `key` off the field you want: that 40-character hash is how a custom field is written and read everywhere else in the API.pipedrive.list_activity_fields
- List Deal ActivitiesPage the activities booked against one deal with GET /api/v2/activities, filtered by deal_id.pipedrive.list_deal_activities
- List Deal FieldsList the field definitions for deals with GET /api/v2/dealFields. Read `key` off the field you want: that 40-character hash is how a custom field is written and read everywhere else in the API.pipedrive.list_deal_fields
- List Deal ProductsPage the product lines attached to one deal with GET /api/v2/deals/{id}/products.pipedrive.list_deal_products
- List DealsPage through deals with GET /api/v2/deals, narrowed by owner, person, organization, pipeline, stage, status or a saved filter.pipedrive.list_deals
- List FilesPage through the files in the account with GET /api/v1/files.pipedrive.list_files
- List LeadsPage through the Leads Inbox with GET /api/v1/leads, narrowed by owner, person, organization or a saved filter.pipedrive.list_leads
- List NotesPage through notes with GET /api/v1/notes, optionally only those on one deal, person, organization or lead.pipedrive.list_notes
- List Organization FieldsList the field definitions for organizations with GET /api/v2/organizationFields. Read `key` off the field you want: that 40-character hash is how a custom field is written and read everywhere else in the API.pipedrive.list_organization_fields
- List OrganizationsPage through organizations with GET /api/v2/organizations, narrowed by owner or a saved filter.pipedrive.list_organizations
- List Person FieldsList the field definitions for people with GET /api/v2/personFields. Read `key` off the field you want: that 40-character hash is how a custom field is written and read everywhere else in the API.pipedrive.list_person_fields
- List PersonsPage through people with GET /api/v2/persons, narrowed by owner, organization or a saved filter.pipedrive.list_persons
- List PipelinesList the account's pipelines with GET /api/v2/pipelines — the first step in turning a pipeline name into the id a deal node needs.pipedrive.list_pipelines
- List Product FieldsList the field definitions for products with GET /api/v2/productFields. Read `key` off the field you want: that 40-character hash is how a custom field is written and read everywhere else in the API.pipedrive.list_product_fields
- List ProductsPage through the product catalogue with GET /api/v2/products.pipedrive.list_products
- List StagesList stages with GET /api/v2/stages, for one pipeline or for all of them. Read the stage id from here before moving a deal.pipedrive.list_stages
- List UsersList every user in the company with GET /api/v1/users — how an owner_id is looked up from a name or an email address.pipedrive.list_users
Show 13 more
- Search DealsFull-text search over deals with GET /api/v2/deals/search. Each match comes back as {result_score, item}.pipedrive.search_deals
- Search EverythingSearch across several record types at once with GET /api/v2/itemSearch. Each match is {result_score, item}, and `item.type` says what was found.pipedrive.search_items
- Search LeadsFull-text search over leads with GET /api/v2/leads/search. Lead search is the one part of leads Pipedrive shipped on v2, so this one pages with a cursor.pipedrive.search_leads
- Search OrganizationsFull-text search over organizations with GET /api/v2/organizations/search. Each match is {result_score, item}.pipedrive.search_organizations
- Search PersonsFull-text search over people with GET /api/v2/persons/search — the way to find someone by email address. Each match is {result_score, item}.pipedrive.search_persons
- Search ProductsFull-text search over the product catalogue with GET /api/v2/products/search — the way to turn a product name or code into an id for Add Product To Deal.pipedrive.search_products
- Update ActivityChange one activity with PATCH /api/v2/activities/{id} — this is also how an activity is marked done.pipedrive.update_activity
- Update DealChange one deal with PATCH /api/v2/deals/{id}. Only the fields you send change; everything else keeps its stored value.pipedrive.update_deal
- Update LeadChange one lead with PATCH /api/v1/leads/{id}, including archiving it by setting is_archived.pipedrive.update_lead
- Update NoteChange one note with PUT /api/v1/notes/{id}. Notes are still a v1 resource, so this is a PUT rather than the v2 PATCH.pipedrive.update_note
- Update OrganizationChange one organization with PATCH /api/v2/organizations/{id}. Only the fields you send change.pipedrive.update_organization
- Update PersonChange one person with PATCH /api/v2/persons/{id}. Only the fields you send change.pipedrive.update_person
- Update ProductChange one product with PATCH /api/v2/products/{id}.pipedrive.update_product
Pipedrive questions
- How does OCNORA authenticate with Pipedrive?
- With a stored API key credential, shaped the Pipedrive API token, or {"api_token": "…"} or the Pipedrive API token. A connection test can check it when you add it.
- What can I automate with Pipedrive?
- 61 typed operations and 1 trigger, each with a reference page listing its config fields and the shapes it emits.
- What if the Pipedrive operation I need is not listed?
- Where Pipedrive has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Pipedrive?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Pipedrive calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Pipedrive workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.