Automate Everything | Entry 89
HubSpot workflows can intentionally add eligible records to or remove them from static segments over time. Nonprofits gain the controlled membership of a static audience and the ongoing automation of a workflow, making it easier to manage campaigns, outreach, events, volunteers, and operational review queues.
A segment is a group of CRM records organized for a specific purpose. Depending on the object and available tools, it may contain contacts, companies, deals, or other supported records.
Older documentation, workflow actions, or interface labels may still use the word “list” or show it in parentheses. This entry uses the current term, “segment,” while recognizing that teams may encounter both labels.
| Segment type | How membership changes | Best fit |
|---|---|---|
| Active | HubSpot continuously adds or removes records as they begin or stop meeting filter criteria. | Current donors, approved volunteers, expiring memberships, regional audiences, or other always-current groups. |
| Static | Original filters are not automatically reevaluated. Membership changes only through deliberate actions. | Point-in-time audiences, approved campaign groups, event snapshots, cleanup batches, and curated cohorts. |
Should membership be determined continuously by data, or intentionally by a process?
A static segment does not recalculate membership from its original filters. It can still evolve through manual additions, manual removals, imports, workflow actions, and other supported HubSpot tools.
The important distinction is that each change happens through an intentional action rather than continuous filter reevaluation.
HubSpot currently provides actions to add eligible enrolled contacts, companies, or deals to a static segment and to remove them later. These actions can work with triggers, branches, delays, approval properties, and other CRM information.
Add to static segment and Remove from static segment currently require Marketing Hub Professional or Enterprise. Supported records and actions depend on the workflow, subscription, object, permissions, and portal configuration.
When a qualifying donation is completed, a workflow can confirm that the donor belongs to the campaign segment, remove the donor from the solicitation audience, add the donor to a stewardship segment, suppress related asks, and notify the assigned development officer.
This helps prevent someone from receiving the same ask after already giving. The nonprofit should still confirm how communications that are already scheduled or queued behave when membership changes.
A nonprofit can preserve an approved gala invitation list while workflows add newly approved guests and move registrants into the groups relevant to their next steps.
When someone registers, the workflow can remove the person from invitation reminders and add them to attendee, food-selection, reminder, or role-specific segments.
This provides more control than an active segment based only on a broad status such as Approved Volunteer.
A board-approved major-donor campaign may require a controlled audience rather than automatic entry whenever someone crosses a giving threshold. A workflow can identify a newly eligible donor, create a review task, wait for approval, add the donor only after approval, and remove the donor when outreach status changes.
The workflow supports the decision process without bypassing the development team.
A workflow can add records to a static cleanup segment when it finds a missing household association, an unassociated donation, an incomplete address, conflicting membership statuses, missing consent, a suspected duplicate, or an integration error.
After staff correct the issue, a workflow can remove the record from the queue. This turns ongoing CRM maintenance into a visible process with a defined endpoint.
An active segment may change as CRM values change. A static segment preserves the selected population unless someone or something intentionally modifies it.
| Use an active segment when | Use a workflow-managed static segment when |
|---|---|
| Membership should always reflect current criteria. | Membership requires approval or curation. |
| Records should enter and leave automatically. | The audience represents a point in time. |
| The filters are the complete source of truth. | Several steps must happen before entry. |
| The group supports ongoing operations. | Removal should follow a defined event or decision. |
Workflows are not required for every segmentation use case. If membership should remain continuously synchronized with filters, an active segment is generally the better tool.
A workflow can check additional conditions and send records down different paths. One path may add the record, another may create a review task, and another may exclude it.
A nonprofit may remove someone when they donate, register, renew, withdraw, become ineligible, request different communication, enter another campaign, are rejected by staff, or are identified as a duplicate.
Every workflow-managed static segment should have a removal strategy. Otherwise, the group may keep growing after records no longer belong there.
The segment Activity area can help teams review which records were added or removed, when membership changed, and the type of change. This is especially useful when several workflows and staff members manage the same segment.
Several workflows can manage one static segment, but their responsibilities must be clear. One might add invitees, another remove registrants, another add VIPs, and another remove people with missing consent.
Without coordination, a record can repeatedly move in and out, a manual decision can be overridden, and teams may not know which workflow owns the audience. Document every workflow that changes an important segment.
Before using a segment for email, SMS, direct mail, advertising, or another channel, confirm consent, subscription status, marketing-contact requirements, legal basis, channel preferences, suppression rules, frequency limits, and sensitive-audience restrictions.
Segment membership, marketing-contact status, and communication subscription are separate controls. A contact may belong to a segment for reporting or operations without being eligible for marketing.
Workflow-managed static segments give nonprofits a practical middle ground between a frozen snapshot and an audience that changes continuously from filters. They preserve intentional selection while allowing specific events, decisions, and outcomes to change membership.
Clear ownership, documented rules, coordinated workflows, membership history, and separate consent controls keep these audiences reliable for campaigns and operations.