tsuiwilliam
Member
Keep getting this error: https://www.twilio.com/docs/errors/20001
Looking to use pabbly to trigger Twilio Studio Flow
Looking to use pabbly to trigger Twilio Studio Flow
-
Instructions to Ask a Question
For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.
We offer seven comprehensive applications designed to help you efficiently manage and grow your business:
- Pabbly Connect
- Pabbly Subscription Billing
- Pabbly Email Marketing
- Pabbly Form Builder
- Pabbly Email Verification
- Pabbly Hook
- Pabbly Chatflow
Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.
🚀 Exclusive Lifetime Offers 🚀
We invite you to take advantage of our special one-time payment plans, providing lifetime access to select applications:
- 🔥 Pabbly Connect — Lifetime Access for $249 — View Offer
- 🔥 Pabbly Subscription Billing — Lifetime Access for $249 — View Offer
- 🔥 Pabbly Chatflow — Lifetime Access for $249 — View Offer
Make a one-time investment and enjoy the advantages of robust business management tools for years to come.
-
Twilio API body setup
- Thread starter tsuiwilliam
- Start date
Hi @tsuiwilliam,
Please try entering your Twilio phone number and check whether this fixes the issue for you.
If this doesn't fix your issue, please share the Twilio API documentation and the endpoint you are trying to execute.
Please try entering your Twilio phone number and check whether this fixes the issue for you.
If this doesn't fix your issue, please share the Twilio API documentation and the endpoint you are trying to execute.
tsuiwilliam
Member
yah same error, this is their documentation, couldn't figure it out even with gpt lol 
www.twilio.com
thanks for the help!
Studio - Trigger (Start) Widget
Begin the Studio Flow with the Trigger (Start) widget and communicate between Studio and the parts of your business logic.
www.twilio.com
thanks for the help!
It seems you've fixed the issue since you are no longer getting the error.
Similar threads
