Setup Time: 20 minutes | Difficulty: Medium | HubSpot Plan: Professional+
Requires: WhatsApp Business API (WABA)
Requires: WhatsApp Business API (WABA)
The Problem
Your team manually sends the same follow-up messages over and over:- “Thanks for booking a demo!”
- “Following up on the proposal…”
- “Your order has shipped!”
The Solution
HubSpot workflows automatically trigger WhatsApp messages when events occur.
Prerequisites
Before starting:- ✅ WABA connected to Eazybe
- ✅ Message templates approved by Meta
- ✅ HubSpot Professional or Enterprise plan
- ✅ Workflow permissions in HubSpot
Step-by-Step Setup
Part 1: Create Message Template
Create New Template
Click + New Template
- Name:
demo_followup(lowercase, underscores only) - Category: Utility or Marketing
- Language: English (or your language)

Write Template with Variables
Use variables that will map to HubSpot properties:Variable mapping:
{{1}}→ Contact First Name{{2}}→ Meeting Owner Name{{3}}→ Company Name{{4}}→ Meeting Date{{5}}→ Meeting Time

Part 2: Create HubSpot Workflow
Create New Workflow
Click Create workflow → From scratchChoose object type:
- Contact-based - For individual follow-ups
- Deal-based - For deal stage changes
- Ticket-based - For support workflows

Set Enrollment Trigger
Choose what triggers the workflow:Example: Demo Booked
Other common triggers:

- Deal stage changed
- Form submitted
- Property changed
- List membership
Configure WhatsApp Action
In the Eazybe action panel:
Variable Mapping:
- Select Template: Choose your approved template
- Map Variables: Connect HubSpot properties to template variables
- Select Sender: Choose which WABA number sends the message

| Template Variable | HubSpot Property |
|---|---|
| Contact: First name | |
| Contact owner: Name | |
| Company: Name | |
| Meeting: Start date | |
| Meeting: Start time |
Add Delay (Optional)
Add a delay before sending:
- Immediately - Send right away
- Delay - Wait X hours/days
- Specific time - Send at set time

Video Walkthrough
Common Workflow Examples
1. Demo Confirmation
Template:Hi , confirming your demo tomorrow at . Reply YES to confirm or let me know if you need to reschedule.
2. Proposal Follow-up
Template:Hi , following up on the proposal I sent for . Happy to answer any questions or walk through the pricing together.
3. Won Deal Thank You
Template:Great news ! 🎉 Welcome to the family. Our onboarding team will reach out within 24 hours to get you started.
What It Looks Like
In HubSpot Workflow History

On Contact Timeline

Best Practices
Always add fallback values
Always add fallback values
If a HubSpot property is empty, the variable shows blank. Add fallbacks:
- Use HubSpot’s “default value” option
- Or add if/then branch to skip contacts with missing data
Don't over-automate
Don't over-automate
Limit to 2-3 automated messages per contact. After that, human touch matters more.
Test before activating
Test before activating
Use HubSpot’s “Test” feature with a sample contact (yourself) before going live.
Monitor delivery rates
Monitor delivery rates
Check Eazybe analytics for failed messages. Common issues: invalid numbers, opted-out contacts.
Troubleshooting
Workflow not triggering?
Workflow not triggering?
- Check enrollment criteria is met
- Verify contact isn’t already enrolled (check re-enrollment settings)
- Check workflow is active
- Review workflow history for errors
WhatsApp not sending?
WhatsApp not sending?
- Verify WABA is connected
- Check template is approved (not pending/rejected)
- Ensure contact has valid phone number
- Check Eazybe action configuration
Variables showing blank?
Variables showing blank?
HubSpot property is empty for that contact. Either:
- Add default value in variable mapping
- Add workflow branch to check property exists first
Wrong number receiving message?
Wrong number receiving message?
Check which phone property is mapped. HubSpot contacts can have multiple phone fields.




