M
member badge
Mark Leeper
Requesting a first-class, native integration between Hatz and Aircall (cloud phone system — developer.aircall.io), so Hatz agents can access call activity, recordings, transcripts, and contacts directly in chat and workflows — without requiring users to set up and maintain a custom MCP server.
Aircall’s API is REST-only — there is no official hosted MCP server, so someone has to self-host and maintain a wrapper just to make it reachable.
Every user has to authenticate individually, and credentials and tool discovery have to be managed per workspace.
What it would do
  1. Data access (read)
  • Search and retrieve calls, voicemails, and SMS by number, contact, date range, tag, or outcome.
  • Pull call recordings and transcripts into chat for summarization.
  • Look up Aircall contacts and their full interaction history.
  1. Actions (write)
  • Log call outcomes and notes.
  • Create or update Aircall contacts.
  • Assign calls and agents, add tags, set callbacks.
  1. Event-driven workflows (the big one)
  • Trigger Hatz workflows from Aircall webhooks — e.g., a missed call automatically drafts a follow-up email, creates a task, and posts a summary to the team channel.
  • Daily or weekly digest: “Here are yesterday’s 12 missed calls, grouped by reason, with suggested owners.”
Aircall supports OAuth 2.0 for authorization and webhooks for real-time events (call.ended, call.missed, etc.).
Scope needed: read access to calls, recordings, transcripts, and contacts; write access to notes, tags, and contacts (ideally configurable per workspace).