Could you try executing system.twilio.getPhoneNumbers() in a script to see if any numbers are returned? Additionally, can you verify on your Twilio Account that you’re using has the number attached to your WhatsApp Service is Active? To check this, navigate to your Twilio Console again and select “Account Dashboard” at the top of the navigation bar. At the bottom of the page, there is a field called “My Twilio phone number” and to the right of it there should be an option to “View all numbers.” After selecting this option, is the Twilio WhatsApp Number listed there?
system.twilio.getPhoneNumbers(‘FlexAccount’) returns only the SMS number I am seeing in the pipeline.
In Twilio that is the same and only number under my Active numbers. The only place I am seeing the different WhatsApp number is under Messaging > Senders > WhatsApp senders.
Are you able to add the WhatsApp number to your Twilio Account’s Active Numbers list? That should then allow the Gateway to get the WhatsApp Number in the Pipeline and through the Method call.
I am digging more into this, as far as just adding the WhatsApp sender to the active numbers, it’s not as strait forward as I would have expected.
It looks like another WhatsApp sender needs to be created which will use the Twilio registered number to register with WhatsApp as a new sender. I’ll test again once everything is approved.
Was able to link up numbers on the Twilio side by setting up a new WhatsApp sender. Testing within the script console everything works as expected now.
Now I’m troubleshooting the notification block- I am triggering the pipeline and seeing the trace for the SMS send, as well as in the Twilio Logs. However, I am not seeing the WhatsApp notification try to send from the pipeline at all.
I see no logs about it.
Some additional feedback (still on Beta2)- I’m not a fan of the popup for the WhatsApp Template parameters. Something else within the notification block editor would be better IMO.
Still seeing the same Trial reset discrepancy with the designer. Still experiencing the Twilio account not resolving to ‘Active’ at times. It shows faulted so just editing something in the description and hitting save again is the work around.
Your user needs to have the “whatsapp” contact type for WhatsApp and not the SMS contact type. There were found issues previously where the UI doesn’t allow you to add the “whatsapp” contact type and calculated rosters don’t support the same “whatsapp” contact type. You will have to add the “whatsapp” contact type to your users through API or wait till the next beta release next week which will have those fixes.
I’ll spin up a ticket on our end to explore improvements to this parameters field.
Is this behavior consistent when the trial timer runs out or does it only happen sometimes? I’ve noticed you are using “reference” for your auth token so I can try replicating with this information on my end.