Manage Pipedrive deals, leads, and contacts from Guild agents

Integrations · Pipedrive

Guild agents read, create, update, and search Pipedrive deals, leads, persons, organizations, pipelines, and activities. Credentials are stored and injected server-side so agent code never sees the API token. Credential policies let you restrict which operations each agent may call, and every request is subject to audit through Guild’s credential proxy.

Book a demo

See how teams govern agents that use Pipedrive.

Start free

Connect Pipedrive and scope your first agent.

What the Pipedrive integration exposes

The tools cover deals, leads, persons, organizations, pipelines, stages, activities, notes, users, field definitions, and cross-entity search. Tools support full create-read-update-delete lifecycles for the core CRM entities. Search tools query by title, notes, and custom fields across deals, leads, persons, and organizations. Agents can also convert a deal to a lead and manage deal discounts and followers.

How it works

Open Credentials in Guild

Go to Credentials in Guild under Access & setup. The page lists connected services and a gallery of available integrations.

Enter your Pipedrive token

Click Pipedrive and paste your personal API token. Find it in Pipedrive under Settings > Personal preferences > API. Personal API tokens do not expire.

Import tools into your agent

Import PipedriveTools from the integration package and spread it into your agent’s tools object. Use pick() to include only the tools your agent needs, since agents perform better with a focused tool set.

Why Pipedrive access needs governing

Pipedrive tools can create, update, and delete deals, persons, organizations, leads, pipelines, and activities. Guild stores the personal API token server-side and injects it through the credential proxy, so the token never enters agent code, prompts, or logs. Credential policies let you write ALLOW and DENY rules that the proxy enforces before any request reaches Pipedrive. Rules can target specific operations by name or glob pattern, scope access to particular agents or workspaces, and restrict HTTP methods to block writes while permitting reads. You can connect the credential at account, workspace, member, or agent scope using Guild’s credentials system. A credential dedicated to one agent never serves others. Without any scoped rules, the default posture is allow-all; deleting that default policy flips the fallback to deny, so only explicitly allowed operations proceed.

About the Pipedrive integration

The Pipedrive integration gives your agents access to Pipedrive CRM records, including deals, contacts, and pipelines.

Authentication

Type: Personal API token
Header: Guild sends your token in the x-api-token request header
Token management: Personal API tokens do not expire

Pipedrive uses a personal API token rather than OAuth. Requests go to the base URL https://api.pipedrive.com, with the API version embedded in each operation path — most operations are on /api/v2, while notes, users, and leads are on /api/v1.

Setup

Open Credentials

Go to Credentials in Guild.

Connect Pipedrive

Click Pipedrive and enter your personal API token. Find the token in Pipedrive under Settings → Personal preferences → API.

Usage

import { PipedriveTools } from "@guildai-services/guildai~pipedrive"
import { llmAgent } from "@guildai/agents-sdk"

export default llmAgent({
  description: "An agent that looks up deals in Pipedrive",
  tools: { ...PipedriveTools },
})

Tools are named with the pipedrive_ prefix — for example, search_deals becomes pipedrive_search_deals.

Selecting specific tools

The integration carries 70 operations. Agents perform better with fewer tools, so use pick() to include only the ones your agent needs.

import { PipedriveTools } from "@guildai-services/guildai~pipedrive"
import { llmAgent, pick } from "@guildai/agents-sdk"

export default llmAgent({
  description: "An agent that manages deals in Pipedrive",
  tools: {
    ...pick(PipedriveTools, [
      "pipedrive_search_deals",
      "pipedrive_get_deal",
      "pipedrive_add_deal",
      "pipedrive_add_note",
    ]),
  },
})

Tools

Tools in the latest published version of guildai~pipedrive:

All 72 tools

