Twilio doesn't connect with a sign-in screen. It uses your own Twilio keys, which you save in your app. Once they're saved, the builder can use them to send texts from your app.
💬 Ask your AI to set this up Paste this into your app's chat, once you've added your keys (Step 2 below):
My Twilio keys are already saved in this app's Env Vars as TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN and TWILIO_PHONE_NUMBER. Send texts from the app's server using those saved keys, never from browser code, without changing anything else. Then send a test text to my own phone number. If you can't do part of this, say so honestly instead of guessing.One thing the AI can't do for you: you add the three keys in your app's Env Vars.
Before you start
You need a Twilio account and a Twilio phone number to send from. Twilio's own rules apply: sender requirements, carrier filtering, country restrictions and Twilio's message charges are between you and Twilio. Only text people who have agreed to hear from you.
Step 1 — Copy three values from Twilio
In your Twilio console, copy:
- Your Account SID
- Your Auth Token
- The phone number you want to send from
Step 2 — Add them to your app
Open your app in the editor, click Dashboard, then Env Vars in the left-hand menu. Add each value as its own variable, and mark the Account SID and Auth Token as secret (the phone number doesn't need to be):
| Name | Value |
|---|---|
TWILIO_ACCOUNT_SID |
your Account SID |
TWILIO_AUTH_TOKEN |
your Auth Token |
TWILIO_PHONE_NUMBER |
your Twilio phone number |
You can also use Connect on Twilio's card in the Integrations page: it asks which app should use Twilio and takes your keys right there. If the builder shows a card in the chat asking for your Twilio keys, you can paste them into that card too.
Spell the names exactly as shown. Keep these keys private: never paste them into the builder chat, and don't add a VITE_ prefix, which would make them readable in the browser.
Step 3 — Ask the builder to send texts
With the keys saved, describe what you want in plain language, for example:
When someone books an appointment, text them a confirmation using my saved Twilio keys.
The builder writes the sending on your app's server, where your keys stay safe. Phone numbers work best in full international format, like +15551234567.
The same keys also sign in to Twilio's other features, such as voice calls. If you want calls, describe what you need and ask the builder to tell you honestly what it can build before it starts.
Test it before you publish
Send a test to your own phone in Preview first, never to a customer. A successful request from Twilio means Twilio accepted the message, not that it arrived, so check your phone. Then publish when it works.
When it doesn't work
The builder says Twilio isn't connected. Tell it in your own words that your Twilio keys are already saved in the app's Env Vars, and ask it to send texts from the app's server using those saved keys, without changing anything else.
The Connect button took me to build new app
.
That happens when your workspace has no apps yet. Build your app first, then connect Twilio. With one app, Connect saves your keys to that app; with several, it asks which app should use Twilio. If you can't add keys to any app, ask a workspace admin.
Texts don't arrive. Check that each key is in the right variable with no stray spaces. Anything about your Twilio number, sender registration or carrier filtering is on Twilio's side, and Twilio's support can see your account.
What to read next
- Connecting Sendblue for iMessage, RCS, and SMS — another way to text customers
- Browsing the integrations marketplace — what else you can connect