You can text from Keap (formerly Infusionsoft) by having a campaign or automation make an HTTP POST to a texting API when a contact hits a step. The two things to get right are a consent field on the contact and a way to bring opt-outs back into Keap.
Ready doesn't have a native Keap connector, and we won't pretend otherwise. What it has is a REST API that any HTTP-capable automation can call. Check your Keap plan's documentation for the exact automation and HTTP-post options you have, since they depend on your plan.
The basic pattern
Keap's automations can, depending on your plan, send an HTTP post to an outside URL with contact data. Point that at a small endpoint of yours (or a no-code tool in between), and have that endpoint call Ready:
POST https://api.tryready.com/v1/messages
X-API-Key: <key>
Idempotency-Key: <a new UUID for each text>
{"to": "+12125550199", "body": "Hi Sam, your estimate is ready.", "consent_attested": true} Don't put your API key inside a Keap step that other staff can read. Keep it in the endpoint you control. The authentication post covers key handling.
Step by step
- Add a custom field in Keap, for example "SMS consent", plus a date and source field.
- Build an automation that only continues when SMS consent is yes.
- Add the HTTP post step to your endpoint, passing the phone number, first name and your message.
- In your endpoint, normalize the phone to E.164, set
consent_attestedto true, and callPOST /v1/messageswith a new idempotency key for each text (for example a UUID you store with that text), reused only when you retry that same text. - Return quickly, and handle failures with retries.
Our E.164 formatting post explains the phone step, which is the most common cause of failed sends.
The consent field
Keap won't know a contact agreed to texts unless you record it. Capture consent on the form with clear wording, store the yes, date and where it came from, and gate every texting automation on it. Ready records an attestation when you send with consent_attested, but it doesn't store a per-contact consent record: your Keap record is the proof. [A sign-up on a Ready-hosted opt-in page is stored per contact.] Our consent language post has wording that holds up.
Don't text a purchased or cold list. Texts go to contacts who agreed or who replied to you.
Syncing opt-outs back into Keap
When someone texts STOP, Ready blocks that number in the sub-account that received it. Keap doesn't know. If you don't sync, your email-side automations may keep treating the contact as textable, and your own endpoint could keep trying.
Two ways to sync:
- Poll. Subscribe to the
contact_opted_outwebhook (contact_opted_inundoes it) and tag or flag the contact in Keap on receipt. - Check at send time. Call
GET /v1/opt-outs/:phonein your endpoint before sending. The list endpoint isn't a complete mirror, since it leaves out cases like a STOP from a deleted contact, so the phone check is the safer gate.
See the opt-out API post for more.
Inbound replies
A reply lands in Ready's inbox. To get it into Keap, you'd receive a webhook and write a note or tag. Ready's quickstart shows how to set up a webhook. The event for a reply is inbound_reply; see the webhook events for the fields.
A worked example with stated assumptions
Assume a service business sends 800 one-segment appointment texts a month to consented contacts. The cost is 800 x ($0.0075 + $0.0045) = 800 x $0.012, all-in and excluding screening. 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
Build one automation with the consent gate first, test it with a number you own, then widen it. Create an account and use the quickstart to send a first text.
Frequently asked questions
Does Ready have a Keap integration?
No native connector. You connect Keap through an HTTP post to your own endpoint that calls Ready's REST API.
Is Infusionsoft the same as Keap?
Infusionsoft was renamed Keap. People still search for the old name, and the automation approach is the same.
How do I stop texting people who opted out?
Check GET /v1/opt-outs/:phone before each send and tag opted-out contacts in Keap.
Do I need 10DLC registration?
For US business texting, yes. See our 10DLC explainer.