Automate Everything | Entry 88
HubSpot workflows can keep nonprofit data current across enrolled and associated CRM records. They can set, replace, append, clear, or copy eligible property values, preserve important history, and manage changing relationships while routing sensitive decisions to staff for review.
Depending on the property, object, and workflow configuration, an Edit record action can perform several kinds of updates.
An association must exist before a workflow updates an associated record. If several eligible records exist, the workflow needs a dependable rule to choose the correct one, such as an association label or defined property criteria.
Source and target properties must be compatible, and the source should contain a value before a copy action runs. Available actions vary by subscription, permissions, workflow type, object, data model, and sensitive-data settings.
A workflow can begin with a contact, company, household, donation, membership, volunteer activity, event registration, deal, ticket, payment, or eligible custom-object record. It may update that enrolled record and supported records connected to it.
| Workflow starts with | Possible update target | Selection safeguard |
|---|---|---|
| Contact | Household or company | Primary relationship label |
| Household | Membership or address | Current record status |
| Donation | Donor or stewardship record | Gift ID and association |
| Event registration | Registrant or attendance record | Registration ID |
| Program enrollment | Participant or service record | Active program label |
Workflows can move information between compatible properties, including from associated records and earlier workflow actions. A nonprofit might copy a contact address to a household, a household name to a membership, a donation amount into a stewardship field, or an external-system ID to a connected record.
Use a branch to confirm the source value is known. Test text, date, number, dropdown, checkbox, and multi-select properties carefully so an empty or incompatible source does not erase or corrupt the target value.
| Action | Use it when | Nonprofit example |
|---|---|---|
| Set or replace | The new value should be authoritative | Change membership status to Active |
| Append | An eligible value should be added without removing existing values | Add another program interest or volunteer skill |
| Clear | An obsolete or temporary value should stop influencing the record | Remove a processed review flag or intake value |
Append behavior is not available for every property type or record target. Clearing should be deliberate when information may be needed for history, compliance, reporting, or troubleshooting.
Some changes need a limited, reportable history. Before changing a household address, a workflow can copy the current address to historical properties, record the date and source of the request, create a review task, wait for approval, and update the official address only after approval.
| Often suitable for automatic updates | Often requires staff review |
|---|---|
| Correct capitalization or formatting | Household address or composition |
| Standardize state or province values | Legal names or primary contacts |
| Set status after a verified event | Tax documentation or donor credit |
| Record submission source or activity date | Consent, restricted gifts, or program eligibility |
Workflows can still manage a human review by storing a proposed value, creating a task, pausing, checking an approval status, applying the approved value, and escalating an unresolved request.
A nonprofit that needs several addresses, effective dates, verification, primary and mailing status, or a durable history may represent addresses as separate custom-object records.
This design preserves stronger history but requires more architecture, governance, and reporting than storing one address directly on a household.
The relationship between two records may change even when neither record should be deleted. A workflow can apply, update, or remove eligible association labels while preserving the underlying history.
Define whether the association itself should remain when its label changes.
Marriage, divorce, adoption, a new dependent, or an elderly parent joining a household can affect household composition, addresses, memberships, program eligibility, communication, and record access. These changes should use controlled labels, historical data, review tasks, and privacy rules.
| Change | Workflow support | Human decision |
|---|---|---|
| Household consolidation | Associate contacts, update name, apply labels | Choose the surviving household and preserve history |
| Household separation | Create a new household and update associations | Resolve gifts, memberships, addresses, and privacy |
| New child or dependent | Create or associate a family-member record | Confirm necessity, access, and retention |
| Elderly parent joins | Update size, labels, and program review tasks | Confirm consent, sensitivity, and operational need |
Household and family changes can be sensitive. Avoid broadcasting them through broad notifications or unrestricted properties. Protect information about minors, dependents, care recipients, consent, eligibility, and family relationships with appropriate access and retention rules.
When an update requires review, a form should write to proposed-value properties rather than directly overwriting authoritative fields. The workflow can validate the input, compare it with the current value, preserve history, create a task, update the official value after approval, and clear temporary properties last.
Connected applications may provide payment, donation, attendance, volunteer, membership, subscription, program, application, shipping, or external-ID data. Define which system is authoritative, how long updates take, what happens when values conflict, whether a delay is necessary, and how failures are monitored.
A workflow that runs before the integration finishes may act on incomplete information.
A household may have several donations, memberships, addresses, registrations, enrollments, or tickets. Labels such as Current Membership, Primary Address, Active Program Enrollment, Event Registrant, and Primary Donation Contact help a workflow target the authoritative record.
Using only the most recently updated or most recently associated record can select something recent but incorrect. The rule should reflect the nonprofit's data architecture.
Record-editing capabilities can include updating enrolled and eligible associated records, setting, replacing, appending, clearing, and copying values, using associated or earlier-action data, and managing eligible association labels and relationships.
HubSpot workflows can keep constituent, household, donor, member, volunteer, program, event, and payment information current as relationships and activities change. The value is not simply that data can be updated, but that the right value reaches the right record through a governed process.
Clear sources of truth, compatible properties, reliable associations, meaningful labels, preserved history, approval paths, and monitoring let a nonprofit automate maintenance without automating costly mistakes.