Pipedrive integration

Joltuar connects to a Pipedrive company account so your team's meeting notes, action items and deal updates can flow into the CRM your sales team already lives in. One connection serves the whole Joltuar workspace — you don't reconnect per user.

What it does

Once connected, Pipedrive shows up as a tool source for the Joltuar Assistant (the chat panel, and the same tools over MCP for external AI clients):

• Look things up — search deals by name, read a deal's fields and custom fields, list its activities, and see your pipelines and stages.
• Write updates on request — add a note to a deal, create or update an activity (task), and update a deal's custom fields. Every write always shows you a confirmation card first; nothing is pushed to Pipedrive silently from chat.
• Post-call automation — a Workflow step (pipedrive_post_call_update) that runs after a call to append the summary as a note, create one follow-up task, and optionally update deal value, a pipeline-stage/label rule, or a no-show field. This runs automatically once a workflow is set up and approved for your workspace — see "Post-call automation" below.

Joltuar never creates a new deal and never renames one. Writes only ever land on a deal the automation or the chat tool already matched or that you named explicitly.

Who can connect

Only a workspace owner or admin can connect or disconnect Pipedrive — Joltuar treats the connection as belonging to the organization, not to whoever clicked Connect. Whichever Pipedrive user approves the consent screen is the account the connection is minted for, so we recommend a Pipedrive admin (or at least someone whose Pipedrive user can see the deals your team needs Joltuar to touch) does the connecting — Joltuar can only see and edit what that Pipedrive user's account can see.

Prerequisites

• A Pipedrive account with permission to install apps from the Pipedrive Marketplace (or to approve the requested scopes on the consent screen).
• A Joltuar workspace you're signed into.

Connect Pipedrive

1. In Joltuar, open your account menu (bottom of the sidebar) and choose Integrations.
2. Find the Pipedrive card and click Connect.
3. You're sent to Pipedrive's consent screen, listing the permissions above. Review them and click Allow.
4. You're redirected back to Joltuar. The Pipedrive card now shows your company's Pipedrive domain instead of the description text — that means it's connected.

Or start from the Pipedrive Marketplace

You can also start the connection from Pipedrive's side: clicking Install now on Joltuar's Pipedrive Marketplace listing opens Joltuar's Integrations screen directly (signing you in first, if you weren't already). A workspace owner or admin then clicks Connect there to approve Pipedrive's consent screen, same as above. This works because the listing's "Installation URL" points at https://app.joltuar.com/?screen=integrations&connect=pipedrive.

What data flows, and in which direction

Pipedrive → Joltuar (read): deal titles, fields and custom fields, activities, pipelines/stages, and enough of a person/organization's data to match a meeting to the right deal (attendee e-mail domains, company names). Nothing here leaves Joltuar except back into your own Assistant conversation.

Joltuar → Pipedrive (write, only when you ask in chat or a workflow runs): deal notes, activities/tasks, deal custom-field values, and — if your workflow enables it — a deal's value or its pipeline label/stage-related field. Notes and tasks are attributed to the deal's owner in Pipedrive when that can be resolved; field/value updates always show as authored by whoever connected the integration, because Pipedrive has no way to attribute those any other way.

If your workspace uses Workflows with a Pipedrive trigger (for example, a workflow that fires whenever a call finishes), Joltuar also registers a webhook subscription in your Pipedrive account the first time that workflow is turned on, so it can react to deal changes. This needs the webhooks:full permission below; if it's missing, reconnect Pipedrive to grant it.

Permissions we request and why

Scope	What it's for
base	Basic identity of the connection — which Pipedrive company you connected.
deals:full	Read deals and their custom fields, and write notes/updates to the deal you asked Joltuar to update.
contacts:read	Read persons and organizations, used to match a meeting's attendees to the right deal.
activities:full	Read a deal's existing activities, and create/update the follow-up tasks the automation or chat creates.
search:read	Search deals, persons and organizations by name/domain when matching a meeting to a deal.
users:read	Resolve a deal's owner, so notes and tasks can be attributed to them instead of the connecting admin.
webhooks:full	Register a webhook so a Workflow with a Pipedrive trigger (e.g. "when a deal changes") can react to it. Only used if your workspace has such a workflow.

Disconnect

From Joltuar: Integrations → Pipedrive → Disconnect (workspace owner/admin only). This immediately stops all reads and writes and deletes the stored connection from Joltuar; Joltuar also asks Pipedrive to revoke the token.

From Pipedrive: open Pipedrive → Marketplace → Manage installed apps, find Joltuar, and remove it. Uninstalling from Pipedrive's side automatically notifies Joltuar and removes the connection on our end too — you don't need to also click Disconnect in Joltuar afterwards.

Troubleshooting

Symptom	What's happening	What to do
The Pipedrive card isn't on the Integrations screen	Your workspace may not have this integration turned on yet	Contact support@joltuar.app
"This Pipedrive connection is missing the webhooks scope"	The connection was made before webhooks:full was requested, or the scope was removed on Pipedrive's side	Disconnect and reconnect Pipedrive from the Integrations screen
A chat write says "not connected" or asks you to reconnect	Pipedrive's refresh token was revoked (uninstalled, or the connecting user's access was removed in Pipedrive)	Reconnect from the Integrations screen
A field update in chat says "unknown field"	The field name doesn't exist (or was renamed/deleted) in your Pipedrive account's custom-field catalog	Check the field still exists in Pipedrive, then ask again
Deals I know about don't show up in a search	The connecting Pipedrive user can't see them	Reconnect using a Pipedrive user with visibility into those deals
Post-call updates aren't happening	Post-call automation runs from a Workflow, not from the Integrations card	Set up a Workflow with a meeting.processed trigger calling the Pipedrive update step — see the Workflows screen, or contact support@joltuar.app if you don't see it

Need help?

Email support@joltuar.app. For how Joltuar handles your data, see our Privacy Policy and Terms of Service.