OCNORA
Start free

Pipedrive

CRM & salesAPI keycredential probe

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.

Connect Pipedrive freePipedrive API docs ↗

Triggers 1

  • Event
    Start a run when a Pipedrive record is created, changed or deleted — a deal, person, organization, activity, lead and more.
    trigger.pipedrive_event

Operations 61

  • Add Product To Deal
    Attach 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 File
    Upload 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 Stage
    Move 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 Activity
    Book 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 Deal
    Create a deal in Pipedrive.
    pipedrive.create_deal
  • Create Lead
    Create 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 Note
    Add 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 Organization
    Create an organization with POST /api/v2/organizations. A name is required.
    pipedrive.create_organization
  • Create Person
    Create 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 Product
    Add a product to the catalogue with POST /api/v2/products. Prices go in `fields` as Pipedrive's prices array.
    pipedrive.create_product
  • Delete Activity
    Delete one activity with DELETE /api/v2/activities/{id}.
    pipedrive.delete_activity
  • Delete Deal
    Delete one deal with DELETE /api/v2/deals/{id}.
    pipedrive.delete_deal
  • Delete File
    Delete one file with DELETE /api/v1/files/{id}.
    pipedrive.delete_file
  • Delete Lead
    Delete one lead with DELETE /api/v1/leads/{id}.
    pipedrive.delete_lead
  • Delete Note
    Delete one note with DELETE /api/v1/notes/{id}.
    pipedrive.delete_note
  • Delete Organization
    Delete one organization with DELETE /api/v2/organizations/{id}.
    pipedrive.delete_organization
  • Delete Person
    Delete one person with DELETE /api/v2/persons/{id}.
    pipedrive.delete_person
  • Delete Product
    Delete one product with DELETE /api/v2/products/{id}.
    pipedrive.delete_product
  • Get Activity
    Read one activity with GET /api/v2/activities/{id}.
    pipedrive.get_activity
  • Get Current User
    Read 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 Deal
    Read one deal with GET /api/v2/deals/{id}, including its custom fields when you name their hashes.
    pipedrive.get_deal
  • Get File
    Read 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 Lead
    Read one lead with GET /api/v1/leads/{id}. A lead id is a UUID, not a number.
    pipedrive.get_lead
  • Get Note
    Read one note with GET /api/v1/notes/{id}.
    pipedrive.get_note
  • Get Organization
    Read one organization with GET /api/v2/organizations/{id}.
    pipedrive.get_organization
  • Get Person
    Read one person with GET /api/v2/persons/{id}.
    pipedrive.get_person
  • Get Pipeline
    Read one pipeline with GET /api/v2/pipelines/{id}.
    pipedrive.get_pipeline
  • Get Product
    Read one product with GET /api/v2/products/{id}.
    pipedrive.get_product
  • Get Stage
    Read one stage with GET /api/v2/stages/{id}.
    pipedrive.get_stage
  • Get User
    Read one user with GET /api/v1/users/{id}.
    pipedrive.get_user
  • List Activities
    Page through activities with GET /api/v2/activities, narrowed by owner, linked record, done state or a saved filter.
    pipedrive.list_activities
  • List Activity Fields
    List 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 Activities
    Page the activities booked against one deal with GET /api/v2/activities, filtered by deal_id.
    pipedrive.list_deal_activities
  • List Deal Fields
    List 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 Products
    Page the product lines attached to one deal with GET /api/v2/deals/{id}/products.
    pipedrive.list_deal_products
  • List Deals
    Page through deals with GET /api/v2/deals, narrowed by owner, person, organization, pipeline, stage, status or a saved filter.
    pipedrive.list_deals
  • List Files
    Page through the files in the account with GET /api/v1/files.
    pipedrive.list_files
  • List Leads
    Page through the Leads Inbox with GET /api/v1/leads, narrowed by owner, person, organization or a saved filter.
    pipedrive.list_leads
  • List Notes
    Page through notes with GET /api/v1/notes, optionally only those on one deal, person, organization or lead.
    pipedrive.list_notes
  • List Organization Fields
    List 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 Organizations
    Page through organizations with GET /api/v2/organizations, narrowed by owner or a saved filter.
    pipedrive.list_organizations
  • List Person Fields
    List 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 Persons
    Page through people with GET /api/v2/persons, narrowed by owner, organization or a saved filter.
    pipedrive.list_persons
  • List Pipelines
    List 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 Fields
    List 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 Products
    Page through the product catalogue with GET /api/v2/products.
    pipedrive.list_products
  • List Stages
    List 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 Users
    List 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 Deals
    Full-text search over deals with GET /api/v2/deals/search. Each match comes back as {result_score, item}.
    pipedrive.search_deals
  • Search Everything
    Search 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 Leads
    Full-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 Organizations
    Full-text search over organizations with GET /api/v2/organizations/search. Each match is {result_score, item}.
    pipedrive.search_organizations
  • Search Persons
    Full-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 Products
    Full-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 Activity
    Change one activity with PATCH /api/v2/activities/{id} — this is also how an activity is marked done.
    pipedrive.update_activity
  • Update Deal
    Change one deal with PATCH /api/v2/deals/{id}. Only the fields you send change; everything else keeps its stored value.
    pipedrive.update_deal
  • Update Lead
    Change one lead with PATCH /api/v1/leads/{id}, including archiving it by setting is_archived.
    pipedrive.update_lead
  • Update Note
    Change 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 Organization
    Change one organization with PATCH /api/v2/organizations/{id}. Only the fields you send change.
    pipedrive.update_organization
  • Update Person
    Change one person with PATCH /api/v2/persons/{id}. Only the fields you send change.
    pipedrive.update_person
  • Update Product
    Change one product with PATCH /api/v2/products/{id}.
    pipedrive.update_product

More in CRM & sales

Run your first Pipedrive workflow today.

Create a free workspace, add the connection, pick a template or describe the workflow to Build with AI. Workflow Health checks it before it runs.

Start freeBook a demo