How Nonprofits Can Use HubSpot’s AI Workflow Builder | HubSpot for Nonprofits Resource Hub

Turn a plain-language goal into workflow logic

Instead of starting with an empty workflow and configuring every technical detail manually, a user can describe what the nonprofit wants to accomplish. HubSpot's AI can then suggest or generate a functional workflow structure for review.

When someone makes their first completed donation, send a personalized thank-you email, notify the development team, and create a follow-up task for the assigned fundraiser.

The resulting draft might include a donation-based enrollment trigger, a first-gift condition, a thank-you email, an internal notification, an assigned task, and a delay before the next stewardship action.

Important safeguard

AI provides a starting point, not final approval

An AI-generated workflow is not automatically accurate, complete, or ready to use. Every draft should be reviewed, tested, and approved by a knowledgeable user before activation. HubSpot keeps AI-created workflows turned off until a user manually activates them.

Availability also varies by subscription, seat, permissions, AI settings, workflow access, connected tools, workflow type, and HubSpot Credits.

Describe the nonprofit process you want to automate

Thank a first-time donor
Alert staff about a major gift
Create a fundraiser stewardship task
Remind members to renew
Follow up with prospective volunteers
Update event-registration status
Notify a grant manager about a deadline
Stop outreach after a donation
Route failed recurring gifts
Flag missing constituent information

The nonprofit still supplies the strategy, organizational knowledge, policies, exceptions, and judgment. HubSpot helps translate those requirements into workflow logic.

Build a more complete first draft

Depending on the portal and workflow environment, Breeze Assistant can help create or configure supported components such as:

Enrollment triggers
Workflow actions
Delays
Internal notifications
Task creation
Record updates
Record assignments
Communications
Workflow settings
Other supported steps

The user should still confirm that the correct object, properties, criteria, delays, actions, settings, and records were selected.

Give the AI enough direction to be useful

Prompt quality	Example	What it communicates
Too vague	Create a donor workflow.	No trigger, audience, action, timing, exclusion, assignment, or end condition.
Stronger	When a new donor makes a first completed donation, send a thank-you email immediately and create a follow-up task for the assigned development officer due within two business days. Exclude anonymous donors and anyone with an open stewardship task.	Enrollment event, audience, actions, timing, assignment, exclusions, and duplicate prevention.

Clear instructions improve the relevance and completeness of the initial workflow, but they do not replace review.

Use a simple prompt structure

When [this happens], if [these conditions are true], then [take these actions], unless [an exclusion applies].

Membership example

When a membership is 30 days from expiration, if the membership is active and no renewal payment has been received, send a renewal email and create a task for the membership coordinator. Do not enroll anyone who opted out of membership communications.

Event example

When an event registration is submitted, send a confirmation email, update the contact's event-registration status, and notify the events team if the registrant requested an accessibility accommodation.

Include the details that shape a responsible workflow

What event or condition should start the workflow?
Which object or record type should enroll?
Who should be included or excluded?
Which properties and associated records should be checked?
What actions should HubSpot take?
Which team member should own the next step?
How long should the workflow wait between actions?
Should different records follow different paths?
What should stop the workflow?
Should records be allowed to enroll again?
What should happen when required information is missing?
Should another workflow start or stop?
Which consent and communication rules apply?

Example: major-donor stewardship

When a completed donation of $5,000 or more is received, notify the assigned development officer, create a high-priority task due within two business days, and send the appropriate thank-you email. Exclude public-recognition actions for anonymous donors. If no officer is assigned, notify the development director.

Possible criteria	Possible actions	Potential branches
Completed gift, $5,000 minimum, valid donor association, no prior enrollment	Notify staff, create task, update major-gift date, acknowledge donor, flag missing owner, end conflicting solicitations	Anonymous or recognized, individual or corporate, first-time or returning, assigned or unassigned, restricted or unrestricted

The nonprofit must still define its threshold, assignment rules, acknowledgment requirements, and stewardship process.

Example: membership renewal

Enroll active members 30 days before expiration. Send a renewal reminder, wait seven days, and check for a completed renewal payment. End reminders after renewal. Otherwise, send a second reminder and create a coordinator task seven days before expiration.

Enroll the eligible member or membership.
Send the first reminder.
Wait seven days.
Check for a completed payment.
End the path after renewal.
Send a second reminder if unpaid.
Wait until seven days before expiration.
Check renewal status again.
Create a follow-up task if still unpaid.
End after renewal or expiration.

This depends on reliable membership records, dates, statuses, member-payment associations, payment-completion criteria, consent data, and re-enrollment rules.

Example: event registration with household awareness

When a contact joins the gala invitation audience, send an invitation. Wait three days and check whether the contact or an associated household member registered. End reminders when a qualifying registration exists. Otherwise, send a reminder and create a personal task for unregistered major donors seven days before the event.

Consistent household records
Correct household associations
Reliable registration records
Defined registration statuses
Accurate event dates
Priority segmentation
Consent properties
Clear suppression rules

The AI can draft the logic, but the outcome still depends on the nonprofit's CRM architecture.

Example: volunteer follow-up

When someone submits the volunteer-interest form, send a confirmation and create a coordinator task. If a valid background check exists, send approved-volunteer next steps. Otherwise, send screening instructions. Exclude volunteers who are already active.

