To text from a Bubble app, add the API Connector plugin, create an API that calls POST https://api.tryready.com/v1/messages, store your key as a private header called X-API-Key, and send to, body and consent_attested as a JSON body. Then call it from a workflow action. The key stays on Bubble's server, so it never reaches a visitor's browser.
There's no Ready plugin to install. The API Connector is the whole integration, and the same request works for order updates, booking reminders, one-time codes your own logic checks and status alerts. We make Ready, so the setup below uses only the request shape we document.
What you need first
- An API key from Ready.
- A card on file and a number. Both are required, and a number is $2 a month.
- A phone field and a consent field on your user or customer data type. The consent field matters: it's what lets you honestly send
consent_attested: true. - The API Connector plugin, installed from Bubble's plugin tab.
Texts are charged from the first one at $0.0075 per segment plus a $0.0045 carrier fee per segment. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.
Step 1: add the API in the connector
In the API Connector, click Add another API and name it Ready. Under Authentication, choose "Private key in header". Set the key name to X-API-Key and paste your key as the value. Bubble keeps that value on the server side of your app.
Then add a call:
| Setting | Value |
|---|---|
| Name | Send text |
| Use as | Action |
| Data type | JSON |
| Method | POST |
| URL | https://api.tryready.com/v1/messages |
| Body type | JSON |
"Use as Action" is the important choice. It makes the call available in workflows rather than as a data source that fires every time a page loads. A text should only go out when something deliberately triggers it.
Step 2: write the body with dynamic values
Paste this into the body and Bubble turns each angle-bracket value into a parameter:
{
"to": "<to>",
"body": "<message>",
"consent_attested": true
} Add a header called Idempotency-Key with the value <idem>. Give each parameter a sample value, such as +12125550199 and a short message, then click Initialize call. Bubble sends one real text to that sample number, so use a phone you own. Once it succeeds, Bubble learns the shape of the answer.
Tick "Private" on any parameter you never want exposed in the page. The to and message values come from your workflow, so they're fine as normal parameters when the call runs from an authenticated workflow.
to is E.164, like +12125550199. A 10-digit US number is treated as +1, but your users type numbers in many ways. Clean them in your workflow, or on the input with a pattern check. Our guide to E.164 formatting for SMS APIs covers the odd cases. Leave from out and Ready picks the number. Field details are in the messages API docs.
Step 3: call it from a workflow
Open a workflow, for example "When a booking is created", and add the action Plugins, then Ready, then Send text. Fill in:
to: the customer's phone fieldmessage: your text, with dynamic values such as the customer's first name and appointment timeidem: a stable string, for example the booking's unique ID joined to the wordreminderand the appointment time, so a moved booking gets its own reminder
Add an "Only when" condition so the action runs only if the consent field is yes and the phone field isn't empty. That single condition prevents most mistakes.
Why the idempotency value matters in Bubble
Bubble workflows can run twice more easily than people expect. A user double-clicks a button, a backend workflow is rescheduled after an error, or a "Do when condition is true" action fires again after data changes. Each of those can text the same person twice.
Build the Idempotency-Key from your own data: the booking's unique ID plus the event name and the appointment time works well: if the booking moves, the new time gives a new value, so the second reminder isn't treated as the first one repeated. Don't use the current date and time, because it differs on every run and defeats the point. With a stable key, a repeated request is recognized and Ready doesn't send twice. The post on idempotency and duplicate texts explains the idea.
Send from a backend workflow for anything important
A page workflow runs when a user is looking at the page. For a reminder that should go out tomorrow at 9 a.m., use a backend workflow instead and schedule it with Bubble's "Schedule API workflow" action. The call runs on the server, whether or not anyone has the app open.
Backend workflows also give you a place to handle trouble. If the call fails, Bubble's server logs show the status. Save a failed flag on the booking so a person can see it.
Know what the API answers
You'll see a few kinds of answer in real use.
- Timeouts and 5xx. Try again with the same idempotency value after a timeout or a 500
send_failed. Because it's the same, a text that did go out won't go out twice. A 503 or a 500hold_not_returnedwas not sent, but the same value replays that error, so the workflow needs a new value for the retry. After a 504, checkGET /v1/messagesbefore sending again. The error codes page has each case. - 4xx for a bad number. Don't loop. Mark the record so someone can fix the phone number. The error codes page lists each code.
- 409 QUIET_HOURS_BLOCK. An API text is held only if the recipient's window opens within 6 hours. Otherwise nothing is sent. Reschedule the backend workflow, or add
hold_until_allowed: trueto the body, which holds the text up to 24 hours. See handling the quiet hours 409. - Opt-out refusals. People who reply STOP are refused up front and not charged. Store that outcome on the user so your screens stop offering a text.
If your users list came from elsewhere, call GET /v1/opt-outs/:phone before the first send. See the opt-out API guide for keeping your records in step.
A worked cost example
Suppose your Bubble app sends 2,000 appointment reminders a month, each a plain 120-character message, so one segment each. That's an assumption for the math. At $0.0075 per segment, plus the $0.0045 carrier fee on each, the monthly cost is 2,000 times the two figures added together, plus the $2 number fee. One emoji in the template drops the limit to 70 characters and can triple the segments, so count before you launch. The pricing page has the current figures.
Where this fits
Bubble is good at turning an idea into a working product quickly, and texting is one more API call. When the app grows into a platform that texts on behalf of many of its own customers, you'll want a sub-account for each. The guide to how to add SMS to your app covers registration and the production checklist.
Frequently asked questions
Is the key safe in the API Connector? Mark the header as private and the value stays on Bubble's server. Don't put the key in a page element or a custom state.
Can Bubble receive replies? Yes, with an API workflow that accepts incoming calls. The quickstart in the Ready docs shows how to set up a webhook.
Do I need 10DLC registration? For production texting from a 10-digit number, yes. See what 10DLC is.
Next step
Initialize the call with your own number, wire one workflow and test it twice to confirm there's no duplicate. Then add the consent condition and move the send to a backend workflow.