Link People to Organizations in Pipedrive

In Insycle, navigate to the RevOps Acceleration > Associate app, select your Pipedrive database, and the People record type in the top menu.

Explore the templates for an existing solution that may be close to what you need. The pre-built template, Link People to Organizations could give you a good starting point.

Under Step 1, select Fields you want to look at and Conditions you want the values to meet to determine whether to include or exclude an item from this task. With this filter, you're telling Insycle what records you would like to update. 

When you click Search, Insycle will list matching records in the Record Viewer at the bottom of the page. You can modify the columns using the Layout tab under Step 1.

Under Step 2, define the rules for bulk matching the two item types and making the appropriate relationships.

In the first row:

1. Action tells Insycle what to do to the records surfaced in Step 1. You can Add or Remove a link between items. 

2. Association specifies the type of record you want to create the relationship with. In the example above, People will be linked to Organizations.

3. Click the Organizations Filter button to limit the pool of target organization items to those that are a good fit for this task. In this example, Insycle will only consider organizations for linking if they have a domain value in the database.

4. Click the Selection button to define rules for picking the organization if there are multiple matches found.

In the second row:

5. Select the People Field you want to try and match with the organization records. In the example above, the Email Domain value from the person record will be used.

6. Select the Organizations Field with the value that should match the people field. In this example, the Domain field from the organization records will be analyzed for a match.

7. Comparison Rule tells Insycle whether the values between the person and organization items must be an Exact Match or Similar Match. In most cases, you'd select Exact Match, but you can learn more about these Comparison Rules in the Advanced How-Tos below.

8. In the Ignored field, you can specify parts of a field value to ignore, such as specific text, whitespace, or characters. In the dropdown, check the box for the values you'd like to ignore. In the above scenario, the Ignored rule tells Insycle to ignore any top-level domains that may appear in the Email Domain or Domain fields such as ".com," ".co.uk," or ".edu."

9. Match Parts tells Insycle whether to match the entire field or just part of it. 

If your team is capturing valuable detail in the CRM, you can automatically copy info into related records, avoiding errors and saving time.

After setting the association rules in Step 2, you can create rules to copy values between the records. If one record type consistently has values that would be helpful in the linked record, you can execute that copy in bulk.

Under Step 3, select the field from the source record type (in this example, people), and the relevant field on the target records (organizations). You can choose to copy values from the source record to the target, or target record to the source.

The Copy Rule gives you three options:

