<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1094218042721276&amp;ev=PageView&amp;noscript=1">
Skip to content

Architecture Entry 8 of 11

Can HubSpot workflows use data from associated records?

Yes. HubSpot workflows can use information from associated records in supported enrollment criteria, filters, branches, notifications, record updates, and other workflow actions. An automation based on one contact does not always have to rely only on information stored directly on that contact.

What does this mean?

Every HubSpot workflow has an enrolled record: the primary record moving through the automation. A workflow may be based on a contact, company, deal, ticket, custom object, subscription, payment, or another supported record type.

Nonprofit decisions, however, often depend on information stored elsewhere in the CRM. Depending on the workflow and account configuration, HubSpot may also use data from associated records such as:

  • Households and companies
  • Donations and payments
  • Volunteer assignments
  • Memberships
  • Event registrations
  • Program enrollments
  • Sponsorships
  • Tickets or service cases

Supported workflow tools can use that connected information to enroll or exclude a record, create an if/then branch, personalize an internal notification, provide a data variable, copy information, update an enrolled or associated record, or determine which communication or task should be created.

Why does this matter for nonprofits?

Nonprofit relationships are connected. A communication sent to one person may need to account for what has already happened across their household, employer, donations, volunteering, membership, events, or program involvement.

Without associated-record data, staff may need to:

  • Check several records before sending an email
  • Manually exclude people from a campaign
  • Copy information between records
  • Maintain duplicate fields
  • Review donations before assigning follow-up
  • Ask another department for information
  • Export records before making a decision
  • Correct duplicate or inappropriate communications

Using associated information allows the workflow to respond to the constituent's wider relationship with the nonprofit instead of treating every record as isolated.

 

A nonprofit example

A nonprofit is promoting its annual fundraising event. It creates a contact-based workflow for people who have shown interest, but the standard registration reminder should not go to everyone.

The workflow checks associated event registrations, households, sponsorships, and volunteer assignments, then routes each person appropriately.

  • The Santos household
  • A company that sponsors the annual gala
  • Three donation records
  • A recurring giving plan
  • Two volunteer assignments
  • An upcoming event registration
Already registered: Remove the contact from the registration-reminder path.
Event volunteer: Send volunteer-specific preparation information instead of a general appeal.
Sponsor or major-gift household: Create a task for the appropriate development employee rather than sending the standard marketing email.
No qualifying associated activity: Continue through the standard registration campaign.

One workflow can respond differently based on the person's wider relationship with the organization.

How can associated information be used?

Enrollment triggers and filters

A contact might enter a workflow when an associated donation reaches a threshold, a membership approaches renewal, a volunteer assignment is completed, or an event registration reaches a specific status.

If/then branches

Related information can determine which path the enrolled record follows. A workflow could create a major-gift task for a qualifying donation, send the member version of an email, suppress an appeal when the household already donated, or stop an event sequence after a cancellation.

Data variables

Supported actions can use information from additional record sources. An internal notification might include the contact's name, household giving total, most relevant donation, membership renewal date, volunteer assignment, event, company, or program status.

Record updates

Workflows can update supported properties on enrolled and associated records and may copy compatible values between records. The association must exist before the workflow attempts to edit the associated record.

Internal notifications and tasks

Associated information gives staff the context behind an alert or assignment.

Maya's household has reached the major-gift threshold. Their most recent associated donation was $2,500, and their household giving total is now $12,000. Please review the household and donation records before contacting them.

Important architecture note

The workflow must know which associated record should provide the information.

One contact may have several donations, event registrations, volunteer assignments, household or company relationships, memberships, or program enrollments. Asking for “the associated donation” is not enough when several donations qualify.

The team may need to identify the most recent or largest donation, an active membership, a registration for a specific event, a volunteer assignment with a particular status, or a household with a specific association label.

Before building the workflow, decide:

  • Which object will enroll
  • Which associated object holds the data
  • Which record to use when several qualify
  • Whether an association label is needed
  • Which record the workflow should update
  • What happens when no record exists
  • Whether re-enrollment is required
  • Which team owns the data

Requirements and limitations

Associated-record data is not automatically available in every workflow action. Availability depends on the HubSpot subscription, workflow type, enrolled and associated objects, selected action, association setup, permissions, property values, and account configuration.

Before implementation, confirm:

  • The workflow can access the required object
  • The action supports the required data variables
  • The association exists before an update runs
  • Filters identify the intended record
  • Property types are compatible
  • Missing information has a defined path
  • Re-enrollment behavior is correct
  • Sensitive data is handled appropriately
  • Users have the necessary permissions
  • The workflow is tested before activation

HubSpot currently allows up to 50 data sources in a workflow. Some sources are automatically available in certain workflows, while others must be added and filtered through the workflow's data panel. Exact options should be confirmed for the nonprofit's account.