I’ve been tasked with automating the porting of phone numbers into Twilio. Before I go any further, this is something I’ve been able to do before but on this second go-around, things aren’t looking so good.
My main issue is with the dropdown menu selectors, or at least what Twilio calls a dropdown menu. After trying with the below activities, none of them recognize the “Configure with” dropdown and won’t establish the selector I would have liked to have
- Select Item
- Select Menu Item
- CV Dropdown Select (this one will find the selector, but not grab the list item)
Now I already knew this, so my fix was to program the bot to manually tab through the Twilio page and use send hotkey activities to get the right option from the dropdown menus. It worked, but now it won’t. To my knowledge, the Twilio page I’m interacting with is the same one as when I did this for the first time, but the selectors are all showing as invalid. So, I essentially had to start from scratch. I tried to mirror what worked the first time and that just ended up with the bot tabbing all the way to the “Configure with” dropdown, but my “down” keys didn’t work as intended. It’s like the bot is sending the down keys as if it’s “entering” that selector for the first time, and not cycling through whatever options are available.
After trying and retrying everything I could think of to make the tabbing down to the dropdown work, I realized that the Click activity might provide some resolution. I set up the bot to tab down to the “configure with” dropdown, click it (shows the options, and then click the highlighted SIP Trunk option, but the second click would not register even though the element had become visible on the previous click.
I’m about as annoyed as I’m allowed to be with this and now I’m at that point where I need some additional opinions. Is there any way for me to more accurately tab through Twilio or configure my click activities differently to get the desired outcome?
Before you suggest it, I did look into some Twilio integration packages but those were only good for phone call automation, not porting into the Twilio console.