Pipedrive integration

What it does

The Pipedrive integration lets your agency operate on a client's sales pipeline without leaving TaskJuice. Connect a client's Pipedrive account once and you can create and update deals, manage people and organizations, log activities and notes, and react to deal or contact changes the moment they happen in the CRM. Every action targets the client's own Pipedrive company subdomain, so a workflow you build for one client runs unmodified against the next account you onboard.

Connect a Pipedrive account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Pipedrive and click Connect.
3. Enter the client's company domain (the subdomain in their Pipedrive URL, for example acme for acme.pipedrive.com).
4. Sign in to Pipedrive as a user with permission to install marketplace apps and approve the requested scopes (deals, contacts, activities, users).
5. TaskJuice returns to the workspace with the connection ready to use in any workflow.

To revoke access, the account owner can open Pipedrive Settings, Marketplace apps, and remove the TaskJuice app. The full grant flow is documented in the Pipedrive OAuth authorization guide.

Triggers

• pipedrive/deal-added fires when a new deal is created in the client's Pipedrive account.
• pipedrive/deal-updated fires when an existing deal is updated. The payload carries both the new deal body under data and the prior state under previous, so workflows can detect stage transitions and other field-level diffs without a follow-up read.
• pipedrive/person-added fires when a new person (contact) is created in the account.

Pipedrive Webhooks v2 do not sign payloads. They authenticate to TaskJuice by sending a static HTTP Basic credential the agency configures when subscribing to the webhook in Pipedrive Settings, Tools and apps, Webhooks. TaskJuice verifies the credential by comparing the inbound Authorization header to the shared secret stored on the trigger. Activations that fail the check are rejected before they reach the workflow.

Actions

• pipedrive/create-deal, pipedrive/update-deal, pipedrive/get-deal, pipedrive/delete-deal, pipedrive/list-deals cover the full deal lifecycle, including stage moves and status transitions.
• pipedrive/create-person creates a person (contact) with email and phone arrays, owner, and organization association.
• pipedrive/create-organization creates an organization with owner, address, and visibility settings.
• pipedrive/create-activity logs a call, meeting, task, deadline, email, or lunch tied to a deal, person, or organization.
• pipedrive/add-note attaches a free-form note (HTML allowed) to a deal, person, or organization, with optional pin-to-deal behavior.

Known limitations

• Pipedrive enforces a token-bucket rate limit per API token (refer to the Pipedrive rate-limiting reference for the current allowance per plan tier). When the API returns a 429 status, TaskJuice surfaces it as a retryable error and respects the Retry-After header.
• A connection is scoped to a single Pipedrive company domain. To run workflows across multiple client accounts, create one connection per account.
• Webhook authentication uses Pipedrive's HTTP Basic delivery model, not a signed payload. Rotate the configured credential in Pipedrive and in the TaskJuice trigger together when staff turnover happens.
• The integration targets the Pipedrive v1 REST API and the v2 webhook payload format. Endpoints or webhook fields outside those contracts are not exposed.