Associate HubSpot Deals with Line Items and Automatically Copy Values

Navigate to RevOps Acceleration > Associate. Select the HubSpot database and Deals record type in the top menu. Then explore the default templates for a pre-built solution. The built-in, Copy "Amount" from Deal to Line Item "Quantity" template could be a good place to start.

Each row in Step 1 is for a field you want to look at to determine whether to include or exclude a record from this association task. With this filter, you're telling Insycle what records you would like to update. 

In the below example, only deals that have an Amount value and the Pipeline value is "Sales Pipeline" will be part of this operation.

When you click Search, Insycle will list records in the Record Viewer at the bottom of the page. If you make changes to the filter, you need to click the Search button again to refresh the viewer.

Under Step 2, define the rules for bulk matching the two record types to create the relationship:

1. Action tells Insycle what to do to records surfaced in Step 1. You can Add associations or use the Replace action to remove existing associations and create new ones in one step.
2. Association specifies the type of record you want to create the relationship with. In the example above, Deals will be associated to Line Items.
3. You can select a Label to identify the relationship.
4. Use the Line Items Filter to narrow the line items down to those that would be a good fit for this relationship.
5. Click the Selection button to define rules for picking the line item if there are multiple matches found.
6. Select the Deals Field you want to try and match with the line items. In the example above, Amount from the deals record will be used. 
7. Select the Line Items Field with the value that should match the deals field. In the example above, the Unit Price field will be used. The two matching fields are often the same for both records, though they may have different labels.
8. The Comparison Rule tells Insycle whether the values between the deals and line 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.
9. In the Ignored field, you can select parts of a field value to ignore, such as specific text, whitespace, or characters.
10. The Match Parts field tells Insycle whether to match the entire field or just part of it—such as the first or last few words, first and last characters, or semicolon-separated values.

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 associated record, you can execute that copy in bulk.

Under Step 3, select the field from the source record type (in this example, deals), and the relevant field on the target records (line items). You can choose to copy values from the source record to the target, or target record to the source, and add multiple rows to copy more than one field set.

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

The preview CSV will include these fields and specify if the value was copied for each record.

Preview Changes in a CSV Report

