Send a text from your workflow
Select a connected Twilio sender and enter the SMS body. Use an SMS-capable phone number when you want recipients to reply; an alphanumeric sender cannot receive replies.
Send the follow-up automatically. Handle the reply in HubSpot.
Add Twilio SMS and approved WhatsApp templates to contact-based HubSpot workflows. Configure the sending channel and message, then handle incoming replies through its connected HubSpot inbox.
- Twilio SMS + WhatsApp templates
- Contact-based workflows
- Template variables + media headers
The practical answer
Can HubSpot workflows send SMS and WhatsApp through Octopods?
Octopods provides two actions: Send SMS via Octopods and Send WhatsApp Template Message. Select a channel connected to your HubSpot workspace and configure the message. SMS uses the text you enter; the WhatsApp action uses an approved, active template and its required values.
From form to follow-up
A contact submits your form
Use your HubSpot enrollment criteria
Check consent & contact details
Your enrollment and suppression rules
Choose an Octopods message action
Send SMS
Connected Twilio number
Send WhatsApp
Approved template
Continue the conversation in HubSpot
Your team picks up customer replies
Use the right WhatsApp template
Choose an approved, active template for the connected WhatsApp Business Platform number. Fill its variable fields and provide a Header Media URL when its header requires an image, video or document.
Give replies a human destination
Connect the sending channel to HubSpot so your team can answer incoming messages. Plan who handles replies before publishing the workflow.
Example workflows to configure
Useful messages, tied to a real customer moment.
HubSpot controls enrollment and timing. These examples use message content you configure in the action; they are not prebuilt automations or a promise of automatic contact-property personalization.
Form submitted → confirmation SMS
Use a form submission as the enrollment condition. Send a configured confirmation such as “Thanks for your request. Reply here if you have a question.”
Follow-up due → check-in SMS
Use your contact-based enrollment and delay settings to send a short, configured follow-up. Choose a reply-capable number and agree who will handle responses.
Eligible contact → WhatsApp template
Select an approved template and enter the required values. Check that the content, recipient permission and timing fit the customer interaction before enabling enrollment.
Your next three steps
Prepare the channel and contact
Connect Twilio or WhatsApp Business Platform to Octopods and a HubSpot inbox. Use a test contact with a valid phone number, or an existing WhatsApp identity already linked by Octopods.
Add an Octopods action
Open a contact-based workflow in HubSpot and look for the SMS or WhatsApp action. Confirm it is available for your installed app, then select the sender and configure its fields.
Test delivery, then publish
Run the action for a test contact. Review its execution result, confirm receipt on the destination phone and send a reply. An action success alone does not prove customer delivery.
Before you connect
Give every automated send the right starting point.
The right HubSpot access
Your HubSpot plan must include the workflow features you use, and the installed Octopods app must expose the action. The sending channel must also be connected to a HubSpot inbox.
A reachable contact
SMS needs a valid Mobile phone number or Phone number on the contact. WhatsApp can also use a WhatsApp identity that Octopods already has linked to that contact. Configure enrollment, consent and suppression rules in HubSpot.
Channel-specific content
Use an active, approved WhatsApp template or a connected Twilio SMS sender. Fill required template values and media fields. Channel restrictions and provider charges still apply.
A few useful answers
Your workflow questions, answered.
Have a setup that needs a closer look?
Talk it through with our teamUse a contact-based workflow with a form submission as its enrollment condition, then add Send SMS via Octopods. Configure the message text and check the contact’s number and messaging permission before testing the action.
No. This action sends approved, active WhatsApp templates. Choose a template for the connected number and fill its required values. Free-form WhatsApp text is not part of this workflow action.
The action exposes up to eight body variables, one text-header variable, one button variable, and a Header Media URL for image, video or document headers. Select a template whose requirements fit those fields.
The current action configuration supports values entered in its message and template fields. Do not build around automatic contact-property mapping without checking the installed action in your portal and testing the resolved message.
These actions are configured for contact-based HubSpot workflows. This page does not describe sales sequences or actions enrolled directly on deals, companies, tickets or other objects.
An SMS action fails when it cannot resolve a valid contact phone number. WhatsApp can use an identity that Octopods has already linked to the HubSpot contact; without a usable phone number or linked identity, that action also fails.
No. Review the action result for send errors, then confirm delivery through the channel’s delivery information or a real recipient test. The workflow response is not a final delivered or read receipt.
Yes. Octopods Proactive Cards provide manual SMS and WhatsApp template sends from a HubSpot contact record. The channel must be connected and the recipient must be reachable.
Successful workflow sends are recorded as Octopods messaging usage. Your HubSpot subscription and channel provider charges also apply. Review your Octopods plan and provider rates when budgeting.
Go deeper
Read the setup details
Keep exploring
Find your next answer
Make messaging part of your workflow
Build one follow-up your customers will appreciate.
Choose a contact-based workflow, configure a useful message and test the send and reply path before enrolling customers.