To send a text when someone submits a Webflow form, turn on a form submission webhook in your site settings, point it at a small relay (a workflow tool or a tiny serverless function), and have the relay call POST https://api.tryready.com/v1/messages with your API key. Webflow can't add a secret header to the webhook, so the relay is what keeps your key safe.
That one extra step is the part most guides skip, and it's the part that matters. We make Ready, and the example sticks to the one request shape we document.
The shape of the flow
The path has three hops:
- A visitor submits the form on your Webflow site.
- Webflow posts the submission as JSON to a webhook URL you choose.
- Your relay reads the phone number and consent answer, then calls Ready.
The relay can be a Zapier, Make, n8n or Pipedream workflow, or a ten-line function on a serverless host. Pick whatever your team already runs. Our guides cover Make, Pipedream and n8n, and the serverless functions guide covers the code route.
Why you can't call the API straight from Webflow
A webhook from a form sends a fixed JSON body to a URL. You can't add an X-API-Key header, reshape the fields, or build an idempotency key. And you must never put your API key into Webflow's custom code, because anyone can read a page's source and then send texts billed to you. The relay is a server you control, so the key lives there.
Step 1: add a consent checkbox and a phone field
Before any wiring, fix the form. Add a phone input and a checkbox for consent. The label should say plainly what the person agrees to: who texts them, roughly how often, that message and data rates may apply, and that they can reply STOP to opt out. Don't pre-check the box.
This isn't decoration. The API's consent_attested field is your promise that the person agreed, so only send true when the box was ticked. If you're unsure what good wording looks like, see SMS consent language that passes registration and keep a record of the time, the wording and the page.
Step 2: add the webhook in Webflow
In your site's settings, open Integrations, then Webhooks, and add one with the trigger type "Form submission". Paste your relay's URL. Webflow posts JSON whose payload.data object holds the field values, keyed by the field names you gave in the designer. Submit the form once with test data and look at what the relay receives, so you map the real names rather than guesses.
Name your fields simply, such as phone, first_name and sms_consent, so the mapping is obvious six months from now.
Step 3: the relay calls Ready
Here is a minimal relay in plain JavaScript, written as a function that receives the webhook:
export async function handle(request) {
const hook = await request.json();
const data = hook.payload.data;
if (data.sms_consent !== "true" && data.sms_consent !== true) {
return new Response("no consent, skipped");
}
const res = await fetch("https://api.tryready.com/v1/messages", {
method: "POST",
headers: {
"X-API-Key": process.env.READY_API_KEY,
"Idempotency-Key": `webflow-${hook.payload.id}-welcome`,
"Content-Type": "application/json",
},
body: JSON.stringify({
to: data.phone,
body: `Hi ${data.first_name}, thanks for reaching out. We'll text you shortly.`,
consent_attested: true,
}),
});
return new Response(await res.text(), { status: res.status });
} Check how your form tool writes a checked box, since it may arrive as the string true, on or Yes, and adjust the test to match what you saw in the test submission. Leave from out and Ready picks the number. The messages API docs list the optional fields.
Make the idempotency key stable
Webhooks are delivered at least once. If your relay is slow to answer, Webflow may deliver the same submission again, and a workflow tool may retry a step. Either can text the lead twice.
Build the Idempotency-Key from the submission, as in the example, which uses the submission's ID from the payload. Don't use a random value made at run time. Check the real payload from your test submission for the ID field. If it has none, combine the form name, the phone number and the day. A repeated request with the same key is recognized and Ready doesn't send twice. See idempotency and duplicate texts.
Clean the phone number
Visitors type (212) 555-0199, 212.555.0199 and +1 212 555 0199. The to field is E.164, like +12125550199, and a 10-digit US number is treated as +1. Strip spaces and punctuation in the relay before sending, and skip the text if what's left isn't a plausible number. The guide to E.164 phone number formatting has the rules.
What the API may answer
| Answer | What it means | What to do |
|---|---|---|
| 2xx | Accepted | Log it |
| 4xx, bad number | The data is wrong | Don't retry; store the lead for a human |
| 409 QUIET_HOURS_BLOCK | Window opens later than 6 hours | Retry later, or send hold_until_allowed: true |
| Timeout or 5xx | Unclear outcome | Retry with the same key |
| Refused for opt-out | Number is blocked | Treat as final |
A form submitted at 11 p.m. is the classic quiet hours case. hold_until_allowed: true holds the text up to 24 hours, so the lead hears from you in the morning. See handling the quiet hours 409.
Why the speed matters
A form lead is warmest in the first few minutes. A text that lands while they're still on your site beats an email that sits in an inbox. Our post on speed to lead goes into the habit. Keep the first text short, say who you are, and don't send a link in it if you can avoid it, because links in a first message can get filtered.
Cost
Each text is $0.0075 per segment plus a $0.0045 carrier fee per segment, with a number at $2 a month. A 100-character welcome text is one segment. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing. The pricing page has the current figures.
Frequently asked questions
Can Webflow's own form notifications text me? They send email. Texting the visitor needs the relay and an API call.
Do I need 10DLC registration? For production texting from a 10-digit number, yes. See what 10DLC is.
Where does the key go? In the relay's secret store, never in Webflow.
Next step
Add the consent checkbox first, then submit a test form with your own number and watch what the relay receives. Once the text lands and a repeated submission doesn't double it, turn it on for the live form. The API quickstart shows how to make your first send.