Send iMessages from Retool

Why give an internal tool a texting capability?#

The ops teams living in Retool apps are closest to when a message should go out: an account manager working renewals, an ops analyst watching stalled orders, a RevOps admin holding the re-engagement list. Today those apps end with a mailto link or a task for someone else. A send action closes the loop where the decision already happens. iMessage is the version people answer, at 2-3x the reply rate of cold email, with no A2P registration required, so adding the channel is a resource config, not a compliance project.

How does the Retool build work?#

Create a REST API resource with base URL https://api.bluereacher.com/v1 and an Authorization header of Bearer brk_live_your_key. Every app in your workspace can then use it in queries. A minimal send app is a table of contacts, a text area for the message, and a button wired to a query that POSTs to /v1/messages with {{ table1.selectedRow.phone }} and the composed body. Retool's building blocks handle the rest: confirmation modals before sends, audit logging of who sent what, permissions so only the right group sees the button.

• For the inbound side, Blue Reacher posts replies, delivery states, and opt-outs to webhooks, and a webhook-triggered Retool Workflow is a natural receiver: write the reply to your database, flag the record in the queue app, or alert the owner. Scheduled Retool Workflows cover the batch patterns, a morning run that texts everyone entering the renewal window, with the query results as the send list. STOP suppression and iMessage availability checks run platform-side, and non-iMessage contacts fall back to RCS, then SMS, automatically.

• Renewals cockpit: accounts inside 30 days listed with a one-click check-in text from the CSM's line
• Stalled-order dashboard: a reviewed send queue that clears with one approval, not thirty copy-pastes
• Win-back app: closed-lost accounts resurfaced quarterly, each text personalized from the record on screen
• Reply inbox view: a table fed by the webhook workflow showing every response and who owns it

What's worth knowing before you build?#

Two design notes from teams running this. First, keep humans on the trigger for anything first-contact: Retool makes a reviewed-queue pattern (select rows, preview messages, approve batch) nearly free to build, and it's the shape that keeps quality high. Second, route each send through the line of the person who owns the relationship, one line per AM or CSM at $249 each ($199 at 6+), so replies go to someone who knows the account, not to a shared inbox nobody owns.

• Blue Reacher is native on GoHighLevel, HubSpot, Close, Salesforce, Pipedrive and Follow Up Boss; Retool connects through the REST API and webhooks as described, and white-glove onboarding includes setting up the resource and webhook workflow with your team, so the first app ships in days.

Pricing#

$249 per line per month with unlimited iMessages and no per-message fees, so a busy ops queue doesn't meter. Lines pace at 50 opted-in / 30 cold new contacts a day to stay deliverable; replies are never metered. $199 per line at four or more lines, or $1,949 per line per year, about $162.50 a month, with the $449 white-glove activation waived on annual billing. If your internal tables are missing mobile numbers, the mobile-validated B2B leads add-on fills them at $0.03 per contact, billed monthly with the line.