You can add SMS to Microsoft Dynamics 365 three ways: a workflow that calls a texting API, a custom connector built once and reused, or a middle layer that watches your CRM and sends for you. All three need the same two things from you: a clean consent field on the contact and a way to carry opt-outs back into Dynamics.

Ready is a REST texting API. We don't claim a Dynamics connection or a Dynamics marketplace listing. This post covers the general approaches and what we do offer, so you can decide what fits.

What you're really connecting

A Dynamics SMS integration has two directions. Outbound: a record changes (a lead is created, an appointment is booked) and a text goes out. Inbound: a reply or a STOP comes back and has to land on the right contact. Most projects get outbound working in a day and spend weeks on inbound and opt-outs.

Approach 1: workflow plus an HTTP call

Dynamics and the Power Platform can run a flow when a row changes and make an HTTP request to an outside service. Check your Microsoft plan's documentation for which actions and connectors your license includes, since that varies.

The flow's HTTP step would call Ready like this:

POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: <any UUID>

{"to": "+12125550199", "body": "Hi, this is Acme Roofing confirming Tuesday.", "consent_attested": true}

Set consent_attested to true only when your consent field says so. Use a stable ID, such as the row ID plus the event, as the idempotency key source, so a flow that re-runs doesn't text twice. Our idempotency post explains why.

Approach 2: a custom connector

If several flows need texting, wrap the API once as a custom connector so makers pick "send text" from a list instead of building the HTTP step each time. It's more setup up front and less repetition later. The request shapes are the same as above, and the API docs have the details.

Approach 3: a layer between the CRM and the API

Some teams skip native flows and run a small service that reads Dynamics through its own API and sends through Ready. Ready's App Library can start or write to Close, HubSpot, Pipedrive, Salesforce and Zoho CRM with no code, but Dynamics isn't in that list, so for Dynamics this route means your own service. Our CRM and automation webhook post shows the pattern.

Consent and opt-out sync pitfalls

These are where integrations go wrong.

  • No consent field. Add a yes/no field plus the date and source of consent. Ready stores no per-contact consent for API sends, so your CRM is the record. [Sign-ups on a Ready-hosted opt-in page are the exception.]
  • STOP never returns. Ready honors a STOP and blocks the number, but Dynamics doesn't know unless you tell it. Update the contact from inbound events, and read GET /v1/opt-outs/:phone before any send from another tool.
  • Opt-out list is not a full mirror. GET /v1/opt-outs leaves out some cases, such as a STOP from a deleted contact, so check the phone-level endpoint.
  • Bulk flows ignoring quiet hours. A one-to-one API text is refused with a 409 if the window won't open within 6 hours. Your flow needs to resend later. See the retries post.

Inbound replies need a webhook receiver on your side; the inbound webhooks post covers it.

A worked example with stated assumptions

Assume a sales team sends 1,200 one-segment confirmations a month, all to consented contacts. The cost is 1,200 x ($0.0075 + $0.0045) = 1,200 x $0.012, all-in and excluding screening. Each inbound reply is billed like a sent text. Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.

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.

Next step

Start with approach 1 on one flow, with a consent check at the top. Once it's stable, decide whether a connector earns its setup. Create an account to try the API.

Frequently asked questions

Does Ready have a native Dynamics 365 integration?

No. Ready is a REST API you can call from a Dynamics flow or your own service. We don't claim a Dynamics connection.

Where should consent live?

In your CRM, on the contact, with date and source. Ready records an attestation when you set consent_attested, not a per-contact consent record.

How do I keep opt-outs in sync?

Update Dynamics from inbound events, and check GET /v1/opt-outs/:phone before sending from another tool.

Can Dynamics start a text automatically?

Yes, through a flow or a service of your own that calls the send endpoint when a record changes.