Skip to main content

  • Ask questions and post tips about Filtering.
  • Click Follow to always stay posted ↗️
  • Learn all about any of Pipedrive’s features from our Knowledge Base tutorials in your preferred language and our Academy video courses. Simply search for your topic! 🔍
9 questions
179 posts

Sign up for free today or log in now to follow this topic, join the discussion, and always stay updated.

🎥 How to customize your notifications, follow topics and join channels in the Community.

How to list PEOPLE associated with an Organizational search ...

We do not enter email addresses for organizations, only people.   How can I do an "organization" type search or filter in PD and have it show me PEOPLE associated with those organizations?

Example:  We have a custom field for ORGANIZATIONS that denotes them as a new account.  I would like to send a bulk email to those PEOPLE.  How can i combine search criteria for ORGANIZATIONS to produce a list of people to include in my "campaign" ...?      Thanks in advance for any suggestions!  :) 

New: Leads Inbox update - Custom columns and filters 📊 🔎



We’ve just released custom columns and custom filters support in the Leads Inbox. Users are now able to:

  • edit the existing or create new filters in Leads Inbox
  • modify and re-order the columns in Leads Inbox


Gradually rolling out to all users in the coming weeks


🔔  Follow What’s New? to get notified about all new product releases 🔔

Filters does not work as supposed to

Example 1: we have deals in a stage of a pipeline. The deals are with organizations. Each organization has one or more people associated with it. We can not filter and get the list of all people from that organizations which are in certain stage of a given pipeline. We need that list to send bulk emails to them. Pipedrive does not support that! (or that is a bug)

Example 2: we have organizations. We have added custom field for the organization. We need to get the list of all people associated with organizations having specific custom field value. We... (More)

Ted YounCommunity Driver
Software Engineer at Hashsnap

Suggestion: Korean localization based on Subject-Object-Verb structure


Although Pipedrive supports Korean language, many potential users are complaining about many missing details. One of them is about the filter definition that only supports the Subject-Verb-Object structure.

In English version, defining a filter is intuitive because the UI supports the Subject-Verb-Object structure such as 'Deal status is open'.

In Korean version, however, defining a filter is counterintuitive because the UI requires the condition statement to be in the form of Subject-Verb-Object, although Korean languge has the form of Subject-Object-Verb.

I understand that this problem can be fixed only after Pipedrive conducts thorough investigation to support... (More)