Beacon phone integration
Beacon generates its API docs per account behind a login, so there is no public object model. Here is what can and cannot be promised for a phone integration.
app.beaconcrm.org/contactsActivity
How it connects
Allo connects to Beacon through Zapier today.
Licensed operator
Registered telecom operator in France (ARCEP).
Its own network
Allo runs its own VoIP infrastructure, not resold.
GDPR compliant
Your call data stays yours, handled to GDPR.
In the Claude directory
Allo's MCP server is in the Claude connectors directory.
What flows between Allo and Beacon
Allo handles the calls and texts. Beacon stays the system of record. Here is what moves between them, automatically.
Call Answered
Triggers when a call is answered.
Call Completed
Triggers when a call ends, with result, duration, recording and AI summary.
Call Received
Triggers when an incoming call starts ringing.
Call Triggered
Triggers when an outbound call is initiated.
Missed Call
Triggers when a call is missed.
SMS Received
Triggers when an SMS is received on one of your Allo numbers.
Connect Allo to Beacon
Because Beacon has a public API, Allo connects over that API and webhooks. These are the API surfaces you point at Beacon: a small, focused REST API, JSON in and JSON out, with webhooks for real-time events.
Search your call history. Every record includes transcripts, AI summaries, recording URLs, IVR selections and transfer chains.
Full CRUD on your contact database. Create, fetch by ID, update and search, with engagement data baked into every response.
Send SMS programmatically from any of your Allo numbers. Dedicated endpoints for US and France, both in E.164 format.
Subscribe a URL to call, SMS and contact events. Full envelope payloads, no secondary fetch to enrich the data.
Pull the whole thread for a contact: calls and SMS stitched together, in order, with pagination built in from day one.
List every Allo number on your account. Use it to route, filter or match a number to an owner without hardcoding.
Native or Zapier
The honest version: here is exactly how the connection is made today, and what is not built yet.
Not built yet for Beacon
Zapier1 trigger, 2 actions published
Why CRM teams add Allo to Beacon
The calling, texting and AI that sit right on your Beacon records.
Click to call
Dial any number in one click, from your CRM or browser.
Call Recording & Transcription
Record and transcribe every call, searchable in seconds.
AI Summaries
Every call written up automatically, ready to share.
Post-Call Actions
AI drafts the follow-up email, SMS and CRM update.
Power Dialer
Work a call list back to back, no manual dialing.
SMS / MMS
Two-way business texting with media and voice notes.
Allo and Beacon, answered
It has an API, but the documentation is not public. developers.beaconcrm.org requires a login and generates the reference from your own account configuration, so there is no shared public schema.
Because the docs host is a single page app that returns an HTML shell for every path, including /openapi.json and /swagger.json. There is no spec there. Any tool that trusts the status code will think it found one.
Only through Zapier's generic Create Record action, which means you decide which Beacon object receives the call and what the fields are. There is no call object in the published automation surface.
Your account's generated API documentation, since the object model is account specific. With that we can map Allo's call fields onto your actual schema.
Request a formal Beacon integration
Tell us about your team and we'll build the Beacon integration and get you early access. The more teams that ask, the sooner it ships.
- Native calling, texting and AI call notes inside Beacon
- Every call logged to the right record, automatically
- We build it for your team and give you early access