I have the number list formatted like " 1xxxxxxxxxx, 1xxxxxxxxxx, 1xxxxxxxxxx, 1xxxxxxxxxx" and I’m getting “Send SMS message: {“code”: 21211, “message”: “Invalid ‘To’ Phone Number”, “more_info”: “Invalid 'To' Phone Number | Twilio”, “status”: 400}”
You should be able to use the Twilio integration. You can probably also use the new API action to do that too.
This is a related thread on StackOverflow. What I understand is you must have multiple ToBinding objects, which might not be natively possible with the Glide Twilio integration.
I’m not sure if you can present those --data-urlencode parts in the Call API action.
What I usually use for this is Make.com, send a webhook payload with the list of numbers and the message, then iterate over the array of numbers to send.
1 Like
I am also trying to figure this out.
I really like the Twilio integration as it is very easy and i am able to use it successfully for a single user message. However my use case requires messages be sent to more than one person and I get the same error as the original poster when there is more than one number.
Can anyone confirm the integration is only for a single user message or am i just formatting the request wrong?
I’ve been able to avoid Make/Zapier so far in my projects so hoping I am just missing something. Seems short sighted for the integration to only send a message to a single user.
Thanks!
Hey, just wondering if you ever came up with a solution for this?
I am pretty frustrated that I can only send one SMS at a time.
Yes I did, what are you trying to do
I’ve got the integration set up to send one SMS, and I have a column with list of numbers set up, but I can’t read it once there is more than one number in there. Wondering if I need to play around with a template, or if it is only designed for individual messages.
The traditional API that Glide use would only send one at a time, so you would need to use a workflow loop in that case.
Else, your options would be configuring a Messaging Service/Notify Service on the Twilio side and handle API calls yourself, I believe.
1 Like
Thanks for replying 
I think I’m going to find life easier if I just add Make and ClickSend into the mix. I don’t have the skills I’d need for a Twilio integration.
1 Like
Is there a reason you don’t use the Glide workflows for looping?
I think the costs could escalate quite quickly, two updates per message.
but maybe I’m being cheap and I’m causing more work for myself 
With the 2 updates for the SMS, plus the SMS cost (and the minimal) cost for the extra update for the trigger. Hmmm but it might be fine for now because I’m still building a POC rather than something fully scalable.
It could also be quite slow, but probably not a deal breaker. It’s a process that can happen in minutes not seconds.
1 Like