Powerful (Easy!) Nonprofit Automations | HubSpot for Nonprofits Resource Hub

Easy to build does not mean limited in power

A workflow can begin when something happens, a record meets criteria, a scheduled date arrives, HubSpot receives a qualifying webhook, or a user enrolls a record manually. It can then send communications, update data, create tasks and records, route work, apply delays, check conditions, and move records through different paths.

HubSpot currently supports AI-assisted creation, templates, and build-from-scratch workflows. The standard process brings enrollment, re-enrollment, unenrollment, actions, review, and publication into one visual environment.

Content boundary

Broad CRM flexibility is not an unlimited technical guarantee

The specific data must be available to the selected workflow type and supported by the applicable trigger, branch, or action. Workflow types, associated-record capabilities, AI features, actions, and limits vary by subscription, seat, permissions, integrations, property access, and HubSpot Credits.

Follow understandable workflow building blocks

Who or what should enter?
What happened or became true?
What should HubSpot do next?
Should the record wait?
Does it meet another condition?
Which path should it follow?
When should it leave or enter again?

A simple workflow may have one trigger, email, task, and delay. In the same editor, a more sophisticated workflow can combine filters, associated-record criteria, branches, goals, record creation, notifications, integration actions, re-enrollment rules, and error alerts.

Start with the right enrollment trigger

Enrollment approach	How it starts
Event-based	Enroll when a specific supported event occurs.
Filter-based	Enroll when defined record criteria are true.
Schedule-based	Enroll on a date or recurring schedule.
Webhook-based	Enroll when HubSpot receives a qualifying webhook from an external system.
Manual enrollment	Allow a user or another HubSpot tool to place a record into the workflow.

The trigger should represent a real nonprofit event or state clearly enough that the team can explain why every record entered.

Translate nonprofit moments into workflow triggers

A donation is completed
A volunteer form is submitted
A membership approaches expiration
An event registration is created
A grant reaches a pipeline stage
Lifetime giving crosses a threshold
A payment fails
A participant completes a program
A sponsor signs an agreement
A volunteer becomes inactive
A support ticket is submitted
An external platform sends a webhook
A scheduled date arrives
A CRM status changes

Distinguish a current condition from a specific event

Trigger type	Question	Nonprofit example
Filter-based	Is this condition currently true?	Membership status is active and renewal date is within 30 days.
Event-based	Did this event occur?	A membership-renewal form was submitted.

Filter-based workflows can use configured re-enrollment criteria. Event-based triggers may be set to enroll once or each time the event occurs. The correct type makes the workflow easier to understand and maintain.

Use supported CRM information to guide the experience

Contact and company properties
Deal or donation properties
Ticket information
Payments and subscriptions
Membership records
Event information
Custom-object properties
Form submissions
Marketing engagement
Website activity
Associations
Action outputs
Integration data
Custom events

A donor acknowledgment workflow might consider amount, gift type, designation, first-time donor status, communication preferences, major-donor status, assigned officer, household relationships, and whether an acknowledgment was already sent.

Use associated records to understand the broader relationship

A constituent can be connected to a household, company, donations, registrations, memberships, volunteer logs, tickets, sponsorships, program enrollments, grants, and payments. Supported associated-record criteria help a workflow evaluate more than one isolated record.

Household event-registration example

Before sending another reminder, a contact-based workflow can check whether the contact registered, another applicable household member registered, or the household already has an active registration record. If registration exists, the workflow can end or redirect the reminder path.

Consistent household records
Correct member associations
Reportable registration data
Defined qualifying statuses
Rules for multiple registrations
Clear household eligibility

The workflow builder makes the logic accessible. The CRM architecture makes the logic possible.

Create meaningful paths with branches

HubSpot supports branch logic based on a single property or earlier action output, if/then criteria using AND and OR logic, and random percentage distribution for eligible subscriptions and use cases.

First-time or returning donor
Donation amount
Member or nonmember
Individual or organization
Volunteer approval status
Preferred language
Event attendance
Grant stage
Program interest
Assigned staff member
Communication consent
Household response status

Example: branch a donation acknowledgment workflow

Welcome a first-time donor
Notify staff about a major gift
Send recurring-donor messaging
Suppress public recognition for anonymity
Create tribute-gift follow-up
Route failed payments to recovery

One workflow can support several constituent experiences while applying the nonprofit's rules consistently.

Choose from contextual workflow actions

Send a marketing email
Create a task
Send an internal notification
Update or clear a property
Copy data between records
Create a CRM record
Create or modify an association
Add or remove an association label
Apply a delay
Create a branch
Enroll in another workflow
Trigger an integration action
Use a webhook
Run eligible custom code
Use an AI or agentic action
Generate actions with AI

