
Implementation Guide: Trigger volunteer onboarding workflows when new volunteers register
Step-by-step implementation guide for deploying AI to trigger volunteer onboarding workflows when new volunteers register for Non-Profit Organizations clients.
Hardware Procurement
Optional: Volunteer Check-In Kiosk Tablet
Volunteer Check-In Kiosk Tablet
$349 per unit (MSP cost) / $449 suggested resale with kiosk configuration and mounting bracket
On-site kiosk for walk-in volunteer registration at events or the organization's front desk. Runs the Bloomerang Volunteer or web-based registration form in Safari guided access (kiosk) mode. This is fully optional—most nonprofits will accept registrations online only.
Optional: Tablet Kiosk Stand/Enclosure
$199 per unit (MSP cost) / $275 suggested resale with installation
Secures the iPad in a tamper-resistant enclosure for unattended kiosk use at volunteer registration desks, events, or lobbies. Prevents theft and restricts access to the registration form only.
Optional: Self-Hosted Automation Server (n8n path only)
Droplet - Basic Regular Intel - 2 vCPU / 4 GB RAM / 80 GB SSD
$24/month (MSP cost) / $75–$100/month managed service fee to client
Linux VPS for hosting n8n Community Edition self-hosted. Only required if choosing the n8n open-source path instead of Zapier or Power Automate SaaS. A single droplet can host workflows for 10–20 nonprofit clients, maximizing MSP margin.
Software Procurement
Zapier Professional Plan (Primary Automation Engine)
$25.49/month after 15% nonprofit discount (billed annually) / $40/month suggested client billing
Core workflow orchestration platform. Detects new volunteer registration events and triggers the complete onboarding sequence: CRM sync, welcome email, e-signature request, background check initiation, training assignment, calendar scheduling, and staff notification. Connects to 7,000+ applications with pre-built templates.
Bloomerang Volunteer
$119/month billed annually ($1,428/year) / $165/month suggested client billing
Purpose-built volunteer management system serving as the primary volunteer registration portal and source-of-truth for volunteer records. Includes reusable form templates, digital waivers with built-in e-signatures, group sign-up options, built-in background checks via Sterling partnership, file uploads, AI-powered scheduling, communication and messaging tools, mobile app for managers and volunteers, and bi-directional CRM data sync.
HubSpot CRM (Free Tier)
$0/month (free tier) / Include in managed service bundle at no additional charge
Central constituent relationship management database. Stores unified volunteer and donor profiles, tracks engagement history, provides reporting dashboards. The free tier supports unlimited users, 1M contacts, and includes email marketing (up to 2,000 sends/month), forms, list segmentation, and basic automation. If the client already has a CRM (Salesforce NPSP, Bloomerang CRM), use that instead.
DocuSign eSignature for Nonprofits
$10–$15/user/month with nonprofit discount / $20/user/month suggested client billing
Sends volunteer waivers, liability releases, codes of conduct, and confidentiality agreements for legally binding electronic signature. Templates allow automatic field population from the automation workflow. Required only if Bloomerang Volunteer's built-in e-signature capability is insufficient for the client's legal requirements.
Sterling Volunteers Background Screening
$15–$30 per background check (MSP cost) / $35–$50 per check suggested client billing or pass-through with admin fee
Provides FCRA-compliant criminal background checks, sex offender registry searches, and identity verification for volunteers working with vulnerable populations (youth, elderly). Integrates natively with Bloomerang Volunteer and VolunteerHub for automated check initiation. Essential for youth-serving organizations.
Microsoft 365 Business Basic (Donated Licenses)
$0/month for up to 300 users (donated via Microsoft Nonprofits program) / Include in managed service bundle
Provides Exchange Online email, Microsoft Teams for staff notifications, SharePoint for document storage, and OneDrive. Eligible nonprofits receive up to 300 free Business Basic licenses. If the client prefers Google, use Google Workspace for Nonprofits (also free) instead.
Google Workspace for Nonprofits (Alternative to M365)
$0/month (free for eligible nonprofits via Google for Nonprofits) / Include in managed service bundle
Alternative productivity suite providing Gmail, Google Forms (registration trigger source), Google Sheets (data logging), Google Calendar (orientation scheduling), and Google Drive (document storage). Best for organizations already in the Google ecosystem. Register through Google for Nonprofits via TechSoup.
Mailchimp Standard (Email Automation)
$0/month (free tier for up to 500 contacts) or $13/month Standard plan for 500+ contacts / $25/month suggested client billing if paid tier
Sends automated multi-step welcome email sequences to new volunteers. The free tier supports up to 500 contacts and 1,000 sends/month. Required only if the CRM's built-in email capabilities are insufficient for the desired onboarding email sequence complexity.
Calendly Free (Orientation Scheduling)
$0/month (free tier, 1 event type) / Include in managed service bundle
Allows new volunteers to self-schedule their orientation session via a personalized booking link sent in the onboarding workflow. Integrates with Google Calendar and Outlook. The free tier supports one event type, which is sufficient for a single 'Volunteer Orientation' booking page.
Prerequisites
- Client has an active 501(c)(3) status or equivalent nonprofit designation (required for Microsoft 365 donated licenses, Google for Nonprofits, Zapier nonprofit discount, HubSpot nonprofit discount, and DocuSign nonprofit pricing)
- Client is registered with TechSoup (https://www.techsoup.org/) — required to validate nonprofit eligibility for most vendor discount programs
- Client has a stable broadband internet connection (25+ Mbps) at their primary office location
- Client has at least one staff member designated as the Volunteer Coordinator who will serve as the primary point of contact and system administrator
- Client has documented their current volunteer onboarding process (even if informal) — MSP will need this during discovery to map the automation workflow
- Client has an existing website or web presence where a volunteer registration page/link can be hosted or linked
- Client has an existing email domain (e.g., @nonprofitname.org) configured for sending — required for transactional emails to pass spam filters
- All staff who will interact with the system have a modern web browser (Chrome 90+, Edge 90+, Firefox 90+, or Safari 15+) on their workstations
- If background checks are required: client has determined which check types are needed based on their state laws and the populations they serve (youth, elderly, etc.)
- Client has identified all required onboarding documents: volunteer waiver/liability release, code of conduct, confidentiality agreement, emergency contact form, and any role-specific documents
- If using Microsoft 365: client has claimed their nonprofit offer through the Microsoft Nonprofits portal (https://nonprofit.microsoft.com/) or has existing M365 licenses
- If using Google Workspace: client has activated Google for Nonprofits through TechSoup verification
- Client has provided admin credentials or will create dedicated service accounts for all existing platforms (CRM, email, website CMS) that need to connect to the automation workflow
- Client has budget approval for the estimated monthly recurring costs ($150–$300/month managed service) and one-time setup fee ($3,500–$5,000)
Installation Steps
Step 1: Discovery and Workflow Mapping Session
Conduct a 60–90 minute discovery session with the client's Volunteer Coordinator and any relevant stakeholders (Executive Director, HR/compliance lead). Document the current volunteer onboarding process step-by-step, identifying pain points, bottlenecks, and manual tasks. Map out the desired automated workflow on a whiteboard or diagramming tool. Identify the registration trigger source (existing web form, new portal, CRM entry), all onboarding steps to automate, required documents/forms, background check requirements, training requirements, and notification preferences. Produce a written Workflow Design Document for client sign-off before proceeding.
Use a template workflow design document. Key questions to ask: (1) Where do volunteers currently register? (2) What information do you collect at registration? (3) What documents must volunteers complete? (4) Do you require background checks? For which roles? (5) What training must volunteers complete before their first shift? (6) Who needs to be notified when a new volunteer registers? (7) How do you currently schedule orientations? (8) What is your current CRM/database? This step is critical — scope creep is the #1 risk. Get explicit sign-off on which steps are in-scope.
Step 2: Activate Nonprofit Software Discounts and Create Accounts
Before purchasing any software, activate all applicable nonprofit discount programs. This step can save the client thousands of dollars annually. Create accounts on all platforms in the selected stack. Use the client's nonprofit email domain for all account creation to maintain clean ownership. Create a shared credentials document (use the MSP's password manager, e.g., IT Glue or Hudu) for all service accounts.
Nonprofit Discount Activation Checklist
Account Creation Order
Create accounts in this sequence to enable integrations:
Allow 3–7 business days for TechSoup nonprofit verification. Microsoft and Google nonprofit programs can take 3–10 business days to approve. Start this step immediately after the discovery session to avoid delays. Some clients may already have TechSoup registration — check first. Document all account credentials in the MSP's documentation platform (IT Glue, Hudu, etc.) and share relevant login details with the client's Volunteer Coordinator via a secure method.
Step 3: Configure Bloomerang Volunteer Portal
Set up the Bloomerang Volunteer instance as the primary volunteer registration and management hub. Configure the volunteer registration form with all required fields mapped during discovery. Set up reusable form templates for different volunteer roles if applicable. Configure the built-in digital waivers and e-signature forms. Set up volunteer status workflow stages (Applicant → In Process → Accepted → Active → Inactive → Archived). Enable the mobile app for the Volunteer Coordinator. Configure notification preferences.
Bloomerang Volunteer's built-in e-signatures may be sufficient for most nonprofits, eliminating the need for a separate DocuSign subscription. Test the built-in e-signature functionality before procuring DocuSign. If the client has role-specific onboarding requirements (e.g., drivers need a DMV check, kitchen volunteers need food safety certification), create separate registration form templates for each role. Bloomerang charges based on accepted and inactive profile statuses — Applicant, In Process, and Archived profiles do not count toward the billing tier.
Step 4: Configure CRM Integration (HubSpot Free or Existing CRM)
Set up the CRM as the central constituent database. If the client uses HubSpot Free CRM, configure it from scratch. If they have an existing CRM (Salesforce NPSP, Bloomerang CRM), configure the integration endpoints. Create custom properties/fields for volunteer-specific data. Set up lifecycle stages and contact segmentation for volunteers vs. donors. Configure the CRM to accept data from the automation workflow.
HubSpot Free CRM Setup (if using HubSpot)
For Salesforce NPSP
- Create custom fields on Contact object
- Create a Campaign named 'Volunteer Onboarding [Year]'
- Use Campaign Member Status for tracking
- Ensure API access is enabled on the org (included in Enterprise edition)
HubSpot Free CRM is the recommended choice for nonprofits without an existing CRM because it supports unlimited users, 1M contacts, and has robust API access at no cost. If the client already has Salesforce with the free 10 NPSP licenses, use Salesforce instead — do not introduce a second CRM. The key requirement is that the CRM has API access or a Zapier connector for the automation to write data. Verify API access on the client's specific CRM plan before proceeding.
Step 5: Configure Zapier Professional Account and Connect Apps
Set up the Zapier Professional account as the central automation orchestration engine. Connect all application accounts via OAuth or API key authentication. Verify each connection with a test action. Organize connections into a folder structure for the client. Enable two-factor authentication on the Zapier account.
Zapier Account Setup
Connect Applications (My Apps Section)
Test Each Connection
Create Folder Structure
- Folder: 'Volunteer Onboarding'
- Zap: 'New Registration → Full Onboarding Workflow'
- Zap: 'Waiver Signed → Update Status'
- Zap: 'Background Check Complete → Update Status'
- Zap: 'Training Complete → Schedule Orientation'
Zapier Professional plan includes 750 tasks/month. For a nonprofit processing 50 new volunteers/month with an 8-step workflow, that consumes approximately 400 tasks/month, leaving headroom. If the client processes more than ~90 new volunteers/month, upgrade to Zapier Team plan ($103.50/month for 2,000 tasks). Each action in a multi-step Zap counts as one task. Monitor task usage in the first month and adjust the plan if needed. Always use a service account email (e.g., automation@nonprofitname.org) rather than a personal email for the Zapier account.
Step 6: Build the Primary Onboarding Automation Workflow (Zap)
Build the core multi-step Zap that triggers on new volunteer registration and executes the complete onboarding sequence. This is the heart of the implementation. Build it step-by-step, testing each action before adding the next. Use Zapier's built-in formatter actions for data transformation where needed.
Primary Zap: New Volunteer Registration → Complete Onboarding
Trigger
- App: Bloomerang Volunteer
- Event: New Volunteer Registration
- Alternative triggers: New Google Form Response, New HubSpot Contact, New Row in Google Sheet, Webhook
Action 1: Create/Update CRM Contact
- App: HubSpot (or Salesforce)
- Event: Create or Update Contact
Email ← {{trigger.email}}
First Name ← {{trigger.first_name}}
Last Name ← {{trigger.last_name}}
Phone ← {{trigger.phone}}
volunteer_status ← 'Applicant'
volunteer_registration_date ← {{trigger.registration_date}}
volunteer_source ← {{trigger.referral_source}}
volunteer_roles ← {{trigger.selected_roles}}Action 2: Send Welcome Email
- App: Gmail / Outlook / Mailchimp
- Event: Send Email
- To: {{trigger.email}}
- Subject: 'Welcome to [Org Name] Volunteers, {{trigger.first_name}}!'
- Body: Use HTML template — see custom_ai_components for full template
- From: volunteer@nonprofitname.org
Action 3: Send DocuSign Envelope (if using external e-sign)
- App: DocuSign
- Event: Create Signature Request
- Template: 'Volunteer Waiver and Code of Conduct'
- Recipient Email: {{trigger.email}}
- Recipient Name: {{trigger.first_name}} {{trigger.last_name}}
- Skip if using Bloomerang's built-in e-signatures
Action 4: Initiate Background Check (conditional)
- App: Filter by Zapier
- Condition: {{trigger.role}} contains 'Youth' OR 'Children' OR 'Senior'
- Only proceed if the volunteer's selected role requires screening
App: Sterling Volunteers (via webhook or API call)
Event: Initiate Background Check
Candidate Email: {{trigger.email}}
Check Type: Standard Volunteer ScreenAction 5: Send Training Link
- App: Gmail / Outlook
- Event: Send Email
- To: {{trigger.email}}
- Subject: 'Your Volunteer Training - Please Complete Before Your First Shift'
- Body: Link to Google Classroom / LMS / training video playlist
Action 6: Create Orientation Scheduling Link
- App: Calendly (or Formatter by Zapier to generate calendar link)
- Event: Create Single-Use Scheduling Link
- Event Type: 'Volunteer Orientation'
- Then email the link via a subsequent email action or include in the training email above
Action 7: Log to Google Sheet (audit trail)
- App: Google Sheets
- Event: Create Spreadsheet Row
- Spreadsheet: 'Volunteer Onboarding Log'
Columns: Date, Name, Email, Role, Waiver Status, BG Check Status,
Training Link Sent, Orientation ScheduledAction 8: Notify Staff via Slack or Teams
- App: Slack / Microsoft Teams
- Event: Send Channel Message
- Channel: #new-volunteers
🙋 New volunteer registered: {{trigger.first_name}} {{trigger.last_name}}
({{trigger.email}}) for role: {{trigger.selected_roles}}.
Onboarding workflow initiated.Build and test each action one at a time. Use Zapier's 'Test & Review' feature at each step. Common issues: (1) Field mapping mismatches — verify that field names in the trigger match exactly what the destination app expects. (2) Email sending limits — Gmail has a 500 emails/day limit; for high-volume orgs, use a transactional email service. (3) Conditional logic — use Zapier's built-in Filter or Paths feature for branching (e.g., background checks only for certain roles). (4) Error handling — enable Zapier's 'Auto Replay' for failed tasks and set up error notification emails to the MSP. The Zap should be built in test mode first, then activated only after all steps pass testing.
Step 7: Build Secondary Automation Workflows (Status Update Zaps)
Build supplementary Zaps that respond to downstream events and update the volunteer's onboarding status. These ensure the CRM and tracking spreadsheet reflect real-time progress through the onboarding pipeline.
Secondary Zap 1: Waiver Signed → Update CRM Status
Secondary Zap 2: Background Check Complete → Update CRM Status
Secondary Zap 3: All Onboarding Steps Complete → Mark Active
Secondary Zap 4: Orientation Booked → Update Calendar & CRM
Secondary Zaps consume additional tasks against the Zapier plan quota. With 4 secondary Zaps averaging 2–3 actions each, a single volunteer's complete onboarding journey consumes approximately 15–20 total Zapier tasks across all Zaps. For the 'All Steps Complete' Zap, using a scheduled trigger (polling) is simpler but less efficient than using HubSpot Workflows to detect when all conditions are met. If the client has HubSpot Marketing Hub Starter or higher, use HubSpot's native workflow feature for this specific Zap instead to save Zapier tasks.
Step 8: Configure Email Templates and Communication Sequences
Create and configure all email templates that the automation workflow will send. Each template should be branded with the nonprofit's logo, colors, and voice. Use merge fields for personalization. Ensure all emails comply with CAN-SPAM Act requirements (unsubscribe link, physical address, accurate sender information).
- Include organization's physical mailing address in footer of ALL templates
- Include unsubscribe/opt-out link in ALL templates
- Use accurate From name and email address in ALL templates
- Subject line must not be deceptive in ANY template
Have the client's marketing or communications staff review all email templates before activation to ensure they match the organization's brand voice and messaging guidelines. If the nonprofit has a graphic designer, provide them with the email template structure and let them supply branded HTML. For Mailchimp, use the drag-and-drop editor. For direct Gmail/Outlook sends via Zapier, use simple HTML templates. Test all emails by sending to yourself and checking rendering in Gmail, Outlook, Apple Mail, and mobile devices. Pay special attention to unsubscribe links — even nonprofit volunteer emails are subject to CAN-SPAM.
Step 9: Set Up Tracking Dashboard and Reporting
Create a real-time dashboard that allows the Volunteer Coordinator to monitor onboarding pipeline status at a glance. This can be done via Google Sheets (simple) or HubSpot dashboards (richer). The dashboard should show: total new registrations, pipeline stage distribution, average time-to-onboard, bottleneck identification, and completion rates.
Option A: Google Sheets Dashboard Setup
# COUNTIF formulas for pipeline status metrics
=COUNTIF('Onboarding Log'!F:F, "Applicant") -- Pending registrations
=COUNTIF('Onboarding Log'!H:H, "Signed") -- Waivers completed
=COUNTIF('Onboarding Log'!I:I, "Cleared") -- BG checks cleared
=COUNTIF('Onboarding Log'!L:L, "Yes") -- Fully onboarded
=AVERAGE(L2:L100 - A2:A100) -- Avg days to onboardOption B: HubSpot Dashboard Setup
The Google Sheets approach is recommended for simplicity and because it works with the free tier of all tools. HubSpot dashboards provide richer visualization but may require Marketing Hub Starter ($15/month) for some custom report types. For clients who want a more polished dashboard without additional cost, consider embedding a Google Sheets chart into a Google Sites page that the Volunteer Coordinator can bookmark. The dashboard is also critical for MSP reporting — it demonstrates the value of the automation to the client during quarterly business reviews.
Step 10: Configure Error Handling, Monitoring, and Alerts
Set up error handling within Zapier to catch and recover from failed automation runs. Configure monitoring alerts so both the MSP and the client's Volunteer Coordinator are notified of issues. This ensures no volunteer falls through the cracks due to a technical failure.
Zapier's built-in error handling is good but not perfect. The most common failure modes are: (1) OAuth token expiration — Zapier connections to HubSpot, Google, etc. can expire every 30–90 days; re-authenticate when this happens. (2) Rate limiting — if the client processes a large batch of registrations at once (e.g., after an event), API rate limits on downstream services may cause failures. (3) Data format mismatches — a volunteer enters an invalid email or phone format, causing the CRM action to fail. Add Zapier Formatter steps to validate/clean data before writing to CRM. The MSP should check the Zapier task history at least weekly during the first month and monthly thereafter.
Step 11: Security Hardening and Compliance Configuration
Implement security and compliance controls to protect volunteer PII (personally identifiable information). Configure role-based access, enable audit logging, set up data retention policies, and ensure all platforms meet baseline security requirements.
1. Enable Two-Factor Authentication (2FA) on ALL accounts
- Zapier: Settings > Security > Enable 2FA
- HubSpot: Settings > Security > Two-Factor Authentication
- Bloomerang: Account Settings > Security
- Google Workspace: Admin Console > Security > 2-Step Verification
- Microsoft 365: Admin Center > Active Users > MFA
- DocuSign: Account > Security Settings
2. Role-Based Access Control
- Zapier: Only MSP admin and client Volunteer Coordinator have access
- HubSpot: Create 'Volunteer Coordinator' permission set (contacts: read/write, reports: read)
- Bloomerang: Assign roles per user (Admin vs. Viewer)
- Limit who can view SSN/DOB fields (if collected)
3. Data Retention Policy
- Set Bloomerang to auto-archive inactive volunteers after 24 months
- Configure HubSpot data retention: delete contacts after 36 months of inactivity
- Google Sheets: add quarterly review reminder to purge old records
4. Privacy Policy
- Ensure client's privacy policy covers volunteer data collection
- Add privacy policy link to all registration forms
- Add explicit consent checkboxes for: data processing, email communications
5. Encryption Verification
- Verify all platforms use TLS 1.2+ (all recommended SaaS tools do)
- Verify API connections use HTTPS exclusively
- Check that no volunteer PII is stored in plaintext in Zapier logs
- In Zapier: Settings > Data Management > configure log retention
6. FCRA Compliance (Background Checks)
- Sterling Volunteers handles FCRA disclosure and authorization
- Client must NOT use background check results for non-authorized purposes
- Document adverse action procedures if a check returns negative results
Non-profit organizations are increasingly subject to data privacy regulations. Oregon's Consumer Privacy Act now fully applies to nonprofits as of July 2025. GDPR applies if the organization has EU-based volunteers. Even where regulations don't explicitly apply, following privacy best practices protects the client from liability and builds volunteer trust. Conduct a brief privacy impact assessment during implementation and flag any concerns to the client's leadership. If the client collects SSNs for background checks, ensure this data flows directly to Sterling Volunteers and is never stored in intermediate systems (Zapier, Google Sheets, etc.).
Step 12: User Acceptance Testing (UAT)
Conduct thorough end-to-end testing of the complete onboarding workflow before going live. Create test volunteer registrations and verify every step of the automation executes correctly. Test edge cases including duplicate registrations, missing fields, and role-based branching. Involve the client's Volunteer Coordinator in testing.
- Test Case 1: Happy Path - Standard Volunteer
- Test Case 2: Youth-Serving Role (Background Check Required)
- Test Case 3: No Background Check Required
- Test Case 4: Duplicate Registration
- Test Case 5: Missing/Invalid Data
- Test Case 6: Volume Test
Test Case 1: Happy Path - Standard Volunteer
Test Case 2: Youth-Serving Role (Background Check Required)
Test Case 3: No Background Check Required
Test Case 4: Duplicate Registration
Test Case 5: Missing/Invalid Data
Test Case 6: Volume Test
UAT should be performed jointly with the Volunteer Coordinator. Walk them through each test case and show them what is happening behind the scenes in Zapier, HubSpot, and Bloomerang. This serves double duty as training. Use email aliases (e.g., volunteertesting+case1@gmail.com) for test registrations so all test emails go to a single inbox. After UAT, purge all test records from the CRM, Google Sheet, and Bloomerang to ensure a clean production start. Document any issues found during UAT and their resolutions.
Step 13: Go-Live and Production Activation
After successful UAT, activate the automation workflow in production. Coordinate timing with the client — ideally launch on a Monday morning so the first week can be monitored closely. Turn on all Zaps, verify the registration form is publicly accessible, and monitor the first real volunteer registrations.
Go-Live Checklist
Pre-Launch (Day Before)
Launch Day
Post-Launch Monitoring (First Week)
Post-Launch Monitoring (First Month)
The first week after go-live is critical. MSP should plan for 2–3 hours of monitoring and adjustment time during this period. Common issues that surface after go-live: (1) Email deliverability — volunteer emails land in spam; add SPF/DKIM records for the sending domain. (2) Form field validation — real users find creative ways to break form inputs. (3) Timing expectations — client expects instant processing but some steps (background checks) take days. Set expectations upfront. Schedule a 30-day post-launch review meeting to assess performance and address any issues.
Custom AI Components
Volunteer Onboarding Master Workflow
Type: workflow The primary Zapier multi-step Zap that orchestrates the entire volunteer onboarding process. Triggered by a new volunteer registration in Bloomerang Volunteer, this workflow sequentially creates/updates the CRM contact, sends a branded welcome email, dispatches e-signature documents, conditionally initiates background checks, sends training materials, creates an orientation scheduling link, logs the event to a tracking spreadsheet, and notifies staff. Includes conditional branching for role-based background check requirements and error handling for failed steps.
Implementation:
Step 1 — Trigger
- App: Bloomerang Volunteer
- Trigger Event: New Volunteer Registration
- Account: [Client's Bloomerang account]
- Trigger Fields Available: first_name, last_name, email, phone, address, city, state, zip, date_of_birth, selected_roles, availability, referral_source, registration_date, custom_fields
Step 2 — Create/Update CRM Contact
- App: HubSpot
- Action Event: Create or Update Contact
- Search by: Email = {{1.email}}
Field Mapping:
Email: "{{1.email}}"
First Name: "{{1.first_name}}"
Last Name: "{{1.last_name}}"
Phone: "{{1.phone}}"
Street Address: "{{1.address}}"
City: "{{1.city}}"
State/Region: "{{1.state}}"
Zip Code: "{{1.zip}}"
volunteer_status: Applicant
volunteer_registration_date: "{{1.registration_date}}"
volunteer_roles: "{{1.selected_roles}}"
volunteer_source: "{{1.referral_source}}"
waiver_status: Not Sent
training_status: Not Started
background_check_status: Not RequiredStep 3 — Send Welcome Email
- App: Gmail (or Outlook)
- Action Event: Send Email
- From: volunteer@nonprofitname.org
- To: {{1.email}}
- Subject: Welcome to [Organization Name] Volunteers, {{1.first_name}}!
- Body Type: HTML
<!DOCTYPE html>
<html>
<head><meta charset='UTF-8'></head>
<body style='font-family: Arial, sans-serif; max-width: 600px; margin: 0 auto; padding: 20px;'>
<div style='text-align: center; padding: 20px 0;'>
<img src='[ORG_LOGO_URL]' alt='[Org Name]' style='max-width: 200px;'>
</div>
<h1 style='color: #2c3e50;'>Welcome, {{1.first_name}}! 🎉</h1>
<p>Thank you for signing up to volunteer with <strong>[Organization Name]</strong>! We're thrilled to have you join our team.</p>
<h2 style='color: #2c3e50;'>Here's What Happens Next:</h2>
<ol style='line-height: 2;'>
<li><strong>Complete Your Documents</strong> — You'll receive an email shortly with your volunteer waiver and code of conduct to sign electronically.</li>
<li><strong>Background Check</strong> — If your volunteer role requires it, we'll send you information about our screening process.</li>
<li><strong>Complete Your Training</strong> — We'll send you a link to our online volunteer training module.</li>
<li><strong>Schedule Your Orientation</strong> — Once your paperwork is complete, you'll be able to sign up for an orientation session.</li>
</ol>
<p>The entire process typically takes <strong>5-7 business days</strong>.</p>
<div style='background-color: #f0f7ff; border-left: 4px solid #3498db; padding: 15px; margin: 20px 0;'>
<strong>Questions?</strong><br>
Contact our Volunteer Coordinator:<br>
📧 [coordinator_email]<br>
📞 [coordinator_phone]
</div>
<p>We can't wait to see you in action!</p>
<p>Warm regards,<br><strong>[Volunteer Coordinator Name]</strong><br>Volunteer Coordinator, [Organization Name]</p>
<hr style='border: none; border-top: 1px solid #eee; margin: 30px 0;'>
<p style='font-size: 11px; color: #999;'>[Organization Name] | [Physical Address] | <a href='[UNSUBSCRIBE_URL]'>Unsubscribe</a> | <a href='[PRIVACY_POLICY_URL]'>Privacy Policy</a></p>
</body>
</html>Step 4 — Send E-Signature Request
- App: DocuSign
- Action Event: Create Signature Request from Template
- Template: 'Volunteer Waiver and Code of Conduct' (pre-configured in DocuSign)
- Recipient Email: {{1.email}}
- Recipient Name: {{1.first_name}} {{1.last_name}}
- Role: Signer 1
- Email Subject: 'Please Sign: Volunteer Documents for [Organization Name]'
- Email Body: 'Hi {{1.first_name}}, please review and sign the attached volunteer documents. This should take about 5 minutes.'
Step 5 — Update CRM (Waiver Sent)
- App: HubSpot
- Action Event: Update Contact
- Search by: Email = {{1.email}}
- Set: waiver_status = 'Sent'
Step 6 — Conditional: Check If Background Check Required
- App: Filter by Zapier
- Field: {{1.selected_roles}}
- Condition: (Text) Contains
- Value: Youth|Children|Minor|Senior|Elder|Vulnerable|Driver
- Continue only if true — if the role involves vulnerable populations
Step 7 — Initiate Background Check (Conditional)
- App: Webhooks by Zapier
- Action Event: POST
- URL: https://api.sterlingvolunteers.com/v2/checks (or Sterling's integration endpoint)
# Headers: Authorization: Bearer [STERLING_API_KEY], Content-Type:
# application/json
{
"candidate": {
"first_name": "{{1.first_name}}",
"last_name": "{{1.last_name}}",
"email": "{{1.email}}",
"date_of_birth": "{{1.date_of_birth}}"
},
"package": "standard_volunteer",
"organization_id": "[ORG_STERLING_ID]"
}If Sterling doesn't have a direct API, use their portal integration with Bloomerang instead and skip this Zapier step.
Step 8 — Update CRM (Background Check Initiated)
- App: HubSpot
- Action Event: Update Contact
- Search by: Email = {{1.email}}
- Set: background_check_status = 'Pending'
Step 9 — Send Training Assignment Email
- App: Gmail (or Outlook)
- Action Event: Send Email
- To: {{1.email}}
- Subject: Your Volunteer Training — Please Complete Before Your First Shift
- Body Type: HTML
<body style='font-family: Arial, sans-serif; max-width: 600px; margin: 0 auto; padding: 20px;'>
<h1 style='color: #2c3e50;'>Hi {{1.first_name}}, Your Training is Ready!</h1>
<p>To prepare for your volunteer role, please complete the following training:</p>
<div style='background-color: #e8f5e9; padding: 20px; border-radius: 8px; margin: 20px 0; text-align: center;'>
<a href='[TRAINING_URL]' style='display: inline-block; background-color: #27ae60; color: white; padding: 15px 30px; text-decoration: none; border-radius: 5px; font-size: 18px;'>Start Your Training</a>
</div>
<p><strong>Estimated time:</strong> 30-45 minutes<br>
<strong>Deadline:</strong> Please complete within 7 days</p>
<p>Topics covered:</p>
<ul>
<li>Organization mission and values</li>
<li>Volunteer policies and expectations</li>
<li>Safety procedures</li>
<li>Role-specific guidelines</li>
</ul>
<hr style='border: none; border-top: 1px solid #eee; margin: 30px 0;'>
<p style='font-size: 11px; color: #999;'>[Organization Name] | [Address] | <a href='[UNSUBSCRIBE_URL]'>Unsubscribe</a></p>
</body>Step 10 — Send Orientation Scheduling Link
- App: Gmail (or Outlook)
- Action Event: Send Email
- To: {{1.email}}
- Subject: Schedule Your Volunteer Orientation
- Body (HTML): Include Calendly link: [CALENDLY_ORIENTATION_URL]
- Delay: Use Zapier Delay step — wait 2 days (allows time to complete docs/training first)
Step 11 — Log to Google Sheet
- App: Google Sheets
- Action Event: Create Spreadsheet Row
- Spreadsheet: 'Volunteer Onboarding Log [Year]'
- Worksheet: 'Log'
Columns:
Registration Date: "{{1.registration_date}}"
First Name: "{{1.first_name}}"
Last Name: "{{1.last_name}}"
Email: "{{1.email}}"
Phone: "{{1.phone}}"
Roles: "{{1.selected_roles}}"
Welcome Email: Sent
Waiver Status: Sent
BG Check Status: "{{Step 6 filter result ? 'Initiated' : 'Not Required'}}"
Training Link Sent: Yes
Orientation Scheduled: Pending
Fully Onboarded: NoStep 12 — Notify Staff
- App: Microsoft Teams (or Slack)
- Action Event: Send Channel Message
- Team: [Org's Team]
- Channel: #new-volunteers (or 'Volunteer Coordination')
🙋 **New Volunteer Registered**
**Name:** {{1.first_name}} {{1.last_name}}
**Email:** {{1.email}}
**Role(s):** {{1.selected_roles}}
**Status:** Onboarding workflow initiated — welcome email sent, documents dispatched.
_All automated steps are in progress. No action needed unless flagged._Error Handling
- Enable Auto Replay on all steps
- If any step fails, Zapier will retry automatically
- Zapier Manager error notification Zap sends alert to MSP support email
Onboarding Status Tracker Workflow
Type: workflow A secondary Zapier workflow that monitors for completed onboarding milestones (waiver signed, background check cleared, training completed) and updates the CRM contact record and tracking spreadsheet accordingly. When all required milestones are met, it automatically marks the volunteer as 'Active' and sends a congratulatory email.
Implementation
OPTION A: Scheduled Polling Approach (Works with HubSpot Free)
ZAP: 'Check for Fully Onboarded Volunteers'
STEP 1 – TRIGGER
- App: Schedule by Zapier
- Trigger Event: Every Hour
- Day of Week: Monday through Friday
- Time Range: 8:00 AM - 6:00 PM (client's timezone)
STEP 2 – SEARCH CRM FOR READY VOLUNTEERS
- App: HubSpot
- Action Event: Find Contact
- Search Criteria: waiver_status = 'Signed'
- Search Criteria: training_status = 'Completed'
- Search Criteria: AND (background_check_status = 'Cleared' OR background_check_status = 'Not Required')
- Search Criteria: AND volunteer_status != 'Active'
- Search Criteria: AND volunteer_status != 'Inactive'
STEP 3 – UPDATE CONTACT TO ACTIVE
- App: HubSpot
- Action Event: Update Contact
- Contact: {{2.id}}
- Set: volunteer_status = 'Active'
STEP 4 – SEND COMPLETION EMAIL
- App: Gmail / Outlook
- Action Event: Send Email
- To: {{2.email}}
- Subject: 'You\'re All Set, {{2.first_name}}! Welcome to the Team! 🎉'
<body style='font-family: Arial, sans-serif; max-width: 600px; margin: 0 auto; padding: 20px;'>
<h1 style='color: #27ae60;'>Congratulations, {{2.first_name}}! 🎉</h1>
<p>You've completed all onboarding steps and are officially an <strong>active volunteer</strong> with [Organization Name]!</p>
<h2>What's Next?</h2>
<div style='background-color: #f0f7ff; padding: 20px; border-radius: 8px; margin: 20px 0;'>
<p><strong>Sign up for your first shift:</strong></p>
<a href='[VOLUNTEER_PORTAL_URL]' style='display: inline-block; background-color: #3498db; color: white; padding: 12px 24px; text-decoration: none; border-radius: 5px;'>View Available Opportunities</a>
</div>
<p><strong>Key Resources:</strong></p>
<ul>
<li><a href='[PORTAL_URL]'>Volunteer Portal</a> — Sign up for shifts and track hours</li>
<li><a href='[HANDBOOK_URL]'>Volunteer Handbook</a> — Policies and procedures</li>
<li><a href='[CALENDAR_URL]'>Events Calendar</a> — Upcoming opportunities</li>
</ul>
<p>Questions? Reach out anytime to [Coordinator Name] at [coordinator_email].</p>
<p>Thank you for giving your time — it makes a real difference!</p>
</body>STEP 5 – UPDATE GOOGLE SHEET
- App: Google Sheets
- Action Event: Update Spreadsheet Row (Lookup by email)
- Set: 'Fully Onboarded' column = 'Yes'
- Set: 'Onboarding Completed Date' = {{zap_meta_human_now}}
STEP 6 – NOTIFY COORDINATOR
- App: Microsoft Teams / Slack
- Action Event: Send Channel Message
- Channel: #new-volunteers
- Message: '✅ Volunteer Fully Onboarded: {{2.first_name}} {{2.last_name}} ({{2.email}}) has completed all onboarding steps and is now Active. They can be scheduled for shifts.'
OPTION B: Event-Driven Approach (Separate Zaps per Milestone)
ZAP 2A: 'DocuSign Waiver Completed'
- TRIGGER: DocuSign → Envelope Completed
- ACTION 1: HubSpot → Update Contact → waiver_status = 'Signed'
- ACTION 2: Google Sheets → Update Row → Waiver Status = 'Signed'
ZAP 2B: 'Background Check Completed'
- TRIGGER: Webhook → POST from Sterling callback URL
- ACTION 1: Parse JSON result → extract status and candidate email
- ACTION 2: HubSpot → Update Contact → background_check_status = result_status
- ACTION 3: IF status = 'CLEAR': no additional action
- ACTION 3 ALT: IF status = 'CONSIDER' or 'FAIL': Send alert email to coordinator
ZAP 2C: 'Training Completed' (Manual or LMS trigger)
- TRIGGER: Google Forms → New Response (training completion form) OR: Webhook from LMS
- ACTION: HubSpot → Update Contact → training_status = 'Completed'
Incomplete Onboarding Reminder Workflow
Type: workflow An automated follow-up workflow that identifies volunteers who have started but not completed their onboarding steps after 3 days and 7 days, sending targeted reminder emails listing their specific outstanding items. Prevents volunteer drop-off during the onboarding process.
Implementation
STEP 1 – TRIGGER
- App: Schedule by Zapier
- Trigger Event: Every Day at 9:00 AM
STEP 2 – SEARCH FOR STALLED VOLUNTEERS
- App: Google Sheets
- Action Event: Lookup Spreadsheet Rows
- Spreadsheet: 'Volunteer Onboarding Log'
- Lookup Column: 'Fully Onboarded'
- Lookup Value: 'No'
STEP 3 – FILTER
- App: Filter by Zapier
- Condition: Registration Date is before 3 days ago AND Fully Onboarded = 'No'
STEP 4 – DETERMINE OUTSTANDING ITEMS
- App: Code by Zapier (JavaScript)
- Input Variables: waiver_status: {{2.waiver_status}}, bg_check_status: {{2.bg_check_status}}, training_status: {{2.training_status}}, orientation_scheduled: {{2.orientation_scheduled}}
// Builds the list of outstanding onboarding items
let outstanding = [];
if (inputData.waiver_status !== 'Signed') {
outstanding.push('📝 Sign your volunteer waiver and code of conduct');
}
if (inputData.bg_check_status === 'Pending') {
outstanding.push('🔍 Background check is still in progress (no action needed from you)');
}
if (inputData.training_status !== 'Completed') {
outstanding.push('📚 Complete your volunteer training module');
}
if (inputData.orientation_scheduled !== 'Yes') {
outstanding.push('📅 Schedule your volunteer orientation');
}
let outstandingList = outstanding.join('<br>');
let count = outstanding.length;
output = [{outstanding_items: outstandingList, item_count: count}];STEP 5 – FILTER (Only send if there are outstanding items)
- App: Filter by Zapier
- Condition: {{4.item_count}} is greater than 0
STEP 6 – SEND REMINDER EMAIL
- App: Gmail / Outlook
- To: {{2.email}}
- Subject: 'Friendly Reminder: Complete Your Volunteer Onboarding, {{2.first_name}}'
<body style='font-family: Arial, sans-serif; max-width: 600px; margin: 0 auto; padding: 20px;'>
<h1 style='color: #2c3e50;'>Hi {{2.first_name}},</h1>
<p>We noticed you haven't quite finished your volunteer onboarding with [Organization Name]. We'd love to get you started — here's what's still outstanding:</p>
<div style='background-color: #fff3cd; padding: 20px; border-radius: 8px; border-left: 4px solid #ffc107; margin: 20px 0;'>
{{4.outstanding_items}}
</div>
<p>Need help? Just reply to this email or contact [Coordinator Name] at [coordinator_phone].</p>
<p>We appreciate your commitment to our mission!</p>
<hr style='border: none; border-top: 1px solid #eee;'>
<p style='font-size: 11px; color: #999;'>[Organization Name] | [Address] | <a href='[UNSUBSCRIBE_URL]'>Unsubscribe</a></p>
</body>7-Day Escalation
To prevent sending reminders to the same volunteer every day, add a 'Last Reminder Sent' column to the Google Sheet and update it when a reminder is sent. Filter the search to only include volunteers where Last Reminder Sent is blank or > 3 days ago.
Volunteer Onboarding Data Sync Integration
Type: integration A bidirectional data synchronization integration between Bloomerang Volunteer and HubSpot CRM that ensures volunteer records are consistent across both platforms. When a volunteer's status changes in Bloomerang (e.g., documents completed, status updated), the change is reflected in HubSpot, and vice versa. This integration uses Zapier as the middleware layer.
Implementation
ZAP A: Bloomerang → HubSpot (Volunteer record changes)
Step 1 – Trigger
- App: Bloomerang Volunteer
- Event: Updated Volunteer Record
- If Bloomerang doesn't support an 'Updated' trigger, use a webhook or scheduled poll
Step 2 – Find HubSpot Contact
- App: HubSpot
- Action: Find Contact by Email
- Email: {{1.email}}
Step 3 – Update HubSpot Contact
- App: HubSpot
- Action: Update Contact
- Field Mapping: volunteer_status ← {{1.bloomerang_status}} (map: Applicant→Applicant, Accepted→Accepted, Active→Active, etc.)
- Field Mapping: phone ← {{1.phone}} (if updated)
- Field Mapping: address fields ← {{1.address fields}} (if updated)
ZAP B: HubSpot → Bloomerang (Coordinator updates in CRM)
Step 1 – Trigger
- App: HubSpot
- Event: Contact Property Changed
- Property: volunteer_status
Step 2 – Find Bloomerang Volunteer
- App: Bloomerang Volunteer API (via Webhooks by Zapier)
- Method: GET
GET https://api.bloomerang.co/v2/volunteers?email={{1.email}}
Authorization: Bearer [BLOOMERANG_API_KEY]Step 3 – Update Bloomerang
- App: Webhooks by Zapier
- Method: PUT
PUT https://api.bloomerang.co/v2/volunteers/{{2.volunteer_id}}
{ "status": "{{1.volunteer_status}}" }Deduplication Guard
To prevent infinite sync loops (A updates B, B triggers update to A, A triggers update to B...), follow these steps:
This prevents circular updates. The 'last_sync_source' field acts as a flag to indicate which system made the most recent change.
If Bloomerang's native Zapier integration doesn't support the 'Updated Record' trigger, use Bloomerang's REST API with a polling webhook via Zapier's Schedule trigger (check every 15 minutes for recently modified records).
If using Bloomerang's built-in CRM (Bloomerang Fundraising), the bidirectional sync is native — no Zapier integration needed for this step.
If using Salesforce NPSP instead of HubSpot, replace all HubSpot actions with Salesforce equivalents (Update Contact, SOQL query for lookup).
Testing & Validation
Client Handoff
The client handoff meeting should be a 90-minute session with the Volunteer Coordinator and at least one backup administrator. Cover the following topics:
All training should be recorded (with permission) so the client can reference it later. Schedule a 30-day follow-up meeting to review performance metrics and address any issues.
Maintenance
Weekly Maintenance (15-20 minutes per client)
- Review Zapier Task History for failed or held tasks. Replay any failed tasks and investigate root causes. Check task quota usage and trend.
- Verify all Zaps are in 'ON' status (Zaps can be paused by Zapier if errors accumulate).
- Spot-check the Google Sheet onboarding log for data integrity (no missing rows, no incorrectly blank fields).
Monthly Maintenance (1-2 hours per client)
- Review onboarding pipeline metrics: registrations vs. completions, average time-to-onboard, drop-off points.
- Re-authenticate any expired OAuth connections (HubSpot, Google, DocuSign connections typically need re-auth every 60-90 days).
- Review Zapier plan usage and recommend tier changes if task consumption is consistently >80% or <30% of quota.
- Check for Zapier app updates — connected app integrations occasionally change their available triggers/actions.
- Review email deliverability: check bounce rates and spam complaint rates.
- Apply any client-requested changes to email templates, form fields, or workflow logic (up to 2 modifications included in managed service).
Quarterly Maintenance (2-3 hours per client)
- Conduct a Quarterly Business Review (QBR) with the Volunteer Coordinator. Present onboarding metrics, demonstrate ROI (time saved, completion rates), identify improvement opportunities.
- Review and update the Workflow Design Document if any changes were made.
- Audit security: verify 2FA is still enabled on all accounts, review user access lists, check for any inactive admin accounts that should be removed.
- Review data retention: archive or delete old volunteer records per the retention policy (24-36 months).
- Test the complete workflow end-to-end (submit a test registration and verify all steps execute).
- Review vendor pricing changes and nonprofit discount renewals.
Annual Maintenance
- Renew all software subscriptions and verify nonprofit discount eligibility is current.
- Review the entire technology stack for potential improvements or consolidation.
- Assess whether the client has outgrown the current Zapier plan or VMS tier.
- Re-evaluate background check provider pricing and contract terms.
- Update training documentation and re-train staff if there has been turnover in the Volunteer Coordinator role.
Escalation Path
SLA Targets
- Workflow uptime: 99.5% (measured by successful Zap execution rate)
- Issue response time: 4 business hours
- Issue resolution time: 1 business day (standard), 3 business days (complex)
- Maximum acceptable task failure rate: <2% per month
Alternatives
Microsoft Power Automate Stack (Zero Automation Platform Cost)
Replace Zapier with Microsoft Power Automate, which is included free in Microsoft 365 Business Basic donated licenses (up to 300 seats for eligible nonprofits). Pair with Microsoft Volunteer Management built on Power Apps (free for up to 10 seats for nonprofits) as the VMS, and Dynamics 365 or Dataverse as the data backend. Use SharePoint for document management, Outlook for email, and Teams for notifications. The entire automation layer runs at $0 additional cost beyond the donated M365 licenses.
n8n Self-Hosted (Maximum MSP Margin)
Deploy n8n Community Edition on a shared MSP-managed VPS (DigitalOcean or AWS). n8n is a free, open-source workflow automation tool with a visual editor similar to Zapier/Make. Pair with HubSpot Free CRM and Google Workspace for Nonprofits (free). The MSP hosts and manages the n8n instance, charging the client a monthly managed service fee. A single VPS can host automation workflows for 10–20 nonprofit clients, making per-client marginal cost extremely low.
Make.com (formerly Integromat) — Best Value Complex Workflows
Replace Zapier with Make.com as the automation orchestration engine. Make uses a visual scenario builder with more granular control over data flow, branching, iteration, and error handling than Zapier. Its pricing is operation-based rather than task-based, which can be 50–70% cheaper than Zapier for equivalent workflow volumes. The rest of the stack (Bloomerang, HubSpot, DocuSign, etc.) remains the same.
When to recommend Make.com: Client has complex onboarding requirements with multiple role-based branches, the MSP team is comfortable with Make's interface, or cost optimization is a priority. Also recommended when Zapier's 750-task quota is insufficient but the client wants to avoid Zapier's expensive Team plan jump to $103.50/month.
Bloomerang Volunteer All-in-One (Minimal Integration)
Maximize the use of Bloomerang Volunteer's built-in capabilities to reduce the number of external integrations. Bloomerang includes built-in registration forms, digital waivers with e-signatures, built-in background checks (via Sterling partnership), communication and messaging tools, AI-powered scheduling, and a mobile app. This approach minimizes the automation engine's role to primarily CRM sync and staff notifications, rather than orchestrating every onboarding step.
When to recommend: Small nonprofit with straightforward onboarding requirements, limited technical sophistication, tight budget, and preference for a single platform. Best for organizations with fewer than 200 volunteers/year where simplicity is valued over customization. Not recommended if the client needs complex conditional branching, multi-channel communication sequences, or deep CRM integration.
Salesforce Nonprofit Cloud + Flow (Enterprise Scale)
For larger nonprofits already on Salesforce, use Salesforce Flow (built-in process automation) instead of Zapier to orchestrate the onboarding workflow entirely within the Salesforce ecosystem. Leverage Salesforce Nonprofit Cloud's native volunteer management features (events, roles, shifts, applications) combined with Flow's record-triggered automations, screen flows for intake, and scheduled flows for reminders. Use Salesforce Experience Cloud for a volunteer portal.
Want early access to the full toolkit?