A Trello SMS integration turns a board into a status line. When a card moves to a new list, a rule fires, a request goes to a texting API, and the customer gets a short text. An ops team can run jobs, repairs, orders or onboarding from the board and keep customers informed without typing a message each time.
This guide is for developers and the operations teams they build for. We'll cover which card events make good texts, how to wire the trigger, the request that sends, and the consent and opt-out rules that keep it from becoming a spam machine.
Which card events are worth a text
Not every card movement deserves a message. Text on the moments a customer would otherwise call to ask about.
| Card event | Example text | Why it works |
|---|---|---|
| Moved to "Scheduled" | "Your install is booked for Thursday between 9 AM and 12 PM." | Replaces a confirmation call |
| Moved to "On the way" | "Your technician is heading to you now." | Cuts the where-are-you calls |
| Moved to "Ready for pickup" | "Your order is ready at the counter." | Prompts the action you want |
| Due date approaching | "Reminder: your appointment is tomorrow at 2 PM. Reply C to confirm." | Reduces no-shows |
| Moved to "Needs info" | "We need one detail to continue. Reply here and we'll pick it up." | Starts a two-way thread |
Texts should be one-to-one, useful and tied to something the customer asked for. Marketing messages need their own, separate consent.
How a card event reaches an SMS API
There are three common routes, and the right one depends on what your Trello workspace allows and who maintains the build.
- Trello's built-in automation (Butler). Rules can trigger on a card move or a due date and run actions. Whether a rule can call an outside URL depends on your plan and the current feature set, so check that in your workspace. If it can, that's the simplest path.
- A Zapier-style or n8n-style workflow. Trigger on "card moved to list," then add an HTTP step that calls the API. This is the common choice for ops teams, and n8n suits teams who want to self-host.
- Your own webhook listener. Trello can send board events to a URL you register. A small service receives the event, looks up the customer's number and consent, and calls the API. Developers get the most control, including retries and logging.
Ready has no native Trello connector. All three routes end in the same HTTP request, so you can start with an automation tool and move to your own service later without changing the message logic. Our post on SMS automation with Airtable, Brevo and Zapier shows the same pattern on other tools.
Where the phone number and consent live
A Trello card isn't a contact record. Putting a customer's phone number in a card description works for a prototype, but it gets messy fast. Better options:
- Custom fields. Add a phone field and a "texting consent" checkbox field to the card, if your plan supports custom fields.
- A lookup step. Store the card's ID against a customer record in a CRM or a spreadsheet, and have the workflow fetch the number and consent flag from there.
- A form that creates the card. An intake form captures the number and a consent checkbox, then creates the card with both filled in.
Whichever you choose, the workflow needs one rule: if the consent field isn't set, don't send. Capture that consent where the customer gives it, with wording like:
I agree to receive texts from Acme Repair about my service request. Msg and data rates may apply. Msg frequency varies. Reply STOP to opt out, HELP for help.
Ready stores no per-contact consent record. You keep it in your own data, with a timestamp and the wording shown. The consent_attested flag on a send is your promise that the recipient agreed. For form wording, see SMS opt-in message and form examples.
The request that sends
The sending step is one call:
POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: <card ID plus list name>
{"to": "+12125550199", "body": "Acme Repair: your technician is on the way. Reply STOP to opt out.", "consent_attested": true} Build the Idempotency-Key from the card ID and the list it moved to. Cards get dragged back and forth, and webhooks can arrive twice, so the key prevents a duplicate text when the same move is delivered again. Moving a card back to a list on purpose is a new event, so decide whether it should text again, and add the move's own timestamp to the key if it should.
Leave from out and Ready picks the number the customer already texts with, or your number closest to their area code. Reference: docs.tryready.com/api/messages.
Replies, opt-outs and the team inbox
Customers reply, and a status text is a good place to invite it. Replies land in the Ready inbox, where the team can answer from a shared thread. If you want a reply to update the card, an inbound webhook can post it to your own service, which then adds a comment through Trello's API. See receiving SMS with inbound webhooks for that side.
Opt-outs are handled for you. A STOP reply is honored automatically and the number can't be messaged again from that sub-account, and phrases like "do not text me" are caught too. Your workflow should still check before each send when it can: GET /v1/opt-outs/:phone answers for one number. Details are in docs.tryready.com/api/opt-outs.
Registration, quiet hours and cost
Business texts to US numbers from a local number run on a registered 10DLC campaign. Ready files it for you in the app: $25 a month covers the brand and its first campaign, $2 a month per number, and most approvals take 2 to 7 days. Before you register, an account can send up to 500 texts a month at its normal per-text rate, so you can test a board before filing. The 10DLC explainer covers why it matters.
Texts are $0.0075 a segment plus a $0.0045 carrier fee. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.
Quiet hours follow the recipient's area. Someone on the team dragging a card at 9 PM can trigger a text that lands too late. An API text goes out if the window opens within 6 hours. If it opens later, the API answers 409 QUIET_HOURS_BLOCK and the text isn't sent, unless the request includes hold_until_allowed: true, which holds it up to 24 hours.
Frequently asked questions
Can Trello send text messages by itself?
No. Trello's automation can fire on card events, but sending a text needs a messaging service. Connect them with an automation rule that can call a URL, an automation tool or your own webhook listener.
Does Ready have a Trello integration?
No native one. You connect a Trello trigger to the Ready REST API with Butler, a Zapier-style or n8n-style tool, or a small service of your own.
Who should I text from a Trello board?
Customers who agreed to texts about that job or order. Keep messages to status updates they asked for, and send anything promotional only to people who agreed to promotions.
Next step
Pick one list on one board, such as "On the way," and make it text a number you own. When that works, sign up, add a card and a number, and wire the real trigger. The SMS webhook and API guide for CRM and automation covers the plumbing in more depth.