HubSpot groups relevant actions in the editor. What appears depends on the workflow type, enrolled object, permissions, accessible properties, installed apps, subscription, seats, and Credits.

Start from scratch, a template, or AI

Starting point	Best fit	Important review
Build from scratch	A unique process with documented rules, triggers, outcomes, and custom branching	Confirm the enrolled object and every business rule.
Workflow template	A common process where a proven structure helps a newer or faster-moving team	Review prerequisites, triggers, actions, and purpose before customization.
Breeze Assistant	A written process description that AI can translate into a first workflow draft	Review every trigger, delay, action, setting, communication, and consequence before activation.

AI-created workflows remain off until a user reviews and activates them. AI access settings must be enabled, and assistance inside an existing workflow may be limited to actions rather than triggers.

Example: stop event reminders after registration

Enroll an eligible contact with the required communication consent.
Send the initial invitation.
Wait three days.
Check for an associated event registration.
Check whether an applicable household member registered.
End the reminder path when registration exists.
Otherwise, send the reminder.
Wait until the response deadline approaches.
Check registration conditions again.
Create a personal follow-up task for a high-priority constituent.
End the workflow when the deadline passes.

This requires dependable household associations, registration records and statuses, consent properties, event dates, priority segmentation, and suppression rules.

Example: coordinate donation follow-up

When a donation reaches the nonprofit's completed or received status, a workflow can update the latest gift date, send an acknowledgment, notify the assigned officer, create a major-gift task, branch tribute gifts, maintain donor status, associate the gift with its campaign or fund, flag missing information, and end conflicting solicitation workflows.

First-time donor
Returning donor
Recurring donor
Major donor
Anonymous donor
Tribute donor
Organization or individual
Restricted or unrestricted gift

Plan re-enrollment and unenrollment

Define whether a record can enter again, which change permits it, when an active record should leave, whether another workflow should end this one, and whether a completed record can return later.

Re-enrollment may be appropriate	Re-enrollment may be inappropriate
Annual membership renewal	One-time donor welcome
Recurring event invitations	Initial volunteer onboarding
Repeated failed payments	One-time program completion
Annual tax-letter preparation	Historical data cleanup
Recurring volunteer inactivity review	Other one-time processes

Easy to build does not mean safe to skip planning

Purpose and success metric
Enrolled object
Enrollment trigger
Exclusions
Re-enrollment rules
Unenrollment rules
Branch definitions
Timing and delays
Actions and record changes
Communication requirements
Error handling
Workflow owner
Testing plan
Maintenance process

A poorly planned workflow can perform the wrong action quickly, consistently, and at scale.

Test every important path before publication

A qualifying record
A record that should be excluded
A record with missing information
A record with several associations
A record for every major branch
A record that should leave
A record that may re-enroll
A consent-restricted record
An integration-created record
An edge case with conflicting data

HubSpot provides workflow review and publication steps, branch-path testing, and alerts when actions need attention.

Data timing

Wait for supporting data before evaluating a branch

Email engagement, page views, form-driven changes, integration data, associated records, and calculated properties may not update immediately. HubSpot specifically notes that page-view analytics may require an 80-minute delay before a branch is evaluated. A condition checked too early can send the record down the wrong path.

Current HubSpot considerations

Confirm which workflow features are available in the nonprofit's portal

Current functionality can include AI creation, templates, build-from-scratch workflows, filter, event, schedule, webhook, and manual enrollment, branches, delays, re-enrollment, unenrollment, HubSpot actions, connected-app actions, AI steps, eligible custom code, record creation, and association management.

Availability varies by subscription, assigned seat, user permissions, workflow object, integrations, AI settings, HubSpot Credits, and property or tool access.

Best practices for easy-to-build nonprofit automations

Start with one outcome: define the result before selecting actions.
Use structured data: rely on controlled properties, statuses, associations, and dates.
Build around relationships: use households, donations, memberships, events, companies, and volunteer records when they matter.
Use branches carefully: every path should represent a meaningful rule.
Plan exit conditions: stop messages and tasks after the constituent completes the action.
Add necessary delays: let HubSpot and integrations process supporting information.
Test edge cases: include blanks, multiple associations, conflicts, and unexpected values.
Review AI drafts: verify every trigger, delay, action, and branch.
Assign an owner: every live workflow needs accountable maintenance.
Name workflows clearly: use names such as "Development | Donation Received | Donor Acknowledgment."

Make sophisticated nonprofit automation understandable

HubSpot's visual workflow builder lowers the barrier to automation without limiting the sophistication of the process. When nonprofits pair the builder with structured data, reliable associations, documented rules, thoughtful exits, thorough testing, and clear ownership, teams can automate repetitive work while keeping constituent experiences relevant and accurate.