Copy a prompt, paste it into Lovable, and your app can text customers by blue-bubble iMessage, SMS or WhatsApp, verify phone numbers at sign-up, and show replies. No A2P registration, no Twilio account.
In the portal, open Integrations › API keys, name it "Lovable" and click Generate new key.
Pick a prompt below and paste it into Lovable's chat. When Lovable asks for IBT_API_KEY, paste your key.
Booking confirmations, order updates, "we got your request" replies, reminders.
Add text messaging with iBlueText (https://ibluetext.com/llms.txt has the full API).
1. Store my iBlueText API key as a Supabase secret named IBT_API_KEY. Never put it in frontend code.
2. Create a Supabase Edge Function called send-text. It takes { to, body } and calls POST https://ibluetext.com/api/v1/send with the header "Authorization: Bearer " + IBT_API_KEY and the JSON body { "to": to, "body": body }. Phone numbers are E.164 like +18135550142. Return the JSON it sends back (it includes an id and the channel, iMessage or SMS).
3. Call send-text from the app when [describe the moment, e.g. a booking is confirmed], with a short friendly message that uses the customer's first name.
4. Show a small toast when the text is sent, and the error message if it fails.
Stop fake sign-ups: a 6-digit code by iMessage or SMS, half a cent per check.
Add phone verification with iBlueText SMS Verify (docs: https://ibluetext.com/llms.txt).
1. Store my iBlueText API key as the Supabase secret IBT_API_KEY.
2. Create an Edge Function verify-start: it takes { phone } and calls POST https://ibluetext.com/api/v1/verify with { "phone": phone, "end_user_ip": the caller's IP } and "Authorization: Bearer " + IBT_API_KEY. Return the id.
3. Create an Edge Function verify-check: it takes { id, code } and calls POST https://ibluetext.com/api/v1/verify?action=check with { "id": id, "code": code }. Return { verified }.
4. On the sign-up page, after the user enters their phone, send the code, show a 6-digit code input, and only finish sign-up when verify-check returns verified: true. Save the verified phone on the profile.
Show two-way conversations, or react when someone texts back.
Receive text replies from iBlueText (docs: https://ibluetext.com/llms.txt, webhooks section).
1. Create a Supabase Edge Function ibluetext-webhook that accepts POST JSON events. Verify the X-IBT-Signature header: it is the hex HMAC-SHA256 of the raw body using my iBlueText signing secret from Settings › Webhook (store it as the Supabase secret IBT_WEBHOOK_SECRET). Reject anything that doesn't match.
2. For event "message.reply" (and "whatsapp.reply"), save { from, body, received_at, channel } to a messages table linked to the customer with that phone number.
3. Show the conversation on the customer's page, newest at the bottom, with a reply box that calls the send-text function.
4. Tell me the function's URL so I can paste it into iBlueText under Settings › Webhook.
No. Each step above is a prompt you paste into Lovable's chat, and Lovable builds it. You only copy your iBlueText API key into a Supabase secret when Lovable asks for it.
Yes, as long as it stays in a Supabase secret and is only used inside Edge Functions, which is what the prompts tell Lovable to do. Never paste it into a page or component.
Both, picked automatically: iPhones get a blue iMessage and everyone else gets SMS. You can force one with "channel": "imessage" or "sms", or send WhatsApp with POST /api/v1/whatsapp.
No. Texts go out from real phone lines that iBlueText runs for you, or from your own Mac.
Every new iBlueText account gets free test texts and 10 free verifications, no card. Verifications are half a cent each after that. To text customers from your own dedicated number, a line is $99 a month hosted by us or $29 a month on your own Mac.
Yes. iBlueText is built for agents: point any AI assistant at https://ibluetext.com/llms.txt, or connect our MCP server at https://ibluetext.com/mcp in Claude or ChatGPT.