Now with the filters and association actions in place, you can preview the changes you are making to your data. That way, you can check to ensure the relationships are being created as expected before those changes are 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 additional recipients who should receive the CSV (and make sure to 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, 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.

Open the CSV file from your email in a spreadsheet application and review the columns. For each deal record, Insycle tried to match it with line items using the Amount and Quantity values. Each row in the CSV includes the Result of the association step, the deal info, the associated line item info, and the result of the copy operation.

Apply Changes to the CRM

If everything in your CSV preview looks correct, return to Insycle and move forward with applying the changes to the live CRM 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 (in most cases this will be All), then click the Run Now button.

Save Templates and Setup Automation to Maintain Formatting

After you've seen the results in the CRM 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 association operation runs on a set schedule. 

Create a template for each segment and association configuration, then you can create a Recipe to automatically run them together. You can also integrate Insycle Recipes into HubSpot Workflows.

Navigate to RevOps Acceleration > Associate. Select the HubSpot database and Deals record type in the top menu. Then explore the default templates for a pre-built solution.

To find deals that already have line items associated with them, use the filter to include only deals that have one or more related line items.

When you click Search, Insycle will list records in the Record Viewer at the bottom of the page. If you make changes to the filter, you need to click the Search button again to refresh the viewer.

Under Step 2, define the rules to find the previously linked records:

1. Action tells Insycle what to do to the records surfaced in Step 1. Use the Add action to find existing associations.
2. Association specifies the type of record you want to create the relationship with. Select Deal to Line Item.
3. You can leave the Label Unlabeled.
4. Click the Line Items Filter button to narrow the line items down to only those where the Associated Deal ID exists. Note that the Line Items Filter will not update the results in the Record Viewer, only in your final Review steps.
5. Click the Selection button to define rules for picking the line item if there are multiple matches found.
6. Select the Record ID field for the Deals Field. 
7. Select the Associated Deal ID for the Line Items Field.
8. Use the Exact Match Comparison Rule. 
9. You can leave the Ignored field blank.
10. Select Entire Value from the Match Parts field.

Create the rules to copy values between the records.

Under Step 3, select the field from the source record type (in this example, deals), and the relevant field on the target records (line items). You can choose to copy values from the source record to the target, or target record to the source, and can add multiple rows to copy more than one field set.

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

The preview CSV will include these fields and specify if the value was copied for each record.

Preview Changes in a CSV Report

Now with the filters and association actions in place, you can preview the changes you are making to your data. That way, you can check to ensure the relationships are being created as expected before those changes are 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 additional recipients who should receive the CSV (and make sure to 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, 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.

Open the CSV file from your email in a spreadsheet application and review the columns. Each row in the CSV includes the deal info, the associated line item info, and the result of the copy operation.

Apply Changes to the CRM

If everything in your CSV preview looks correct, return to Insycle and move forward with applying the changes to the live CRM 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 (in most cases this will be All), then click the Run Now button.

Save Templates and Setup Automation to Maintain Formatting

After you've seen the results in the CRM 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 copy operation runs on a set schedule. 

Create a template for each segment and association configuration. Additionally, you can create a Recipe, a template bundle that can then be inserted into HubSpot Workflows.

You can specify more than one matching field when making associations in the Associate app. 

For example, maybe you want to compare a deal Amount against a line item's Unit Price or Unit Cost. 

To do this, select the Advanced tab under Step 2. There, you'll be able to add Related Match Fields to catch more associations. 

If you need to create relationships between records based on one of several values in a field, you can use the "Semicolon Separated" Match Parts parameter. 

For example, you need to link contacts to companies based on specific locations using Postal Code. You have a custom field, “Allowed Post Codes,” that contains several codes that cover a region. Since the values are separated by semicolons, Insycle can look at each value in the field for a match.

You can also use the Semicolon Separated parameter to search for matching values in a Related Match Field.

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 broaden the search and 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 a Deal Name of “Acme 64” is found, it could include records with the Deal Name values “Akme 64," "acm 64," or "Acma 64,” as matches.

Similar Match uses looser criteria that cast a wider net for what can be considered matches. Make sure to carefully review the results to ensure the relationships being created are what you're expecting.

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

When you have a reliable set of templates, you can put them together into a longer, ordered sequence as a Recipe. Then, you can schedule that Recipe to run on a consistent, set schedule. Your templates will run one after another in the order that you set.

To add your Recipe to a HubSpot Workflow, it must be automated and set to Execute as HubSpot Workflow Action.

Learn more about associating records in HubSpot Workflows.

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, no matching record found (use 'Grid Edit' to troubleshoot)" message in the Result column of 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..." result 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 go through the process of merging 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 would have to match both field values to be considered appropriate for making the relationship.
3. You can also use the filter in Step 2 of the Associate app to narrow the records to be associated.
   
   In the filter popup, you could, for example, add the "Company name" field and set the Condition, "contains" "HQ." This tells Insycle to only consider companies for association if the Company Name value includes the term "HQ."
   
4. In cases where there are multiple target records that could match, you can add Selection rules for picking the appropriate record.
   
   You can create rules in the selection pop-up to select the most recently created record with an owner assigned.
   

An "Unmodified" Result with the Message "Unmodified, 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 with the Message "No matching record found (use 'Grid Edit' to troubleshoot)" message 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.

Bulk associations require that you have a field that you can use to match the two records. For instance, you might select "Company" for contact records, and "Company Name" for company records. You then use these two fields to associate the two records.

But what do you do if you have no obvious matching field between the two record types that you would like to associate?

This is a fairly common scenario. For example, maybe you would like to associate contacts not only with the company that they work for but with the parent company as well. In this scenario, it is not very likely that you capture the parent company on the contact record, which means that you may have no field to use to match the association. As a result, you'll need to create a custom field for contacts and companies, such as "Custom Parent Company." Ideally, if child companies are already associated with parent companies, you'll be able to pull this data from your company records and populate both custom fields using your CRM's automation features.

Then, you can use the Custom Parent Company field for both contacts and companies to make the match.

The key is finding a data point that would allow you to match the associations, even if it is only available for one record type. Then, you can create the custom matching fields that allow you to make the associations.

It can take a while for Insycle to find and match records if the fields being used to identify the relationship have very long values. The longer the values, the longer it takes Insycle to process the data and generate the results. This might come up when using links with long ID numbers, LinkedIn bios, or other URLs with long strings (e.g., https://www.linkedin.com/in/svadin%C3%ADr-n%C4%9Bmec-1234b31a3/).

If the end of the values are all unique you can try and speed this up by using the Match Parts parameter under Step 2, which will limit the comparison to the last several characters.

Or use the Ignored > Text (Substrings) parameter and click the Terms button.

On the Ignored Text tab of the popup, add the common portion of the URL or text string.

Yes. With Insycle's Associate app, you can create advanced association templates and run them from within HubSpot Workflows. You’ll need to configure association templates in Insycle, bundle them into a Recipe, and insert the Recipe into your HubSpot Workflow.

Learn more in the Associate Records in HubSpot Workflows article.

Currently, Insycle does not support accessing, updating, or associating activities with other objects. 

When working with HubSpot, for every Insycle operation that updates or creates a record, the Run ID will be updated in the custom property, Insycle Run ID. 

If the Insycle Run ID doesn't already exist in your HubSpot database, add it as a custom property with the label "Insycle Run ID" to each object type as needed. 

This object label is the only requirement for the integration to work properly. It's not dependent on the internal name or underlying API field name.

When using an Insycle Recipe that includes templates for more than one object type, such as companies and contacts, the same Run ID will appear in both HubSpot records.