Pipedrive Tools

The Pipedrive block lets a workflow create and manage records in the Pipedrive CRM. Use it to create deals and persons (contacts), list deals filtered by status, and search deals by term during a workflow run.

Overview

Operations

Configuration

pipedrive_create_deal

POST https://api.pipedrive.com/v1/deals

pipedrive_list_deals

GET https://api.pipedrive.com/v1/deals

pipedrive_create_person

POST https://api.pipedrive.com/v1/persons

pipedrive_search_deals

GET https://api.pipedrive.com/v1/deals/search

Outputs

pipedrive_create_deal

• data (json) — The created Pipedrive deal object.
• metadata (json) — Deal identifiers.
  • id (number) — Deal ID.

pipedrive_list_deals

• data (json) — Array of Pipedrive deal objects.
• metadata (json) — List metadata.
  • count (number) — Number of items returned.
  • has_more (boolean) — Whether more items exist beyond this page.

pipedrive_create_person

• data (json) — The created Pipedrive person object.
• metadata (json) — Person identifiers.
  • id (number) — Person ID.

pipedrive_search_deals

• data (json) — Array of matching Pipedrive deal search results.
• metadata (json) — Search result metadata.
  • count (number) — Number of items returned.
  • has_more (boolean) — Whether more items exist beyond this page.

YAML Example

pipedrive_1:
  type: pipedrive
  name: "Pipedrive"
  inputs:
    operation: "pipedrive_create_deal"
    title: "Enterprise Software License"
    value: 5000
    currency: "USD"
    apiKey: "{{PIPEDRIVE_API_KEY}}"
  connections:
    outgoing:
      - target: next-block-id

Tips

• Generate an API token in Pipedrive under Settings → Personal preferences → API, then store it as an environment variable and reference it with {{PIPEDRIVE_API_KEY}}. The token is passed as the api_token query parameter on every request — there is no OAuth flow.
• The block defaults to the pipedrive_create_deal operation. Set operation to one of pipedrive_create_deal, pipedrive_list_deals, pipedrive_create_person, or pipedrive_search_deals to switch behavior.
• For pipedrive_search_deals, the term must be at least 2 characters or Pipedrive will reject the request. Search results are returned under data as an array of match items (not the same shape as full deal objects from pipedrive_list_deals).
• Reference outputs in downstream blocks with double braces, e.g. {{pipedrive_1.metadata.id}} for a newly created deal/person ID or {{pipedrive_1.data}} for the returned array or object.
• person_id, org_id, and stage_id expect numeric Pipedrive IDs. Use pipedrive_search_deals or the Pipedrive UI to look up the correct IDs before creating linked records.