To send an SMS from Retool or another internal admin tool, create a REST API resource pointed at the messaging API, keep the API key in the resource's header, and add a query that posts to, body and consent_attested to POST /v1/messages. Then put a confirmation step in front of the button and send an Idempotency-Key that's generated once per confirmed send. That way a double click or a retried query can't text a customer twice.

The send itself is the easy part. The care goes into what an internal tool lets a person do: text the wrong customer, text someone who opted out, or click twice. We make Ready, so the examples use the Ready REST API and only the request shape we document. The same steps apply to Appsmith, Budibase, Superblocks or a tool you built yourself.

When an internal tool is the right place to text

Support and operations teams often need to send one text to one customer: a delivery update, a "we've fixed it" note, a payment reminder. Building it into the admin panel your team already uses beats pasting numbers into a personal phone. A few honest limits apply:

  • An internal tool is good for one-off or small sends. For campaigns and drip campaigns, use the Ready app's own bulk sending, which handles quiet hours and opt-outs for lists.
  • If your team needs to read and answer replies, the Ready Inbox is the place for that. A button in an admin tool only sends.
  • It's a tool for people who have a reason to text. Don't make it a free-text box available to everyone with access.

Create the REST resource

In Retool, add a REST API resource and set:

  1. Base URL: https://api.tryready.com
  2. Headers: X-API-Key with your key, and Content-Type: application/json.
  3. Storage: put the key in Retool's configuration variables or secrets, and give the resource to the apps that need it. Don't paste it into a query.

Use a dedicated key for the tool, so you can rotate or revoke it without touching your production backend. Our post on API key security and rotation has the checklist. Resource-level headers mean the key never reaches the browser as part of a query you can inspect in an app's JavaScript.

The send query

Add a query on that resource named sendText, method POST, path /v1/messages, body type raw JSON:

{
  "to": {{ customerPhone.value }},
  "body": {{ messageBody.value }},
  "consent_attested": {{ consentCheckbox.value }}
}

Add one more header on the query: Idempotency-Key, set to {{ sendKey.value }}. Create sendKey as a temporary state variable that's filled with a fresh UUID when the person opens the confirm dialog, for example crypto.randomUUID() in a JavaScript query. It must not regenerate on each retry of that same confirmed send. Fresh per confirmation, constant per send.

Quotes and newlines in a message can break a raw JSON body, so check in the query's preview that to arrives as a quoted string, and that a message with a quote in it still parses, before you wire up the button.

The to value takes E.164 format, such as +12125550199; a 10-digit US number is treated as +1. For exact response fields and error bodies, use the messages API reference.

The consent checkbox is a real statement

consent_attested is your promise that the recipient agreed to receive texts. When you set it, Ready records the attestation for that send: who sent it, to how many, and when, which builds an audit trail. Ready doesn't store a per-contact consent record from an API send, so the sender keeps the proof of the opt-in in its own form or CRM. (One exception: a sign-up on a Ready-hosted opt-in page is stored per contact, with the time, IP and exact wording.) An API send without consent_attested still goes out today, with a warning, and leaves no attestation, so don't leave it out.

In an internal tool, don't hard-code true. Bind it to a checkbox the agent must tick, labeled in plain words: "This customer has agreed to receive texts from us." Disable the send button until it's ticked. Better still, pull the answer from your own consent field on the customer record, and only enable the button when that field says yes. Compliance is the sender's responsibility, and the button should make the right choice the easy one.

Confirm before you send

A text can't be unsent, so make the dialog do real work. In Retool, have the Send button open a modal rather than run the query. The modal should show:

ElementWhat to show
RecipientCustomer name and the number, formatted, so a wrong row is obvious
MessageThe exact text, with a character counter
SegmentsAn estimate: 160 characters per segment, 153 when it spans several, and 70 or 67 if any emoji is in the text
CostSegments × ($0.0075 + $0.0045) as a plain line
ConsentThe checkbox, unticked by default
ConfirmDisabled until consent is ticked and the message isn't empty

Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.

The Confirm button runs sendText, then disables itself until the query finishes, which stops a double click. Set the query to run only when consentCheckbox.value is true as a second guard in the query's own conditions, so a changed UI can't bypass the first one.

Opt-outs, errors and what to show the agent

Ready refuses opted-out numbers and numbers on your Ban list up front and doesn't charge for them. Show that result in plain words in the app, such as "This customer has opted out of texts", and don't offer a retry. For a customer whose consent came from another tool, you can check GET /v1/opt-outs/:phone when the row loads and grey out the button. Our opt-out API post has the details.

A short error map helps agents:

  • Network error or timeout: the text may have gone out. Let the agent retry with the same key, which the tool keeps until the dialog closes.
  • HTTP 429: wait a few seconds and retry with the same key.
  • Other 4xx: show the message, fix the input, and use a new key for a corrected send.
  • Quiet hours: an API text is held only if the recipient's window opens within 6 hours. Otherwise it isn't sent and you get a 409 QUIET_HOURS_BLOCK. Tell the agent to send it once the window opens, or send with hold_until_allowed: true, which holds it up to 24 hours.

The error codes page lists the rest. Our post on idempotency and duplicate texts explains why the key stays constant across a retry.

Log who sent what

An internal tool has an advantage a script doesn't: you know which employee clicked. Write a row to your own table after each confirmed send, with the agent's user, the customer ID, the key and the time. It answers "who texted this customer?" without guessing, and it gives you the key to reuse if the agent needs to retry. Don't log full message bodies if they could hold anything sensitive. Keep health details, such as diagnoses, medications and test results, out of texts entirely, because Ready isn't HIPAA compliant and doesn't sign BAAs.

Frequently asked questions

Can I call the API from the browser in Retool?

Run the call through a Retool resource, not client-side JavaScript. Resources send the request from Retool's backend, so the key isn't exposed to the page.

Is there a Retool integration for Ready?

We don't publish a prebuilt one. A REST API resource with the request shape above does the job.

What does it cost to send from an internal tool?

The same as any API text: $0.0075 per segment plus a $0.0045 carrier fee. A card on file and a number of your own are required, and accounts opened before November 12, 2026 keep their signup prices, shown under Billing.

Where to go next

The takeaway: a resource that holds the key, a query with an idempotency key made at confirmation, a consent checkbox that means something, and a dialog that shows exactly what will be sent. If your team prefers no-code automation to a custom panel, the post on SMS integrations with HubSpot, Zoho and n8n is a good next read, and the API quickstart gets you a key.