Skip to the operations

CRM

Pipedrive in a decision flow.

6 Pipedrive operations a decision flow can call directly, with the credentials your own contract issued. The response is data the rest of the flow reads, branches on, and keeps in the trace.

Category
CRM
Type
Integration
Authentication
API key
Test environment
Production host only

Who they are

Sales CRM built around the pipeline rather than the contact record.

Pipedrive organises a sales team's work as deals moving through stages, with activities attached to each one. It sells to small and mid-sized teams that found a larger CRM heavier than the job needed. Its API is straightforward and every object carries custom fields, which is what makes it usable as a system of record rather than only a sales tool.

What a flow can call

6 operations, each one a step you can place on the canvas.

  1. PUT/deals/$data.pipedrive_deal_id

    Write the outcome to a deal

    The main reason to have this connection: push the decision onto the deal the sales team is looking at.

  2. GET/deals/$data.pipedrive_deal_id

    Read a deal

    The deal's current state, including its custom fields.

  3. POST/notes

    Add a note to a deal

    Attaches the reasoning to the deal. Better than overwriting a field for anything a person will read: the note keeps the wording the decision produced, timestamped, next to everything else the team has said about the applicant.

  4. GET/persons/search?term=$data.applicant_email&fields=email&exact_match=true

    Find a person

    Looks a contact up by email before creating one.

  5. PUT/persons/$data.pipedrive_person_id

    Update a person

    Writes back to the contact rather than the deal — the right place for something durable about the applicant, such as a verified phone number the decision confirmed, as against the outcome of one application.

  6. GET/users/me

    Verify the token

    Returns the user the token belongs to and the company it sits in.

Where it sits in the decision

CRM calls have a natural place in a flow.

Writing the outcome back closes the loop with the commercial team, so the record they work from carries the same verdict the customer received rather than a copy that drifts.

Whatever Pipedrive returns is part of the run, so it is part of the record. When someone asks months later why an applicant was declined, the answer cites what came back at the time rather than re-fetching from a service whose answer has since changed.

  • 01Add Pipedrive as a connection authenticating with an API key.
  • 02Pipedrive has one host for both environments, so guard test runs with your own credentials and limits.
  • 03Place a Connection node and pick an operation — “Write the outcome to a deal” is usually the first one a flow needs.
  • 04Map the response into the fields your rules read, then test the whole path before it carries live traffic.

Common questions

Using Pipedrive in a flow.

How do I connect Pipedrive to a decision flow?

Add Pipedrive as a connection in your workspace authenticating with an API key, with the credentials your own contract issued — ArboRule calls the provider as you, and never holds a contract on your behalf. Once the connection exists, any flow in the workspace can place a Connection node and choose one of its operations. The credentials live on the connection, not in the flow, so a policy owner can use Pipedrive in a decision without ever seeing the secret.

Can I test Pipedrive without touching production?

Pipedrive exposes one host for both environments, so there is no separate sandbox to point at. Test runs still execute in Sandbox and are recorded separately in decision history, but the call goes to the same place as production — so guard it with your own test credentials, rate limits, or data.

What can a flow call on Pipedrive?

6 operations, including “Write the outcome to a deal”, “Read a deal”, “Add a note to a deal”. Each one is a step you place on the canvas and map into the fields your rules read, and most flows start with “Write the outcome to a deal”. The list comes from the same manifest the engine uses to make the call, so this page cannot describe an operation the product does not have.

Where in a decision should Pipedrive be called?

Writing the outcome back closes the loop with the commercial team, so the record they work from carries the same verdict the customer received rather than a copy that drifts.

Also in CRM

Ready when you are

Wire Pipedrive into a real decision.

Build the flow in Sandbox, connect your account, and watch the decision pull what it needs before it answers.

Read the docs