Your agent. A real conversation.
Updated
Real blue-bubble iMessage, RCS where supported, and SMS fallback for your AI agent.
Beam works with Claude agents through MCP. Not an Anthropic or Apple product.
Connect through Beam’s API or a compatible MCP client. Live sending requires permission and an assigned line.
Connect a compatible Claude client to Beam through MCP using a workspace connection token. Grant sending permission and use an active assigned line. Your agent can read conversations and send messages through Beam. Beam selects iMessage when the recipient is eligible and the selected line supports it. An accepted send is not proof of delivery.
MCP and API docs ↗Connect Beam to the correct GoHighLevel location, then add a Custom Webhook workflow step using the documented Beam workflow endpoint. Use a workspace token with sending permission and an active assigned line. Validate with a test contact before enabling the workflow. The regular GoHighLevel Send SMS action continues to use your default SMS provider.
GoHighLevel workflow docs ↗Yes. Beam provides a messaging API and MCP tools for AI agents to read conversations and send messages within an authorized workspace. This is Beam software, not an official Apple iMessage API. Pause the built-in assistant before an external agent takes over replies, grant sending permission explicitly, and check delivery status in Beam.
MCP and API docs ↗How it works
For desktop clients that support stdio, download the Beam bridge and run it with Node.js 20 or newer. Replace the absolute path with your local download path and YOUR_TOKEN with your workspace connection token. Keep the configuration private.
{
"mcpServers": {
"beam": {
"command": "node",
"args": ["/absolute/path/beam-mcp.mjs"],
"env": { "BEAM_TOKEN": "YOUR_TOKEN" }
}
}
}Create a workspace connection in Developer access. Connect a compatible client with bearer-authenticated HTTP or the local stdio bridge. Grant real sending separately.
MCP setup ↗Send signed message events to your HTTPS endpoint. Verify the signature against the raw body. Events have no automatic retries; reconcile important activity with message history.
Event webhooks ↗Connect the right CRM location. Use a Custom Webhook step to send iMessage from GoHighLevel, with your existing triggers, delays and conditions.
GHL workflow setup ↗Pause Beam’s bot for the conversation before an external agent takes over. Read the thread, generate a response and send with permission. Check delivery status in Beam.
Build your text agent ↗Built around the reply
Connect GHL lead workflows to Beam and let an AI agent handle replies, with a separate workspace connection for each client.
Build a follow-up text into your Voice AI workflow. Beam also supports FaceTime Audio, so calls and texts can work together.
Use your CRM’s timing rules to send reminders through Beam. Give your agent the conversation context to handle the reply.
Have your agent read the conversation and prepare a reply for your team to review before authorizing a send.
Guides
Free Claude skill
A free Claude skill for working with Beam is coming soon.
Before you connect
Beam documents a Claude Code connection using HTTP with a Bearer authorization header. Desktop clients that support stdio can use the downloadable Beam bridge with Node.js 20 or newer. Keep your workspace token in private client configuration. Hosted connectors that require OAuth-only login are not supported, so check your client’s supported connection method before setup.
Yes. Agency owners can select a directly managed client in Developer access before creating a connection token. Create a separate connection for each client because a token cannot switch workspaces. Client owners can also create and revoke their own connections. Access stops if the client leaves the agency, and live sending requires explicit permission.
Message event webhooks are pushed once, with no automatic retries in this version. Verify webhook signatures against the raw request body before processing events. For conversations your workflow cannot afford to miss, reconcile activity with message history on a schedule. Your integration should account for missed events instead of assuming every notification will arrive.
Claude iMessage means connecting Claude to Beam so an AI agent can work with business text conversations. Beam provides the messaging connection; Claude provides the AI. Beam works with Claude agents through MCP and is not an Anthropic or Apple product. Channel availability depends on the selected line and the recipient.
You can build a ChatGPT or other AI agent integration using Beam’s API, or use a compatible MCP client. Beam MCP supports HTTP with a Bearer authorization header and a local stdio bridge. Hosted connectors that require OAuth-only login are not supported yet. Each connection is restricted to its authorized workspace.
Beam’s iMessage and RCS channels avoid the carrier A2P 10DLC registration process. SMS fallback remains subject to applicable carrier A2P requirements. Consent and opt-out obligations still apply to your messaging workflows. Channel availability does not remove those obligations, and live sending still requires an active assigned line and appropriate workspace permissions.
Beam uses RCS when the Android recipient’s phone and carrier support it, with SMS fallback otherwise. Beam sends from Apple and Android devices. Sender capability and recipient reachability still matter. For eligible iPhone recipients, Beam selects iMessage when the chosen line supports it. Test the message and reply path before relying on a workflow.
No. Delivery status and recipient read status are different signals. An accepted or queued message is not proof of delivery. Beam shows recipient read status only when a channel supplies a real read event; read receipts depend on the channel and recipient settings. GoHighLevel receives pending, delivered or failed states, without invented open or read status.
Start with a conversation
Tell us about your setup. Text our team to explore iMessage, RCS and SMS for your business.
iMessage and RCS avoid the carrier A2P 10DLC registration process. SMS fallback remains subject to applicable carrier A2P requirements.
iMessage
Today 9:41 AM
Hi! I would love to hear how your coaching works.
Happy to chat. Would Thursday work for a discovery call?
Thursday sounds great! Looking forward to meeting you.
Blue bubbles. Read receipts. Typing.
Try a conversation with the Beam team.
Beam is not affiliated with Anthropic or Apple.
Powered by Beam