How the CustomerEagle Zapier app works
Push every new conversation, message, contact and help-centre article out to the rest of your stack — and let a Zap write back into CustomerEagle: send a reply, drop an internal note, update a contact.
The CustomerEagle app is published on Zapier as a private app — invite-only for now, so it does not turn up in Zapier's public app directory yet. Accepting our invite link adds CustomerEagle to your Zapier account; you then connect it with an API key you create yourself in the dashboard, scoped READ and WRITE to a single workspace. Triggers poll every few minutes today; instant, webhook-based triggers are the next step.
Status verified September 2026 — private app, invite-only
Free plan · No credit card · 25 free AI resolutions (one-time) · No time limit
What you need
- A Zapier account, on any Zapier plan
- Our invite link — the app is private, so it is not in Zapier's public directory yet
- A CustomerEagle API key with the READ and WRITE scopes, set never to expire
- A plan that includes the public API (Standard and higher)
How it connects
- 01Accept the invite link to add CustomerEagle to your Zapier account — the app is private, so searching Zapier's directory for it will not find it.
- 02In CustomerEagle, open Settings → API Keys and create a key with the READ and WRITE scopes, set to "Never expires" — Zapier reuses the same key for every Zap you build.
- 03Paste the key when Zapier asks you to connect CustomerEagle. The key is scoped to one workspace, and you can revoke or rotate it at any time.
- 04Pick a trigger — new conversation, new message, new or updated contact, new or updated article — or an action: Send Reply, Add Internal Note, Create or Update Contact, Create Article.
What you get
- Four triggers: New Conversation, New Message (customer, agent or AI messages — internal notes excluded), New or Updated Contact, New or Updated Article.
- Four actions: Add Internal Note, Send Reply, Create or Update Contact, and Create Article as a draft with optional publish.
- Send Reply goes out through the conversation's own channel — web chat, email, WhatsApp, Messenger, Instagram or Telegram — along the same path a human agent's reply takes.
- Two searches — Find Contact by email or external id, Find Conversation by id — so a Zap can look something up before it acts.
- A Zap can only do what the API key's scopes allow. The AI gains no new write powers from Zapier, and revoking the key stops every Zap at once.
What the AI can and cannot see
- Conversations — status, channel, assignee and the AI summary
- Messages from customers, agents and the AI
- Contacts and their custom fields
- Help-centre articles
- Your workspace directory: agents, inboxes, article collections and contact fields
- Internal notes your team writes — the read API hides them, so they never reach a Zap
- Passwords and credentials
- Billing data
- Any other workspace — each API key is scoped to exactly one
One inbox for every channel
Connect your channels once and every conversation lands in the same AI-first inbox — with shared routing, SLAs and analytics. Start on the Free plan — no credit card required.