Comprehensive Hubspot Walkthrough
Last updated: April 12, 2026
Last Updated: April 12, 2026
Customer-Facing Guide
Overview
This guide is the practical “build it end to end” version of the HubSpot + Sendblue workflow setup. Use it when HubSpot is the system deciding who should enter a Sendblue workflow and when that should happen.
What this walkthrough should help you build
A HubSpot-triggered Sendblue workflow that enrolls the right contacts.
Clean data handoff from HubSpot into Sendblue.
The right sending number / sender logic.
A reply-aware workflow instead of a “fire and forget” sequence.
A test plan so you can validate the setup before trusting it on real traffic.
Recommended build order
Connect HubSpot to Sendblue and confirm the integration is live.
Decide what exact HubSpot event should start the workflow (new lead, booked appointment, tag/field change, etc.).
Make sure the contact fields you need are actually available at enrollment time — especially phone number, first name, owner/sender, and any personalization tokens.
Choose the correct sending number or sender logic before you write the messages.
Build the Sendblue workflow steps: first message, waits/delays, reply handling, and exits.
Test with a real contact record instead of assuming the mapping is correct.
The 4 things that usually break first
| Symptom | What to check first | Best next move |
|---|---|---|
| The contact never appears in Sendblue | HubSpot trigger / enrollment logic | Confirm the contact actually met the HubSpot conditions and that the integration passed the event through. |
| The contact enrolled, but no message was created | Workflow path / timing / branch logic | Review the Sendblue workflow step order, delays, and conditions. |
| The message was created but did not send | From number, timing rules, or delivery path | Check sending number, sending hours, and delivery/configuration guides next. |
| The message sent with blank or wrong personalization | Field mapping timing | Confirm the source HubSpot field was populated before enrollment and available to Sendblue at step runtime. |
A good first test
Create or pick a realistic test contact in HubSpot.
Trigger the exact HubSpot event that should start the workflow.
Check that the contact enrolls into Sendblue.
Confirm the workflow uses the correct sender / from number.
Confirm the first message is created and appears in the expected conversation.
Reply from the test contact and verify your response-handling or stop logic behaves correctly.
Common mistakes
Debugging delivery before confirming the HubSpot event reached Sendblue at all.
Using the wrong sending number or leaving sender logic too ambiguous.
Relying on personalization fields that are not populated yet when the workflow fires.
Building the first send, but forgetting to define what happens after a reply or non-reply.