noombat
Start for free

Integrations · Pipedrive

Connect Pipedrive to noombat

A one-way connection. noombat reads your CRM on a schedule and writes nothing back. One dedicated user, one API token: an admin completes the setup in about 15 minutes.

Talk to usAll integrations

Direction

noombat reads from it

Access

A dedicated integration user with the fewest write permissions Pipedrive allows, and its API token

Time

About 15 minutes

Who

A Pipedrive admin

Cost on your side

One seat at your plan's per-seat price; Pipedrive sells no free integration seats

Before you start

What to have ready.

  • An admin in your Pipedrive company account, to add a user and set its permissions.
  • A seat for the integration user, at your plan's per-seat price.
  • Pipedrive has no fully read-only user: permission sets can remove deleting, exporting and bulk editing, and creation stays on. The security questions below say what is and is not enforceable.

What noombat reads

What noombat reads from Pipedrive, and why.

Organizationsthe companies you sell to
Personsthe people at those companies
Leadsoptional, if you use the Leads inbox
Deals, pipelines and stagespipeline and revenue outcomes
Activitiescalls, meetings and tasks on your records
Notescontext logged on deals and contacts
Deal- and contact-linked emailsemails shared into the CRM; private inboxes stay private
Usersrecord owners, for attribution

Setup

4 steps, about 15 minutes.

  1. 1Create the integration user
  2. 2Permissions and visibility
  3. 3Copy the API token
  4. 4Send us the details
  1. 1

    Create the integration user about 5 minutes

    A dedicated account keeps noombat's access separate from any person: attributable on its own, unaffected by staff changes, revocable in one click. On cost: Pipedrive sells no free integration seats, so this user takes a normal paid seat on your plan.

    Company settings > Manage users > Add user

    • Name: noombat Integration
    • Email: integrations@noombat.ai. We monitor this inbox and complete the account activation ourselves.
  2. 2

    Permissions and visibility about 5 minutes

    Two dials matter: what the user may do (the permission set) and what it may see (the visibility group). We want the least doing and full seeing.

    Permission set. On plans with custom permission sets (Premium and Ultimate on current naming), create a set called noombat from the regular-user template and switch off everything Pipedrive lets you switch off:

    • Deleting deals, leads, people, organizations, products
    • Exporting data from list views
    • Bulk editing
    • Editing others' items, changing owners, editing won and lost times
    • API access stays on for this set. Without it the user has no API tab and no token.

    On plans without custom sets, assign the default regular-user set. The guarantees in the security questions below hold either way.

    Visibility. Put the user in a visibility group that sees your whole book (the default "entire company" group, if you have kept it). Whatever the integration user cannot see, noombat cannot score, and gaps here are silent, so this is worth 30 seconds of checking.

  3. 3

    Copy the API token about 2 minutes

    The token belongs to the integration user, so it must be copied while logged in as that user: from the activation we complete in step 1, or through your admin's log-in-as if your plan has it.

    Profile icon > Personal preferences > API

    Copy the personal API token. Each user has exactly one valid token; generating a new one invalidates the old at once, which is also your rotation and kill-switch story.

    Since the account email is ours, we can also do this step ourselves after activation. In that case tell us the user is created and assigned, and skip step 4.

  4. 4

    Send us the details about 2 minutes

    • Your company domain, e.g. yourco.pipedrive.com
    • The integration user's API token

    Once the details arrive we run a verification the same day, connecting as the integration user and checking that each data type returns what it should, and confirm back to you. If anything is off, the table below lists everything it could be.

Troubleshooting

What you might see, and the fix.

Every row is a failure we have met or verified. If yours is missing, send it over.

What you seeWhyFix
No API tab under Personal preferencesThe user's permission set lacks API access; admins switch API access per permission set.Company settings > Manage users > Permission sets > (the set) > enable API access, then log back in as the integration user.
401 Unauthorized on every requestThe token was regenerated (each user has exactly one valid token, so a new one kills the old), or the user was deactivated.Step 3: copy the current token from the integration user's Personal preferences > API and send it to us again.
Data arrives, and it is a fraction of your bookVisibility groups: the integration user sees only what its group may see.Step 2: put the integration user in a visibility group that sees everything, or the default entire-company group.
429 Too Many RequestsPipedrive meters API usage with a daily token budget (30,000 × plan multiplier × seats, reset every 24 hours).Usually nothing: our sync paces itself and backs off. If it persists, another integration may be consuming the budget; we look at it together.
Emails you expected are missing in noombatOnly emails linked or shared to deals and contacts are visible beyond their owner's inbox; Pipedrive keeps private mailboxes private, API included.Have reps use Smart BCC or email sync with sharing on. This mirrors what your own team can see in Pipedrive.

Security and data

The questions a security review asks.

Is this read-only?

Our sync is strictly one-way: noombat reads, and writes nothing back. On the platform side, the honest difference from HubSpot and Salesforce: Pipedrive API tokens cannot be scoped, so the token can do whatever the integration user can do, and Pipedrive has no fully read-only user, since creation rights stay on. That is why step 2 strips every write permission Pipedrive lets you strip (deleting, exporting, bulk editing, editing others' items), why we use a dedicated user so every API action is attributable to noombat alone, and why the record change history would show any modification. If platform-enforced read-only is a hard requirement for you, talk to us and we walk through it together.

What does noombat read, and why?

Organizations, persons and leads (who you sell to), deals (pipeline and revenue), and activity: calls, meetings, notes, shared emails. noombat keeps a scored mirror and connects the companies it names to the meetings and revenue that follow. History matters: the scoring learns from what already happened, which is why a forward-only feed is too little.

What does this cost on the Pipedrive side?

One seat, at your plan's per-seat price. Pipedrive sells no free integration users, so the dedicated account takes a normal paid seat. If that is a blocker, the fallback is an existing admin's token, with the trade-offs that access then rides on that person's account (it leaves when they leave and dies if their token is regenerated) and API actions show under their name. We recommend the dedicated seat.

Will this eat our API limits?

Pipedrive gives each company a daily API budget (30,000 tokens × plan multiplier × number of seats). Our sync is scheduled and incremental: after the initial history pull it reads what changed, and it backs off on 429s, so it lives well within the budget alongside your other integrations.

How do we revoke access?

At once, in two ways: regenerate the integration user's API token (each user has exactly one valid token, so a new one kills ours immediately), or deactivate the user. Both are your-side actions we cannot undo.

Is our data safe with noombat?

Your data is kept apart from every other customer's, in a schema of its own, encrypted in transit and at rest, read through connections that write nothing back, and deleted when we part ways. Data-processing terms written for a security review, for teams in the EU and in the US. We walk through them with your security team on request.

Checked against Pipedrive's own documentation. Last updated . Questions, or a policy in the way: integrations@noombat.ai

Bring your Pipedrive admin and we do it together.

A 30-minute call on your market, and the setup above on a screen share if you want it.

Talk to usSee the product

Other integrations

noombat reads from it

Attio

An access token with read scopes and an optional webhook. noombat mirrors your book and writes nothing back.

About 10 minutes · A workspace admin

noombat posts into it

Slack

The morning list and the alerts in your channels, and Snout, the analyst, on call in a DM or with an @mention.

About 5 minutes · A noombat org admin; on workspaces that restrict app installs, a Slack admin approves it

noombat posts into it

Microsoft Teams

The morning list and the alerts as cards in a Teams channel. One workflow link, no app install, no admin rights.

About 5 minutes · Any member of the team

All integrations · checked 10 October 2026