New beta: Twilio Automation Action

Topic Labels: Automations
4669 13
Showing results for 
Search instead for 
Did you mean: 
Airtable Employee
Airtable Employee


Hi everyone! We’re excited to invite you to try one of our newest features - Twilio Automation Action.

With Twilio Automation Action, you can set up automations that send text messages based on triggers related to connected Airtable bases.

To sign up for the beta, fill out this quick form and click on the link at the end.

The feature should be available within a few minutes of clicking on the link. If it doesn’t, try refreshing the page. Please note that this feature will only work if you’re on a Pro or Enterprise plan. If you are on an Enterprise plan, you’ll need to ask your enterprise admin to also enroll in the beta via the same link and enable the feature from the enterprise admin panel.

If you have any feedback about the feature, please submit via this form.

13 Replies 13

Nice! Was waiting/hoping for this one :raised_hands:

And welcome to the community @Eileen_Xing :slightly_smiling_face:

Welcome to the community, @Eileen_Xing! :grinning_face_with_big_eyes: Not sure if I’ll sign up for the beta, but I’m definitely glad to see this added to the automation action collection.

7 - App Architect
7 - App Architect

Great integration!
Is it just sms or a range of Twilio’s features?

Just “send sms” for now (?).

8 - Airtable Astronomer
8 - Airtable Astronomer

@Eileen_Xing The form is not accessible: Sign in - Airtable

I keep getting this error :point_down: . Doing exactly the same thing with another Airtable and Twilio account works fine. Only possible issue that I can think of, is that I’m already using the same phone number in an active Zap :thinking:

Twilio reported an error while processing this action:
The ‘From’ number (360) 525-xxxx is not a valid phone number, shortcode, or alphanumeric sender ID.

Anyone has any ideas?

If you log into Twilio and look at the error log, does it give you any additional information?

The “message log”? Doesn’t mention anything special.

There should be an “Error Logs” page in Twilio. See if that page gives you any additional information.