Pipedrive Resellers

Connect AI agents to the Pipedrive Resellers partner API. Agents provision client Pipedrive accounts, manage subscriptions, and add or remove users on behalf of the customer.

11 actions API key available

Platform Documentation ↗

A deal reaches closed won in the reseller's own sales system, because this partner API publishes no events and this connector ships no triggers

Get Available Plans and Addons returns the valid plan identifiers and addon codes for the client's ISO alpha-2 country

The agent maps the signed order onto a plan identifier, a seat count, and addon codes that exist in that country

List Subscriptions confirms this client does not already hold a company under a slightly different name

The agent assembles the subscription payload with language, user self management mode, and the first user's email

The partner operations owner receives the plan, the seat count, the addons, and the recurring figure those imply

The owner confirms the seat count, and Create Subscription provisions the billable company only on that answer

What This Integration Enables

This is not the Pipedrive CRM connector, and the difference matters more than the shared brand name suggests. The Resellers API is Pipedrive's partner-only provisioning surface: it creates and manages client company subscriptions on behalf of an approved reseller, using a credential issued out of band under a partner agreement rather than a self-service key. Everything it touches belongs to somebody else's company, and everything it creates generates a billing obligation against the partner. Those two facts should shape every flow built on it.

The surface is small and coherent. Get Available Plans and Addons returns the valid plan identifiers and addon codes, queried by ISO alpha-2 country for a new account or by company identifier for an existing one. Create Subscription provisions the client company and returns a company identifier that becomes the handle for everything afterwards: Get Subscription, Update Subscription, Suspend Subscription, Restore Subscription, and every user operation on that account. Add User to Account, Update Account User, and Remove User from Account manage the people on it, and Get User API Token retrieves a user's Pipedrive public API token.

Two semantics are worth internalising because they contradict reasonable assumptions. Billing runs on plan price and seat count, and seat count can be set higher than the number of users actually on the account, so seats are the commercial variable and users are not. And users are global to Pipedrive rather than local to the account. Adding a user matches on email and links an existing Pipedrive user rather than creating a duplicate. Removing a user unlinks them from this account without deleting the person, so the same user can later be added elsewhere. Suspend Subscription is the reversible lever, restored through Restore Subscription, and while a company is suspended it is unusable and generates no billing obligation.

There are no triggers. The Resellers API publishes no event or webhook surface, so a flow is driven by events in the reseller's own systems, meaning a deal closing, a payment failing, a renewal date arriving, or a scheduled reconciliation sweep across List Subscriptions.

Without FlowRunner

Provisioning is a checklist A person logs into the partner portal and retypes what the contract already said

Plan and seat errors surface at invoice The mismatch between what was sold and what was provisioned is found a month later

Account changes are untracked Users are added and removed on client accounts with no record outside the portal

With FlowRunner

Provisioning follows the signed order Plan, seats, and addons are read from the deal record rather than remembered

Seat count is confirmed before it bills The number that drives the invoice is shown to a person before the account exists

Every account change is a logged step Adds, removals, suspensions, and restores run as workflow steps with an audit trail

Use Case Scenarios

The contract provisions the account, not a person retyping it

A partner closes a deal in their own CRM. The flow reads the signed order and calls Get Available Plans and Addons for the client's country, which returns the plan identifiers and addon codes actually valid there rather than the ones from the last deal in a different market. The agent maps the order onto a plan and a seat count, checks List Subscriptions for a near-duplicate company name that would indicate this client already exists, and assembles the payload including the account language and the user self management mode the partner wants to grant. Then it stops for a person. On approval, Create Subscription provisions the company, the returned company identifier is written back onto the deal record and into a provisioned-accounts tracker in Google Sheets, and the partner operations channel in Slack gets the company name, plan, and seat count.

Payment lapses, access pauses, payment clears, access returns

Suspension is the partner's most useful lever and the easiest one to apply carelessly. A flow watches invoice status in the billing system. When an invoice passes its grace period, the agent gathers the account context with Get Subscription, posts the client name, the outstanding amount, and the number of users who will lose access, and waits. A person decides, because suspending a company makes it unusable for everyone in it and that is a relationship decision rather than an accounting one. When payment clears, the reverse runs without a gate: Restore Subscription is applied automatically, because restoring access to a paying customer as fast as possible is never the wrong call. Gating one direction and not the other is a deliberate asymmetry rather than an oversight.

Seat count that matches reality instead of last year

