1. Integrations
  2. Pipedrive

Pipedrive integration: visitors from the chat are saved in Pipedrive as persons and leads

Agenola's Pipedrive integration connects your agent to your Pipedrive CRM: the agent finds the visitor in your persons by email, adds them as a new person if they aren't there, opens their request as a lead, leaves their answers as a note and creates a follow-up activity for your team. It can also read and update deals. You connect it in one click with your Pipedrive account.

How it works

Pipedrive steps are added to a flow or turned on in the Integrations tab of the AI Assistant step. In every step, a person is found by ID or email address; the email the visitor gives is enough.

In person, organization and deal steps, fields your team added in Pipedrive go in the "Custom fields" field, by the name they have in Pipedrive; for dropdowns, the option's name is enough.

Notes and activities are linked to the person, organization, deal or lead you name and show in the record's history in Pipedrive. What the visitor writes is saved as plain text.

  • If a person with that email already exists, "Create person" goes to its error branch; on that branch you can use "Update person" with the same email. That way the same visitor isn't added twice.
  • A lead shows up in Pipedrive's Leads Inbox; your team can turn it into a deal from there.
  • You can write a deal's stage by its name; choosing a stage of another pipeline moves the deal there.
  • Steps work with the connecting person's access in Pipedrive and see only the records that person can see.
  • The step that deletes an activity doesn't run until the confirmation box on the step is ticked.

What it does

This list is generated from the same source as the Pipedrive page in the dashboard: if it isn't listed here, we don't do it with Pipedrive. Flow steps live in the flow editor under Add step → Integrations → Pipedrive.

PersonAction · Flow step7

  • Get person

    Reads a person's name, email, phone, organization and Pipedrive page. The person is found by ID or email address.

  • Create person

    Adds a new person. If a person with this email already exists, the step fails with “Record already exists”; use Update person with the email instead.

  • Update person

    Changes the fields you fill in and leaves the others as they are. A new email or phone becomes the primary one; the old ones stay on the person. The person is found by ID or email address.

  • Search persons

    Searches names, emails, phone numbers and notes, and returns the matching persons as a list, best match first. With no search text, it returns the newest persons.

  • Get person's deals

    Returns the deals linked to a person as a list, newest first; optionally only those with a given status.

  • Get person's notes

    Returns the notes on a person as a list, newest first.

  • Get person's activities

    Returns a person's activities as a list, newest first; optionally only the open or the done ones.

OrganizationAction · Flow step3

  • Get organization

    Reads an organization's name, website, address and Pipedrive page.

  • Create organization

    Adds a new organization.

  • Search organizations

    Searches names, addresses and notes, and returns the matching organizations as a list, best match first. With no search text, it returns the newest organizations.

DealAction · Flow step4

  • Get deal

    Reads a deal's title, value, stage, status, expected close date and Pipedrive page.

  • Get deal with custom fields

    Reads the deal, and as a list the values of the fields your team added in Pipedrive.

  • Update deal

    Changes the fields you fill in and leaves the others as they are. Choosing a stage of another pipeline moves the deal there.

  • Search deals

    Searches deal titles and notes, and returns the matching deals as a list, best match first. With no search text, it returns the newest deals.

LeadAction · Flow step4

  • Create lead

    Adds a new lead to Pipedrive's Leads Inbox; it has to be linked to a person or an organization. If you enter a value and leave the currency empty, the connecting person's currency in Pipedrive is used.

  • Get lead

    Reads a lead's title, value, label, linked person and Pipedrive page.

  • Update lead

    Changes the fields you fill in and leaves the others as they are.

  • Search leads

    Searches titles and notes, and returns the matching leads as a list, best match first. With no search text, it returns the newest leads.

NoteAction · Flow step3

  • Create note

    Adds a note to the person, organization, deal or lead you name; it shows in the record's history in Pipedrive. At least one record is needed.

  • Get note

    Reads a note's text and date.

  • Get notes

    Returns the notes on the record you name as a list, newest first. With no record, it returns the newest notes.

