Send SMS from a workflow
HighLevel workflow Send SMS steps route through your Telnyx number automatically once Phone Clover is your SMS provider.
For admins · Updated Sep 23, 2026
All guides
If you already use HighLevel workflows to text contacts automatically, for example after a form submission or a tag being added, you do not need to change anything about how those workflows are built. Once Phone Clover is switched on as your native SMS provider, the workflow’s Send SMS step routes through your Telnyx number the same way a text sent by hand from Conversations does.
Before you start
- Who can do this: an admin or anyone with workflow-building access in HighLevel.
- What it needs: Phone Clover switched on as your sub-account’s native SMS provider. See Turn on Telnyx as your native SMS provider.
- US business texting also needs A2P 10DLC registration on the sending number. See Register for A2P 10DLC.
How it works
Build your workflow in HighLevel’s own workflow editor as usual, using the Send SMS action step. Once the native SMS provider is on, HighLevel hands that send to Phone Clover instead of its default carrier, using the same default number (or contact-assigned number) that a text sent from Conversations would use. There is no separate “Telnyx” action to add and no extra configuration inside the workflow step itself.
Note: because the routing happens at the provider level, a workflow built before you turned on the native SMS provider will automatically start sending over Telnyx the moment the provider switch is on. There’s no need to rebuild or republish existing workflows.
Things worth checking before relying on automated sends
- Registration status. An unregistered number can have automated texts filtered or delayed by carriers, especially in a workflow that sends to many contacts close together. Confirm A2P 10DLC status on Settings → Overview before turning on a high-volume automated workflow. See What the settings health badges mean.
- Number health. A workflow that sends frequently is exactly the kind of traffic that can get a number flagged if there’s an underlying deliverability problem. Check Number health radar periodically if you run automated texting at volume.
- Firewall rules. Phone Clover’s spam filtering applies to inbound replies the same way it does for manually sent texts, so a workflow that expects a reply back should behave the same as any other conversation. See SMS firewall: block and allow lists.
Troubleshooting
Workflow texts aren’t sending at all. Confirm the native SMS provider is switched on for this sub-account; a workflow’s Send SMS step still needs an active provider behind it, same as a manual text. See Turn on Telnyx as your native SMS provider.
Some contacts in a workflow get the text and others don’t. Check Why texts fail and what the reasons mean for the affected contacts. Common causes include a landline number, a contact who previously opted out, or a carrier content filter on the specific message.
A workflow sends to a large list and I’m worried about carrier limits. Treat a large automated send the same as a bulk send. See Send bulk SMS for the same sending-limit considerations, since carriers do not distinguish a workflow-triggered text from a manually sent bulk text.
I changed the number a workflow sends from and now nothing’s going out. Confirm the new number is connected, enabled, and registered for texting in Settings → Numbers. A number that exists in your account but is not yet enabled will not send. See Set up your first number.