Hi All, Captain Jack here building a whatsApp chatBot service and loving BuildShip!
I do need help with my current project, issue described below, appreciate any help or suggestions: Hi There,
I am building a chatbot application similar to your example whatsApp + Twilio solution, I've got the Twilio sandbox, whatsApp bot and buildship backend integration running with just one issue, for one of my usecases, I need a request to come into the buildship endpoint from one user, process the request and send the request off to the appropriate endpoint to generate a response, however the response is to go to a different whatsApp user, this is where the issue arises, the request is received fine, and both endpoint workflows execute with no errors in the logs, the output response message is built and twilio sms sender node configured to send to the new recepient's number however this message is never received. Both whatsApp users numbers are signed on to the Twilio sandbox account. Is there a reason a request from one number cannot have the response forwarded to a different number? hoping you can shed some light as I have debugged and check all logs but cannot see why the response message is not received.
8 Replies
Hi, @Luis, Could you please help with this?
Sure. Hey @captainjacksparrow7862, I'm not sure I fully understand but assuming that you've opted in the numbers your working with in the twilio sandbox, as per https://www.twilio.com/docs/whatsapp/sandbox#what-is-the-twilio-sandbox-for-whatsapp, then this should not be a problem. If we can have a look at your workflows, then we can try to better figure out what the issue is.
Get started with the Twilio Sandbox for WhatsApp
With the Twilio Sandbox for WhatsApp, you can start prototyping with Twilio API functionality and sending WhatsApp messages right away: outbound and inbound messages, status callbacks, and more!
Hi @Luis and Gaurav!
Thanks for the quick response, I have added both numbers to the Twilio sandbox and they can both receive messages from my flows individually i.e user1 req to buildship endpoint and res back to user1 or user2 req to buildship endpoint and res back to user2. The problem I am having is when I try to do something like user1 req to buildship endpoint and res to user2
How can I share the workflows with you?
via the in-app support form and attaching the workflow - https://docs.buildship.com/support-messages.
Done, please take a look at the support request and workflow.
Hi guys, any update? @Gaurav Chadha @Luis
ok I have resolved this issue now. For anyone interested it was due to Twilio's policy/restrictions on business initiated messages: https://www.twilio.com/docs/whatsapp/api#sending-notifications-with-whatsapp See also: https://www.twilio.com/docs/whatsapp/tutorial/send-whatsapp-notification-messages-templates#send-a-whatsapp-message-using-a-template Thanks for your help all.
Overview of the WhatsApp Business Platform with Twilio
Complete Twilio API for WhatsApp overview showing API calls, parameters, message formatting, and common examples and responses.
Send WhatsApp Notification Messages with Templates
How to create message templates for notifications with the Twilio API for WhatsApp. Examples and guidelines for WhatsApp message templates with Twilio.
Oh, good to hear this. Thanks a lot for sharing the Twilio's policy item. 👌
Hello ,
I'm trying to use the Twilio connector to send messages via Whatzap with templates, but according to the manual it has some updates such as using ContentSid instead of body, MessagingServiceSid, ContentVariables using variables via templates, can you explain to me the best way to adapt what's in the buildship for this, I didn't find the new variables to impute to the node.