A monthly reconciliation flow walks List Subscriptions across the partner's book, calls Get Subscription on each, and compares the billed seat count against the actual users on the account. Because seats can legitimately exceed users, a gap is not automatically an error, it is a question: an account with 40 seats and 12 users is either a growth plan or a mistake nobody has looked at since onboarding. The agent builds the whole list, splits it into accounts trending up and accounts paying for air, and posts it to the account managers rather than changing anything. Update Subscription runs only where a human has already had the conversation with the client.

Human-in-Loop Highlight

Create Subscription is where an agent should stop, and the reason is a specific asymmetry in how this API bills. Seat count, not user count, is the commercial variable. The API happily accepts a seat count higher than the number of users on the account, because that is a legitimate and common way to buy Pipedrive, which means there is no validation anywhere in the request that would catch a seat number that is simply wrong. A transposed figure, a plan tier read from the wrong field, or an addon code carried over from a previous deal all produce a perfectly successful call and a recurring charge against the partner's agreement rather than against the client. Nothing in this connector unwinds that: Suspend Subscription pauses billing but leaves a company that should never have existed, and Update Subscription changes the plan going forward rather than undoing what already billed. So the agent does the work that is genuinely mechanical, meaning resolving the country's valid plans and addon codes, checking for a duplicate company, and assembling the payload, and then hands over the one number that carries money: "Provisioning Northgate Legal on Professional, 25 seats, 2 addons, Ireland. Their signed order says 18 users. Seats are what bills. Confirm 25 or correct it." A partner operations owner answers, and Create Subscription runs on that answer. This is human-in-the-loop sitting exactly where automation stops being able to check itself: the agent can validate that a plan identifier exists, but only a person can confirm that the number is the one that was sold.

A second caution belongs on Get User API Token rather than a second gate. That action returns a user's Pipedrive public API token, a live secret that grants access to that account's entire CRM through a different API. Retrieving it is legitimate and often necessary for downstream automation, but it should be treated as a credential handling step with the care that implies, not as an ordinary read.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

11 actions

Subscriptions

List Subscriptions Lists the client company subscriptions under the reseller agreement. The starting point for reconciliation sweeps and the duplicate check before provisioning a new account.
Get Subscription Retrieves one client company subscription by company identifier, including its plan and seat count. The company identifier returned by Create Subscription is the handle for this and every other account-scoped action.
Create Subscription Provisions a new client company with a plan and a seat count, returning the company identifier. Billing runs on plan price and seat count, and seats may exceed actual users, which makes this the action that commits money on the partner's behalf.
Update Subscription Changes an existing client company's plan and seat count. Applies going forward rather than retroactively, so it corrects the next charge and not the last one.
Suspend Subscription Suspends a client company. While suspended the company is unusable by everyone on it and generates no billing obligations. Reversible, but visible to the customer the moment it happens.
Restore Subscription Returns a suspended company to normal service. The counterpart to Suspend, and the one action in this connector that is almost always safe to run without asking.

Plans and Pricing

Get Available Plans and Addons Returns the plan identifiers and addon codes available, queried by ISO alpha-2 country for a new account or by company identifier for an existing one. Call it before pricing or provisioning anything, because valid plans and addons differ by country.

Account Users

Add User to Account Adds a user to a client company, matching on email address. Pipedrive users are global, so this links an existing user rather than creating a duplicate person.
Update Account User Updates a user's settings on a client company, including the user self management mode that decides whether the customer can add users or seats themselves: Disabled for no changes, Partial for adds and removals within the seat limit, Full for adding users and seats freely without seat removal.
Remove User from Account Unlinks a user from a client company. The user is not deleted and can be added to another account later, which makes this less destructive than it sounds but no less noticeable to the person who loses access.
Get User API Token Retrieves a user's Pipedrive public API token for use against the main Pipedrive CRM API on that account's behalf. This returns a live secret with broad access to the client's data, so handle the result as a credential rather than as a field.

Frequently Asked Questions

What can FlowRunner do with Pipedrive Resellers?

FlowRunner agents can run List Subscriptions, Get Subscription, and Get Available Plans and Addons in Pipedrive Resellers, plus 8 more actions.

Does connecting Pipedrive Resellers to FlowRunner require OAuth?

No. Pipedrive Resellers connects to FlowRunner with an API key, no OAuth flow required.

Can Pipedrive Resellers trigger a FlowRunner workflow automatically?

Pipedrive Resellers doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Pipedrive Resellers

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us