To send an SMS from n8n, add an HTTP Request node, set the method to POST, point it at https://api.tryready.com/v1/messages, authenticate with an X-API-Key header, and send to, body and consent_attested as a JSON body. Add an Idempotency-Key header built from a stable ID in your data, and route failures to the node's error output so a retry never texts the same person twice.

There's no special Ready node to install. The generic HTTP Request node is the whole integration, and the same steps work in any workflow tool with an HTTP action. We make Ready, so the example uses only the request shape we document.

What you need before you build

  • An API key. Create it in Ready and keep it in n8n's credential store, not pasted into a node.
  • A card on file and a number. Both are required to send. A number is $2 a month.
  • Consent you can show. Every request carries consent_attested: true, your promise that the recipient agreed to texts. Only send that value for people who did.
  • A trigger that has a phone number. A Webhook node, a form, a CRM trigger or a spreadsheet row all work.

Every text is charged from the first one: $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.

Store the key as a credential

In n8n, open Credentials and create a Header Auth credential. Set the name to X-API-Key and the value to your key. Then pick that credential on the HTTP Request node. Your key stays out of the workflow JSON, so exporting or sharing the workflow doesn't leak it.

Limit who can edit the workflow too. Anyone who can change the node can send texts billed to you.

Configure the HTTP Request node

Add the node and fill it in like this:

FieldValue
MethodPOST
URLhttps://api.tryready.com/v1/messages
AuthenticationGeneric credential type, Header Auth, your credential
Send HeadersOn, one header named Idempotency-Key (see below)
Send BodyOn
Body Content TypeJSON
Specify BodyUsing JSON

The JSON body:

{
  "to": "{{ $json.phone }}",
  "body": "Hi {{ $json.first_name }}, your order #{{ $json.order_number }} has shipped.",
  "consent_attested": true
}

$json.phone comes from the node before it. to is E.164, like +12125550199. A 10-digit US number is treated as +1, but clean the value in an earlier Edit Fields or Code node if your source holds spaces or dashes. Our guide to E.164 phone number formatting for SMS APIs covers the odd cases.

Test with a name like O'Brien or one with a double quote in it. Raw JSON with an expression inside a string breaks on quotes. If that bites you, build the body in a Code node and pass the object through, so n8n does the escaping.

Leave from out. Ready picks the number: the one this contact already texts with, otherwise your primary number. The full field list is in the messages API docs.

Build the idempotency key from your data

n8n can run a node more than once. You can re-execute a failed run, a retry setting can fire the same item again, and a trigger can deliver an event twice. Each of those can send the same text again.

Send an Idempotency-Key header built from something stable about the message, not about the execution. A good value is an expression like {{ $json.order_id }}-shipped. Don't use n8n's execution ID or a random UUID made inside the workflow, because a re-run changes both and the protection disappears. With a stable key, a repeated request is recognized and Ready doesn't send twice.

If the same order can legitimately get the same message twice, add what makes it different, such as the shipment number. The post on idempotency and duplicate texts explains the pattern in more depth.

Handle failures without double sends

Open the node's settings and look at two options.

  1. Retry On Fail. Turn it on with a short wait between tries. Because the idempotency key is the same on each try, a timeout that actually did send won't send again.
  2. On Error. Pick "Continue (using error output)". The node then has a second output. Connect it to a step that writes the row and the response text to a "failed texts" sheet or sends you a Slack message.

A bad number or a malformed body won't fix itself, so don't loop on a 4xx. Check the error codes page and fix the data. For a timeout or a 5xx, retrying with the same key is the safe default. Our post on retries and failure handling goes through each case.

Quiet hours and opt-outs

Two answers will show up in real workflows.

  • 409 QUIET_HOURS_BLOCK. 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. Send that to a Wait node and try again later, or add hold_until_allowed: true to the body, which holds the text up to 24 hours like a campaign text. See handling the quiet hours 409.
  • A refusal for an opted-out number. Opt-outs and numbers on your Ban list are refused up front and not charged. Treat the answer as final and mark the row so the workflow skips it next time.

If your list comes from outside Ready, add a step before the send that calls GET /v1/opt-outs/:phone and filters on the result. A workflow tool drifts away from the source of truth easily: someone replies STOP, but your spreadsheet still says active.

Sending to a list

For one message to many numbers, POST /v1/messages/bulk takes to as an array, with at most 100 recipients per call. In n8n, use the Loop Over Items node with a batch size under that limit, and call the bulk endpoint once per batch. It uses far fewer HTTP calls than one request per row. The bulk messages docs have the limits.

n8n or a built-in automation?

If your trigger lives in a CRM Ready already connects to, a built-in automation can text a contact on a stage change with no workflow tool at all. n8n is the better fit when the trigger is an app Ready doesn't connect to, when one flow touches several systems, or when your team already runs n8n. For a wider view of connecting an SMS API to common tools, see connecting an SMS API to HubSpot, Zoho, n8n and WordPress. Prefer Make? There's a matching guide on sending SMS from Make scenarios.

Checklist before you switch it on

  • Key stored as a Header Auth credential
  • consent_attested set to true only for people who agreed
  • Stable Idempotency-Key built from your own data
  • Error output wired to a place a person will see it
  • A test run with a number you own and a name with a quote in it

Frequently asked questions

Is there an official n8n node for Ready? No. The HTTP Request node does the job, and you only need the one request shape above.

How should I test it? Send one message to a number you own, then repeat the run on purpose to confirm the idempotency key stops a second text. Widen the trigger after that.

What does a text cost? $0.0075 per segment plus the $0.0045 carrier fee, with one flat Standard rate. See the pricing page. If you expect large volume, talk to us on the Enterprise form.

Next step

Build the workflow with one test number first. When it sends cleanly and a deliberate retry doesn't double up, point the trigger at real data. The API quickstart shows how to create a key and make your first send.