• Only when [the record you're linking to] field is empty
• Only when [the record you're linking from] field is not empty
• Always copy

Preview Changes in a CSV Report

Now with the filters and linking actions in place, you can preview the changes you are making to your data. That way, you can verify the relationships will be created as expected when made in your live database.

First, under Step 4, click the Review button.

In the Bulk Associate popup, select Preview and click Next.

On the Notify tab, add any recipients who should receive the CSV (and hit Enter after each address). You can add colleagues and additional context here.

On the When tab, click the Run Now tab and select which records to apply the change to (in most cases, this will be All), then click the Run Now button.

Open the CSV file from your email in a spreadsheet application and review the columns. 

For each person item, Insycle looked at the Email Domain then looked through organization items for a match in the Domain field. You can see these values side-by-side in the CSV.

An "Added" Result indicates a match was found, and the relationship will be added when the update is applied to Salesforce.

If there is an issue, the Message field will give you details so you can troubleshoot. See the Troubleshooting section below for more details.

Apply Changes to Pipedrive

If everything in your CSV preview looks correct, return to Insycle and apply the changes to the live Pipedrive data.

Under Step 4, click the Review button. This time select Update mode. 

On the When tab, click Run Now and select which records to apply the change to (you could do All, but if you have a large number of records, you may just want to do a chunk for your preview), then click the Run Now button.

Save Templates and Setup Automation to Maintain Formatting

After you've seen the results in Pipedrive and you are satisfied with how the operation runs, you can save all of the configurations as a template and set up automation so this linking operation runs on a set schedule. 

By automating with a template, you'll save time and ensure that your fields are consistently linked on an ongoing basis.

Return to the Template menu at the top of the page and click Copy to save your configurations as a new version of whatever template you started with. Then click the pencil to edit your new template name.

Under Step 4, click the Review button, and select Update mode.

On the Notify tab, select the send option appropriate for your automation: Always send, Send when errors, or Do not email.

Add any additional recipients who should receive the CSV each time the automation runs. You can also provide additional context in the message subject or body.

On the When tab, select Automate, and configure the frequency you'd like the template to run. When finished, click Schedule.

In Step 2, the Comparison Rule defines what kind of likeness to look for when deciding if field values should be considered a match.

It's a good idea to start with Exact Match for the straightforward matches, then use Similar Match to look for edge cases.

Exact Match looks for values that match exactly, with no differences from one record to the next. Any unique identifying fields should use Exact Match.

Similar Match looks for values that may be close but with a one-character difference (like a typo, extra character, or missing character) and broadens the search. This search behaves like when Google shows results for a slightly different term, or says “Did you mean...”

For example, if an organization Name of, “Acme” is found, it could include records with the organization Name values, “Akme," "acm," or "Acma,” as matches.

Be careful if using Similar Match, as the looser criteria can incorrectly identify records as matches.

 If using ID fields to match, note that they will only work with Exact Match, not Similar Match.

If no matching organization is found, you can choose to automatically create a new one based on what is in the source record.

Under Step 2 of the Associate app, check the Create new [record] when no matching is found box to enable, then select the field to use for naming the new record.

When using the Associate app, you can opt to be alerted when records aren’t matched. This may be helpful if you want to investigate and address any records where a relationship has not been created.

Under Step 2 check the Count unmatched records as Failed box.

Then in the Step 4 popup on the Notify tab, you can select the email delivery option “Always send” or “Send when errors.”

When checked, any record where there is no match to create the association will be counted as “Failed.” This will be reflected by a “with Failures” suffix on the report email subject line…

…and a "Failed" Result and "No matching record found (use 'Grid Edit' to troubleshoot)" Message in the CSV report.

When you save this associate configuration as a template and set up automation, the report emails will let you know when a relationship has not been created for a record so you can address it as needed.

A "Failed" Result with the Message "Multiple target matches (x)..." or "Multiple source matches..." occurs when multiple records meet your matching specifications. For example, if you were linking contacts to companies, and Insycle found ten company records with the name "Microsoft," it wouldn't know which Microsoft to establish the relationship with.

There are a few options for resolving this issue:

1. If there shouldn't be multiples of these records you should first merge duplicates before trying to create these relationships.
2. If there are supposed to be multiple similar but distinct records, you can add another matching field in Step 2 to make the criteria more specific. A record must match both field values to be considered appropriate for making the relationship.
3. Or, use the filter in Step 2 to narrow the records to be associated.
   In the filter popup, you could, for example, add the organization Name field and set the Condition, "contains" "HQ." This tells Insycle to only consider organizations for association if the Company Name value includes the term "HQ."

An "Unmodified" Result with the Message "No matching record found (use 'Grid Edit' to troubleshoot)" result occurs when there aren’t any records that meet your matching specifications.

You can examine the data in the unmatched records and troubleshoot using the Grid Edit module. Look at different fields and values to identify why your associate setup didn’t work for the record. Then, decide what match options could work or if some cleanup is needed.

Learn more about reviewing your data using the Grid Edit module.

When using the Associate app, you have the option under Step 2 to Count unmatched records as Failed. When checked, any record where there is no match to create the association will be counted as “Failed.” This will be reflected by a "Failed" Result and the Message "No matching record found (use 'Grid Edit' to troubleshoot)" in the CSV report.

You can examine the data in the unmatched records and troubleshoot using the Grid Edit module. Look at different fields and values to identify why your associate setup didn’t work for the record. Then, decide what match options could work or if some cleanup is needed.

Learn more about reviewing your data using the Grid Edit module.

You can use any field in your database to create links between records. You just need to figure out which field in each item type will have the same value. For instance, you might select "Organization" for people and "Name" for organization items. Or you could use "Email Domain" on the person, and "Website Domain" on the organization.

Commonly used fields for linking include organization names, domains, and URLs.

This error occurs when multiple records meet your matching specifications. Often, this happens when you are linking two record types together using an organization name as a match field.

For example, if you were linking people to organizations, and Insycle found ten organization items with the organization name "Microsoft," it wouldn't know which Microsoft to establish the link with.

In these situations, you may have to deduplicate the relevant items before creating the link.

Yes, you can link item types in either direction. 

Though making relationships will work in both directions, consider that people to organizations is the standard direction, and some features (such as the "Create new [record] when no matching is found" feature) are only designed to work when people are being linked to organizations. 

Yes. If no matching item is found, you can choose to automatically create a new one based on what is in the source record.

Under Step 2 of the Associate app, check the Create new [record] when no matching is found box to enable, then select the field to use for naming the new record.