Connect Pipedrive to Qoren

Connect Pipedrive once with an API token and your agents can wake the moment a deal is added, moves stage, is won or lost, or a person, organization, activity or note appears. Qoren sets up the Pipedrive webhooks itself, so there is no URL or secret to copy.

The same connection lets the agents you choose look things up in Pipedrive and, if you allow it, add notes, schedule activities, create people and deals and move deals between stages. Closing a deal as won or lost always waits for your approval. How connections, access and approvals fit together is in connect your tools with Integrations.

Before you start#

• You are the owner of your Qoren organization. Only the owner connects tools, gives agents access and sends connect links.
• Integrations is on for your account. It is rolling out: if the sidebar has no Integrations under Capabilities, it is not on your account yet.
• You can sign in to Pipedrive as the user whose token Qoren will hold. Pick that user with care (next section).

Pick the right Pipedrive user#

A Pipedrive API token cannot be limited: it can do everything its user can do, and a webhook only reports what that user is allowed to see. So the user decides both what agents could reach and what triggers notice.

• An admin sees every deal, person and activity, so triggers miss nothing.
• A dedicated user for Qoren is the safer choice when you can: give it access to the pipelines and records your agents should know about, and nothing else.
• A regular user works, but triggers only see the deals, people and activities that user can see. Qoren says so when it checks the token.

Whichever you pick, Qoren keeps agents to the level you grant: a read only connection never writes, even though the token itself could.

Make the key#

1. Sign in to Pipedrive as the user you picked.
2. Open your profile menu, choose Personal preferences, then the API tab (open it in Pipedrive).
3. Copy your personal API token. Pipedrive gives each user one active token at a time.

Paste it only into Qoren. Never send it by email or chat.

Connect it in Qoren#

1. In the sidebar, under Capabilities, click Integrations.
2. Under Add a tool, click Pipedrive. The Connect Pipedrive dialog shows the same steps as above, and a warning that Pipedrive keys cannot be limited.
3. If you run an agency, choose the client in Which client is this for?, or leave No client (your own account). A client's connection can only be used by that client's agents.
4. Paste the token into API token.
5. Click Check key. Under Key checked you see the Pipedrive company (Account:), Can read, Can write and how many webhooks this user has left, such as Can add webhooks (38 of 40 left).
6. Under What agents may do, choose Read only or Read and write.
7. Click Connect.

The screens are shown step by step in connect a tool.

What Qoren checks#

When you click Check key, and again when you click Connect, Qoren asks Pipedrive:

• Who the token belongs to. It reads the user and the company. The company name (or its Pipedrive address) becomes the connection's label. A token Pipedrive refuses is not saved.
• Whether the user is an admin. If not, the check notes that triggers only see what this user can see.
• Whether the user may use the API at all. A user whose permission set does not allow API access is refused, with the reason.
• How many webhooks the user already has. Pipedrive allows 40 per user; the check counts the active ones this user owns.

The token is encrypted as soon as it arrives. After that the console only ever shows its last four characters.

Give an agent access#

A new connection is used by no agent until you give one access. Open the connection under Connected, choose an agent (or all agents) in Give access to…, pick Read only or Read and write, and click Give access. You can also narrow which tools each agent may use and how many records it may read an hour. See give an agent access.

Events#

These are the Pipedrive events an agent can wake on. Create a trigger from them on the agent's Triggers tab, as described in wake an agent from a connected tool.

What the agent receives. The event name, what kind of record it is, its id, when it happened and who changed it, then the record itself with only the fields an agent needs (for a deal: title, value, currency, status, stage, pipeline, owner, person, organization, dates and the like), plus what the fields were before the change. Long text is shortened. If a delivery arrives without the record, Qoren reads it from Pipedrive first.

How the webhook is set up. Qoren registers one Pipedrive webhook per kind of change it needs (for example one for deal changes), and triggers that need the same change share it. Each webhook is named after what it listens for, such as "Qoren deal change", and checks every delivery with a username and password only Qoren and Pipedrive know, on an address unique to your connection. Deal won and Deal lost are deal changes whose status turned to won or lost.

Before adding a webhook, Qoren counts the user's webhooks against Pipedrive's 40. If the user is full, the trigger is not created and you are told which webhooks to clean up. Qoren never removes a webhook it did not create.

Tools agents can use#

An agent with access calls these through Qoren. It never sees the token.

Searches return at most 20 results at a time. There is no tool that deletes, merges, exports or bulk edits anything. Closing a deal as won or lost can set off your own Pipedrive automations, so it always waits on the Approvals page, whatever the agent's settings. The other writes follow the agent's autonomy and need a Read and write grant. More on these limits in how Qoren keeps connected tools safe.

Limits and gotchas#

• The token carries its user's full rights. Qoren's tools are the only thing holding an agent to Read only. Use a dedicated user if you can.
• Triggers only see what the user sees. A regular user's token misses deals in pipelines that user cannot open.
• 40 webhooks per Pipedrive user. Each kind of change Qoren listens for uses one.
• Pipedrive removes failing webhooks. It deletes a webhook after three days with no successful delivery, and bans one for 30 minutes once it has failed 10 times; events in that window are lost. Qoren's daily check notices a webhook that was deleted, switched off or changed and sets it up again with the same address.
• Pipedrive meters API use per company per day. When the day's budget is spent, Pipedrive refuses calls until it resets, and Qoren says so.
• One token per user. If someone generates a new token for that user in Pipedrive, the old one stops working and the connection needs the new one.

Troubleshooting#

• "Pipedrive did not accept this key." Copy the whole token again from Personal preferences, API. If someone generated a new token since, use the new one.
• "This Pipedrive user is not allowed to use the API." Ask a Pipedrive admin to allow API access for that user, or use another user.
• "This Pipedrive user already has 40 webhooks." Delete a webhook you no longer use in Pipedrive (Tools and apps, Webhooks), then create the trigger again.
• "This Pipedrive account is already connected here." Open the existing connection and use Replace key instead.
• The connection says Needs a new key. Pipedrive stopped accepting the token, usually because a new one was generated or the user was removed. Its triggers are paused. Click Replace key and paste a working token; the triggers come back by themselves. See when a connected tool stops working.
• A trigger never fires. Check that the token's user can see the record, and look at the trigger's deliveries on the agent's Triggers tab.

Disconnect and delete the token#

1. On the Integrations page, open the Pipedrive connection under Connected.
2. Click Disconnect. The Disconnect Pipedrive? dialog says what happens. Click Disconnect to go ahead, or Keep it.

Qoren deletes the stored token, removes the webhooks it created in Pipedrive, removes every agent's access and pauses the triggers that used the connection.

Qoren cannot revoke a Pipedrive token, so do it in Pipedrive too: open Personal preferences, API and generate a new token. The old token stops working at once.