Tool	What it does
`pipedrive_add_activity`	Adds a new activity.
`pipedrive_add_deal`	Adds a new deal.
`pipedrive_add_deal_follower`	Adds a user as a follower to the deal.
`pipedrive_add_lead`	Creates a lead.
`pipedrive_add_note`	Adds a new note.
`pipedrive_add_organization`	Adds a new organization.
`pipedrive_add_organization_follower`	Adds a user as a follower to the organization.
`pipedrive_add_person`	Adds a new person.
`pipedrive_add_person_follower`	Adds a user as a follower to the person.
`pipedrive_add_pipeline`	Adds a new pipeline.
`pipedrive_add_stage`	Adds a new stage, returns the ID upon success.
`pipedrive_convert_deal_to_lead`	Initiates a conversion of a deal to a lead.
`pipedrive_delete_activity`	Marks an activity as deleted.
`pipedrive_delete_additional_discount`	Removes a discount from a deal, changing the deal value if the deal has one-time products attached.
`pipedrive_delete_deal`	Marks a deal as deleted.
`pipedrive_delete_deal_follower`	Deletes a user follower from the deal.
`pipedrive_delete_note`	Deletes a specific note.
`pipedrive_delete_organization`	Marks a organization as deleted.
`pipedrive_delete_organization_follower`	Deletes a user follower from the organization.
`pipedrive_delete_person`	Marks a person as deleted.
`pipedrive_delete_person_follower`	Deletes a user follower from the person.
`pipedrive_delete_pipeline`	Marks a pipeline as deleted.
`pipedrive_delete_stage`	Marks a stage as deleted.
`pipedrive_get_activities`	Returns data about all activities.
`pipedrive_get_activity`	Returns the details of a specific activity.
`pipedrive_get_additional_discounts`	Lists discounts attached to a deal.
`pipedrive_get_archived_deals`	Returns data about all archived deals.
`pipedrive_get_current_user`	Returns data about an authorized user within the company with bound company data: company ID, company name, and domain.
`pipedrive_get_deal`	Returns the details of a specific deal.
`pipedrive_get_deal_conversion_status`	Returns information about the conversion.
`pipedrive_get_deal_fields`	Returns metadata about all deal fields in the company.
`pipedrive_get_deal_followers`	Lists users who are following the deal.
`pipedrive_get_deal_followers_changelog`	Lists changelogs about users have followed the deal.
`pipedrive_get_deal_products`	Lists products attached to a deal.
`pipedrive_get_deals`	Returns data about all not archived deals.
`pipedrive_get_lead`	Returns details of a specific lead.
`pipedrive_get_lead_labels`	Returns details of all lead labels.
`pipedrive_get_leads`	Returns multiple not archived leads.
`pipedrive_get_note`	Returns details about a specific note.
`pipedrive_get_notes`	Returns all notes.
`pipedrive_get_organization`	Returns the details of a specific organization.
`pipedrive_get_organization_fields`	Returns metadata about all organization fields in the company.
`pipedrive_get_organization_followers`	Lists users who are following the organization.
`pipedrive_get_organization_followers_changelog`	Lists changelogs about users have followed the organization.
`pipedrive_get_organizations`	Returns data about all organizations.
`pipedrive_get_person`	Returns the details of a specific person.
`pipedrive_get_person_fields`	Returns metadata about all person fields in the company.
`pipedrive_get_person_followers`	Lists users who are following the person.
`pipedrive_get_person_followers_changelog`	Lists changelogs about users have followed the person.
`pipedrive_get_person_picture`	Returns the picture associated with a person.
`pipedrive_get_persons`	Returns data about all persons.
`pipedrive_get_pipeline`	Returns data about a specific pipeline.
`pipedrive_get_pipelines`	Returns data about all pipelines.
`pipedrive_get_stage`	Returns data about a specific stage.
`pipedrive_get_stages`	Returns data about all stages.
`pipedrive_get_users`	Returns data about all users within the company.
`pipedrive_post_additional_discount`	Adds a discount to a deal, changing the deal value if the deal has one-time products attached.
`pipedrive_search_deals`	Searches all deals by title, notes and/or custom fields.
`pipedrive_search_item`	Performs a search from your choice of item types and fields.
`pipedrive_search_item_by_field`	Performs a search from the values of a specific field.
`pipedrive_search_leads`	Searches all leads by title, notes and/or custom fields.
`pipedrive_search_organization`	Searches all organizations by name, address, notes and/or custom fields.
`pipedrive_search_persons`	Searches all persons by name, email, phone, notes and/or custom fields.
`pipedrive_update_activity`	Updates the properties of an activity.
`pipedrive_update_additional_discount`	Edits a discount added to a deal, changing the deal value if the deal has one-time products attached.
`pipedrive_update_deal`	Updates the properties of a deal.
`pipedrive_update_lead`	Updates one or more properties of a lead.
`pipedrive_update_note`	Updates a note.
`pipedrive_update_organization`	Updates the properties of a organization.
`pipedrive_update_person`	Updates the properties of a person.
`pipedrive_update_pipeline`	Updates the properties of a pipeline.
`pipedrive_update_stage`	Updates the properties of a stage.

Supported capabilities

The curated specification covers 70 operations across the CRM core entities.