ActivityAction · Flow step5

  • Create activity

    Creates an activity for your team, such as a call, meeting or task; optionally assigns it to someone and links it to a person, organization, deal or lead. If the date is empty, Pipedrive sets the activity for today; if no type is chosen, it uses the first activity type.

  • Get activity

    Reads an activity's subject, type, date, note and whether it is done.

  • Update activity

    Changes the fields you fill in and leaves the others as they are. Choose the status “Done” to complete the activity.

  • Delete activity

    Deletes the activity; Pipedrive removes it for good after 30 days.

  • Get activities

    Returns activities as a list, newest first; you can filter by status, owner and linked record.

Example conversations

A new visitor is opened as a lead

Visitor: I'd like a price for licenses for our team. I'm Deniz, and my email is deniz@example.com.

Agent: Thanks, Deniz. How many people are on the team?

Visitor: 25.

Agent: Noted; our sales team will get in touch about a quote for 25 people.

Behind the scenes: "Create person" adds Deniz to Pipedrive; "Create lead" opens the request in the Leads Inbox, linked to Deniz. "Create note" writes the team size on the record, and "Create activity" opens a call activity for the sales team.

A returning customer is recognized

Visitor: I got a quote last week. What's the status? My email is can@example.com.

Agent: Your quote is at the "Proposal made" stage; the value is $12,000 and the expected close date is November 30. If you have questions, I can pass them to the team.

Behind the scenes: "Get person's deals" finds the person by email and returns their deals; the agent reads the deal's stage, value and expected close date.

A note and an activity are left at the end of the conversation

Visitor: Can we move the demo from Tuesday to Thursday? My email is ece@example.com.

Agent: Of course. I've passed your request for Thursday to our team; they'll get back to you to confirm.

Behind the scenes: "Create note" leaves the visitor's request as a note on the person found by email; "Create activity" opens an activity for Thursday for the team.

Setup

Our app on the Pipedrive side is currently going through approval. Until it is approved the connection is not open to everyone; once approved, the steps on this page apply as written.

  1. 1In Agenola, go to Integrations → Pipedrive, press "Connect to Pipedrive" and give access with your Pipedrive account.
  2. 2In the agent editor, add the Pipedrive steps; in the person field, write the variable that holds the visitor's email.
  3. 3In lead, note and activity steps, choose which person the record is linked to and who it's assigned to.

Detailed setup: How do I connect Pipedrive?

Permissions and where your data goes

  • Sent to Pipedrive: the fields you fill in on the step (such as the visitor's name, email and phone), note and activity text, and the records to link.
  • Read from Pipedrive: the person, organization, deal, lead, note and activity details a step asks for; users, pipelines and stages, activity types, lead labels and field definitions for the step's lists.
  • Permissions requested: reading and writing persons, organizations, deals, leads and activities; reading users; searching. Email, product and admin settings permissions aren't requested.
  • Steps work with the connecting person's access in Pipedrive. Connection details are stored encrypted on the server. Only the workspace owner and admins can connect or remove it; when you remove it, Agenola's access in Pipedrive is removed too, and your records stay in Pipedrive.

Related integrations

See all integrations

Frequently asked questions

Can a visitor see another person's Pipedrive record?

The visitor's identity isn't verified: someone who types another person's email can see the details the step reads. That's why you choose which of the step's outputs are shown to the visitor; show details such as a phone number or a deal value only when needed.

Is the same person added twice?

No. Although Pipedrive allows a second person with the same email, "Create person" looks the email up first; if the person exists, it goes to the error branch and you can update the existing person instead.

Can I use my own Pipedrive fields?

Yes. In the "Custom fields" field you write the field's name as shown in Pipedrive and its value; for dropdowns, the option's name is enough. "Get deal with custom fields" reads the values of these fields.

Which records do the steps see?

The records the connecting person can see in Pipedrive: Pipedrive's visibility settings apply to the steps too. Connect with a user who has broad access to your records.

Try the Pipedrive connection on your own account

Log inGet started

Agenola and our partners use cookies to improve the site and show you relevant ads. We count which of our ads bring visitors without using your name or email; anything more only happens if you allow it. Privacy Policy(opens in a new tab)