CRM
GoHighLevel
via Miss Blue
Project opt-in; new direct-message sync. Existing history and groups are not imported.
AN ATLAS OF IMESSAGE API INTEGRATIONS
CRM records, agent tools, workflows and people.
Find the path between them—and the work it takes.
01 / THE CONNECTION REGISTER
CRM
via Miss Blue
Project opt-in; new direct-message sync. Existing history and groups are not imported.
CRM
via Miss Blue
Map contact and deal signals to a business line and durable thread state. Confirm the actual implementation.
CRM
via Miss Blue
A guide for records, flows and owner handoff; not evidence of an installed marketplace app.
AI
via Miss Blue
Project-scoped messaging through the mb mcp stdio interface. Client approval policy remains separate.
Automation
via Miss Blue
Documented webhook/API workflow pattern. Confirm whether a dedicated connector is available for your account.
Automation
via Miss Blue
HTTP and webhook modules, record mapping and failure routing described in a provider guide.
Automation
via Miss Blue
HTTP Request and Webhook node pattern with server-held credentials and durable state.
Support
via Miss Blue
Map support conversation identity and teammate ownership through a custom adapter.
AI
via Miss Blue
A backend tool and conversation-state pattern; not a bundled SDK plugin.
AI
via Sendblue
Provider-documented setup for messaging, contacts and lookup tools. Plan rights still apply.
Automation
via Sendblue
The official docs list Zapier support. Inspect available actions and the chosen production tier.
AI
via Blooio
Hosted v4 MCP endpoint with API-key headers and a published tool list.
AI
via Linq
Official channel plugin with version requirements, pairing and runtime configuration.
Developer
via Linq
Messaging API and webhooks for your application adapter. Obtain production API terms.
Developer
via messages.dev
REST and TypeScript entry points with signed event processing. Production is contact-first.
Developer
via LoopMessage
Omnichannel API described for sites, services and CRMs. Verify the exact application path.
Developer
via Photon
Pricing describes managed tiers and self-hosting. Sender identity and operating duties differ.
CRM
via Project Blue
Provider-arranged CRM work; agree on mapping, write-back, acceptance and maintenance.
Support
via Tuco AI
Packaged conversation modes; confirm specific CRM/API exchange and export requirements.
CRM
via myCRMSIM
Customer-operated sender devices. Confirm exact CRM compatibility and recovery ownership.
Sources checked October 2, 2026. Documentation identifies a path; we have not installed or tested every connection. The publisher operates Miss Blue.
02 / TEN PROVIDER ROUTES
Miss Blue is our featured first route.
Follow the setup and ownership details.
10 of 10 options · positions reflect editorial fit, not measured performance
A business API with several clearly different connection paths
Miss Blue is our featured integration option for a dedicated messaging line, a documented MCP interface and a beta GoHighLevel connection. Its other app guides describe workflows that may require custom backend or webhook work.
Watch for: A published integration guide is not proof of a one-click installed connector.
An official MCP route and a documented automation entry
Sendblue’s documentation lists programmatic messaging, an MCP server and a Zapier integration. It is worth examining when an existing Sendblue account needs a supported tool or no-code entry point.
Watch for: Connector availability does not remove inbound-first or outbound account restrictions.
An API layer plus a client-specific agent channel
Linq documents messaging APIs and an official Claude Code iMessage channel. It can fit a custom application or that particular client workflow, provided the host requirement is respected.
Watch for: The Claude Code channel is not a generic connector promise for every assistant.
A remote MCP connector with explicit account actions
Blooio publishes a hosted MCP endpoint and a catalog covering sending, status, contact capability and webhook configuration. This is a specific documented connection to examine for a compatible client.
Watch for: Webhook settings and message sends are different account powers; review which actions the client can reach.
A developer-owned connection with a typed entry point
messages.dev documents a REST API, a TypeScript SDK and webhook processing patterns. It is a candidate when the team intends to build and maintain the application adapter.
Watch for: The production contact-first rule remains part of any custom connection.
A custom API connection with configurable sending options
LoopMessage’s homepage positions its omnichannel API for sites, backends, chatbots, services and CRMs. It is a custom connection path to evaluate against the required sender options.
Watch for: A listed CRM use case does not establish a native connector for your specific CRM.
Managed access or a self-hosted layer behind your adapter
Photon’s published pricing offers managed tiers and a self-hosted route. It gives an integration team a meaningful infrastructure choice rather than a universal no-code connector claim.
Watch for: Shared entry plans and a dedicated Business line have different identity and feature scope.
An implementation service around a CRM workflow
ProjectBlue’s public offering emphasizes CRM implementation, consultation and automation support alongside business messaging. It belongs in an integration shortlist as a provider-arranged implementation path.
Watch for: The scope and maintenance of a requested CRM integration should be written into the quote.
A packaged conversation platform to connect deliberately
Tuco AI advertises AI-oriented conversation modes and an operator workspace. It is an option when the team prefers a packaged handling layer and wants to investigate how that layer fits existing business systems.
Watch for: Confirm the specific CRM, API and export capabilities; a platform workflow is not an assumed native app connector.
An owned-device connection for a CRM-oriented team
myCRMSIM describes native phone/eSIM operation, a Mac app and messaging from a CRM. It is a candidate when the team intentionally wants to own the sender devices and investigate the supported CRM path.
Watch for: Verify the exact CRM arrangement and device health requirements before purchase.
THE READING ROOM
Read past the app name and identify what you will install, enable or implement.
Read article ↗02 / CRM mappingKeep the business record, contact, line and conversation separate so replies reach the right owner.
Read article ↗03 / Automation adaptersAn HTTP node can call a messaging API. The integration still needs deduplication, scope and an operating owner.
Read article ↗04 / SupportKeep ticket state and messaging state connected without letting two systems independently answer the customer.
Read article ↗BEFORE THE FIRST CONNECTION
A QUICK REFERENCE
Published entry prices can exclude setup, devices, calling or outbound access. Scroll the table to see all columns.
| Option | Model | Starting point | Confirm before buying |
|---|---|---|---|
| Miss Blue | Managed API | $99/line/month promotional rate | A published integration guide is not proof of a one-click installed connector. |
| Sendblue | Managed API | $100/line/month inbound; outbound quoted | Connector availability does not remove inbound-first or outbound account restrictions. |
| Linq | Managed API | Request a production quote | The Claude Code channel is not a generic connector promise for every assistant. |
| Blooio | Managed API | $89 shared / $289 dedicated per month | Webhook settings and message sends are different account powers; review which actions the client can reach. |
| messages.dev | Managed API | 50 free test messages/day; confirm paid pricing | The production contact-first rule remains part of any custom connection. |
| LoopMessage | Managed API | Dedicated Light from $59.99/month + options | A listed CRM use case does not establish a native connector for your specific CRM. |
| Photon | Managed API | Free / $25 Pro / $250 Business per line/month | Shared entry plans and a dedicated Business line have different identity and feature scope. |
| Project Blue | CRM platform | $300 single line / $250 per line at 2–10 lines; setup extra | The scope and maintenance of a requested CRM integration should be written into the quote. |
| Tuco AI | CRM platform | Confirm monthly tier; published $335 setup | Confirm the specific CRM, API and export capabilities; a platform workflow is not an assumed native app connector. |
| myCRMSIM | Own devices | $290/year per line at 1–10 lines; devices and carrier extra | Verify the exact CRM arrangement and device health requirements before purchase. |
BEFORE YOU CHOOSE
No. Each entry states the path: official connector, beta connection, custom build guide, implementation service, platform workflow or device setup. A provider’s app guide can require custom implementation.
We have researched linked primary documentation. We have not installed or benchmarked every connection. Validate the exact account, version and required actions with owned data.
Only if the particular connection documents and supports that scope. For example, Miss Blue’s GoHighLevel beta guide excludes existing history and group import.
The team behind Miss Blue. Its first position is a disclosed editorial choice, not an independent benchmark result.