Capability	Description
Deals	Manage deals and their lifecycle.
Leads	Create, read, and search leads.
Persons	Manage person (contact) records.
Organizations	Manage organization records.
Pipelines	Read and manage sales pipelines.
Stages	Read and manage pipeline stages.
Activities	Manage activities such as calls and meetings.
Notes	Create and manage notes.
Search	Search across CRM records.
Users	Read user records.
Field-definitions	List field definitions for CRM entities.

Creating a lead requires linking it to a person or an organization (or both). Leads support the same hash-keyed custom fields as deals, so you can push a full lead payload through the integration.

Webhook events

Pipedrive uses a credential-scoped webhook model. When you enable the first Pipedrive trigger on a connection, Guild registers one webhook for all Pipedrive events and routes them to matching triggers. Disabling the last trigger removes it. Deliveries are checked with a password Guild generates for the webhook. A trigger can narrow an event to one action, such as guild trigger create --type webhook --integration pipedrive --event deal --action create --agent <identifier>. Without an action it fires on every action of that event. A trigger with no event fires on every Pipedrive event, including objects the table doesn’t list, such as products.

Event	Description	Actions
`activity`	Activity created, changed, or deleted	`change`, `create`, `delete`
`deal`	Deal created, changed, or deleted	`change`, `create`, `delete`
`lead`	Lead created, changed, or deleted	`change`, `create`, `delete`
`note`	Note created, changed, or deleted	`change`, `create`, `delete`
`organization`	Organization created, changed, or deleted	`change`, `create`, `delete`
`person`	Person created, changed, or deleted	`change`, `create`, `delete`

Payloads use Pipedrive’s webhook v2 format, with the record in data, its earlier values in previous, and the event in meta. Guild doesn’t filter out changes the agent makes itself, so an agent that updates a deal from a deal change trigger fires that trigger again. Have the agent check meta.user_id and skip changes made by the connected Pipedrive user.

Limitations

Products, projects, tasks, and installments endpoints are omitted.
Beta endpoints are omitted.
Pipedrive pauses a webhook for 30 minutes after 10 failed deliveries in a row, and deletes it after three days without a successful delivery. If triggers stop firing, disable every Pipedrive trigger on the connection, then enable them again so Guild registers a new webhook.

Frequently asked questions

Does the Pipedrive integration support OAuth?

No. Pipedrive authenticates with a personal API token. Guild sends the token in the x-api-token request header. Personal API tokens do not expire.

Can an agent react when a deal changes in Pipedrive?

Yes. Guild registers a webhook with Pipedrive when you enable a trigger on the connection. You can scope a trigger to a specific event such as deal and action such as create, or leave it unscoped to fire on every Pipedrive event. Guild routes incoming payloads to matching triggers automatically.

Can I limit which Pipedrive operations an agent can call?

Yes. Credential policies let you write ALLOW and DENY rules scoped to specific operations, agents, and workspaces. The credential proxy enforces them before any request leaves Guild, and agents cannot bypass the check.

Are Pipedrive products and projects covered by the integration?

Not yet. The integration omits products, projects, tasks, installments, and beta endpoints.

Put a governed agent on Pipedrive this week

Book a demo

See how teams govern agents that use Pipedrive.

Start free

Connect Pipedrive and scope your first agent.

Read: Docs: Credential policies · Credentials · Tools in agents

Overview

Code & CI/CD

Communication

Project management

Testing

Productivity

Monitoring & observability

Data

Customer support

Sales & finance

Recruiting

Manage Pipedrive deals, leads, and contacts from Guild agents

Book a demo

Start free

What the Pipedrive integration exposes

How it works

Why Pipedrive access needs governing

About the Pipedrive integration

Authentication

Setup

Usage

Selecting specific tools

Tools

Supported capabilities

Webhook events

Limitations

Frequently asked questions

Put a governed agent on Pipedrive this week

Book a demo

Start free

Book a demo

Start free

​What the Pipedrive integration exposes

​How it works

​Why Pipedrive access needs governing

​About the Pipedrive integration

​Authentication

​Setup

​Usage

​Selecting specific tools

​Tools

​Supported capabilities

​Webhook events

​Limitations

​Frequently asked questions

​Put a governed agent on Pipedrive this week

Book a demo

Start free

​Related

What the Pipedrive integration exposes

How it works

Why Pipedrive access needs governing

About the Pipedrive integration

Authentication

Setup

Usage

Selecting specific tools

Tools

Supported capabilities

Webhook events

Limitations

Frequently asked questions

Put a governed agent on Pipedrive this week

Related