New or existing volunteer
Background check complete or required
Approved or pending
Adult or youth volunteer
Program or location preference
Training complete or incomplete
Active or inactive
Missing required information

Use the AI builder as a learning tool

AI-assisted creation can show newer users which HubSpot actions may support the process, including record creation and updates, assignments, internal tasks and notifications, eligible emails, delays, branches, property changes, associations, segments, connected-app actions, and enrollment in other workflows.

Describe the desired outcome.
Review the suggested workflow.
Learn why each component was included.
Adjust it using organizational knowledge.
Test representative records.
Review the results.
Apply the lessons to future automations.

Workflow environment matters

AI behavior can differ inside an existing workflow

HubSpot documents that Breeze Assistant can create complete workflows from prompts. When used inside an existing standard workflow editor, however, it may be limited to adding or editing actions and may not change enrollment triggers from that location.

Always inspect what the AI created instead of assuming every part of the workflow was addressed.

Review every generated component before activation

Correct enrolled object
Correct qualifying records
Required exclusions
Intended trigger
Correct communication recipients
Accurate task assignments
Appropriate delays and dates
Valid branch logic
Controlled repeat enrollment
Suitable re-enrollment rules
Clear unenrollment conditions
Appropriate sensitive-data handling
No conflicting automation
Available actions and features
Named owner
Defined success metric

Verify every property, value, and association

AI may suggest properties or filters based on portal data and prompt wording. Confirm that each selected property is authoritative, reliable, current, and appropriate for the rule.

Avoid duplicate or outdated fields
Handle blank values
Check historical records
Confirm associated-record criteria
Protect valuable existing information
Use current business definitions

If several fields appear to represent donor status but only one is maintained, using the wrong field can enroll or exclude the wrong people.

Test more than the ideal scenario

A donor workflow should be tested with representative records and edge cases before it is turned on.

First-time donor
Returning donor
Recurring donor
Anonymous donor
Tribute donor
Donor without an owner
Consent-restricted donor
Existing stewardship task
Household that already gave
Missing information
Integration-created gift
Failed or refunded payment

Decide how often the process should run

Re-enrollment may be appropriate	Re-enrollment may be inappropriate
Annual membership renewal	One-time donor welcome
Recurring event invitation	Initial volunteer onboarding
Repeated failed payment	One-time program completion
Annual tax-letter process	Historical data cleanup
Repeat donation acknowledgment	One-time consent confirmation

Also define which event permits re-enrollment, what removes active records, and whether other workflows should start or stop.

Govern AI-assisted workflow creation

Who can use AI tools?
Who can create workflows?
Who can activate workflows?
What may be included in prompts?
What sensitive data is excluded?
Who reviews generated workflows?
What testing is required?
How are AI-assisted changes documented?
Which workflows need approval?
How are outcomes and errors monitored?

The speed of AI-assisted creation should not replace controls around publication, data access, communication, and record updates.

Current HubSpot considerations

Confirm the capabilities available in the portal

Current AI-assisted workflow functionality can include creating workflows from prompts, generating triggers and actions, adding supported delays and settings, editing actions in eligible workflow editors, suggesting automations, using AI-assisted actions, and generating eligible custom code.

Availability varies by subscription, seat, permissions, workflow access, AI settings, Breeze access, workflow object, integrations, HubSpot Credits, and property or tool access. Appropriate workflow permissions or Super Admin access are required.

Know where the AI builder delivers the most value

The outcome is clear, but the starting point is not
A common process is being automated for the first time
A user wants to learn available actions
Several connected actions are needed
A team wants a draft before administrator review
Repetitive administrative work needs automation
An operational process needs workflow logic
A repeatable process needs documentation

It shortens the distance between recognizing repetitive work and creating a practical automation.

Expect more human refinement when the foundation is unclear

Properties have similar names
Business rules are undocumented
Household relationships are inconsistent
Donations are associated incorrectly
Membership statuses overlap
Critical information lives only in notes
Departments use different definitions
The process has many exceptions
Workflows update the same fields
Consent rules are undefined
Integration data arrives late
Staff disagree on next steps

Best practices for easy-to-build nonprofit automations

Start with one clear outcome: define the result before writing the prompt.
Describe the trigger precisely: explain the exact event or condition.
Include exclusions: identify who or what should not enroll.
Define timing: include delays, deadlines, business days, and recurring dates.
Name the responsible team: specify task, notification, and assignment owners.
Account for associated records: explain which related records affect the decision.
Define the exit condition: state what stops the workflow.
Review every component: verify the object, criteria, properties, branches, delays, and actions.
Test edge cases: include blanks, duplicates, conflicts, multiple associations, and integration delays.
Activate carefully: begin with a limited audience where practical.
Assign an owner: make someone accountable for monitoring and maintenance.
Document the prompt: preserve the original request and major revisions.
Measure the outcome: define how the nonprofit will know the automation works.

Create a virtuous cycle of speed and learning

The nonprofit describes its process. HubSpot suggests a structure. The user reviews the result, learns from the recommendations, and improves the workflow. Each cycle makes the next automation easier to describe and safer to build.

AI does not replace the nonprofit's judgment. It helps the organization turn that judgment into a functional workflow more quickly, leaving a small but mighty team more time to advance the mission.