AlloCopper logo

Copper phone integration

Copper needs three auth headers, its public OpenAPI spec is read only, and bulk writes cap at 3 per second. Here is how Allo logs calls to Copper anyway.

How it connects

Allo connects to Copper 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.

Endpoints

Connect Allo to Copper

Because Copper has a public API, Allo connects over that API and webhooks. These are the API surfaces you point at Copper: a small, focused REST API, JSON in and JSON out, with webhooks for real-time events.

CallsREAD

Search your call history. Every record includes transcripts, AI summaries, recording URLs, IVR selections and transfer chains.

GET/v1/api/calls
ContactsREAD & WRITE

Full CRUD on your contact database. Create, fetch by ID, update and search, with engagement data baked into every response.

GET/v1/api/contacts
POST/v1/api/contacts
PUT/v1/api/contacts/:id
SMSSEND

Send SMS programmatically from any of your Allo numbers. Dedicated endpoints for US and France, both in E.164 format.

POST/v1/api/sms
POST/v1/api/sms/fr
WebhooksREAL-TIME

Subscribe a URL to call, SMS and contact events. Full envelope payloads, no secondary fetch to enrich the data.

GET/v1/api/webhooks
POST/v1/api/webhooks
DEL/v1/api/webhooks/:id
ConversationsREAD

Pull the whole thread for a contact: calls and SMS stitched together, in order, with pagination built in from day one.

GET/v1/api/conversations
Phone NumbersREAD

List every Allo number on your account. Use it to route, filter or match a number to an owner without hardcoding.

GET/v1/api/phone-numbers

Native or Zapier

The honest version: here is exactly how the connection is made today, and what is not built yet.

Native Allo integration

Not built yet for Copper

Zapier

17 triggers, 19 actions published

Allo and Copper, answered

No. Copper has Activities, and a call is an activity with a call type resolved from GET /developer_api/v1/activity_types. There is no duration, disposition or recording field, so those go in the activity body.

Because Copper needs three headers, not one. X-PW-AccessToken, X-PW-Application set to developer_api, and X-PW-UserEmail all have to be present on every request. Missing either of the last two fails.

You can, but it will be read only. The spec Copper publishes is titled Copper CRM Read-Only API and contains no write operations. Creating activities is documented separately under developer_api/v1.

Slower than you would expect. Bulk endpoints carry an additional cap of 3 requests per second on top of the standard limit, so a large historical import is paced by that rather than by your own throughput.

Not to a dedicated field, because Copper's activity has none. The recording URL goes into the activity body alongside the AI summary, which keeps it clickable in the Copper timeline.

The full_result flag on Activities Search is silently ignored unless the API key belongs to an administrator. It does not error, it just returns less.

Request a formal Copper integration

Tell us about your team and we'll build the Copper integration and get you early access. The more teams that ask, the sooner it ships.

  • Native calling, texting and AI call notes inside Copper
  • Every call logged to the right record, automatically
  • We build it for your team and give you early access

Prefer to talk it through? Book a call