Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

I’m working with a company that has 2-step verification setup on quite a few systems using a specific phone number that each employee does not have access to. This same company also uses Slack internally. Is anyone aware of a method to create a phone number that can be used as their primary 2-step verification phone number and would then have the ability to forward to Slack in a Zap?

In a scenario where I attempted to update their Amazon Seller’s account with a Google Voice phone number, it informed me that “this number is not valid”. I then attempted to utilize Twilio… The number was accepted, however the code was not forwarding at all and thus was undetected by Zapier to forward into Slack.




Update here; Received an email from Twilio support on this and just incase anyone was wondering:


"Services like Google Voice, Facebook, and Skype, which use short codes (e.g. 55555) to send SMS will not be able to send messages to Twilio phone numbers. This is because short code carriers have arrangements to exchange messages with mobile phone numbers only, and Twilio phone numbers are not considered mobile numbers. Unfortunately, we can not guarantee delivery from these incoming messages."



@craigleblanc Thanks for the heads up and bummer Twilio isn't going to work for this use case! You know what, I remember listening to an Asian Efficiency (AE) podcast and I think they ran into a similar issue with 2-step access. Their solution was to use a Grasshopper number. While Grasshopper isn't a supported app on Zapier, I would imagine you could get SMS notifications to your email and then use a Zap to trigger off of the message and send that information to Slack. Is that something you'd be up for trying?


You've probably sorted this now but... if an authenticator app is an option, we use 1password to store One Time Passwords so the whole team can access them, rather than using a phone number. (Bitwarden does this too but requires a mobile app to scan the onscreen QR code).


Hi @craigleblanc! I was wondering if you had an update on this? Were you able to find a way to make your verification flow work using SMS by Zapier or 1password?


Terms & Conditions