# What is a communication gateway for AI agents?

Source: https://catalex.co/ai-agent-gateway/ · Updated 2026-11-19

A communication gateway for AI agents is the layer between an agent and the chat apps people use. It receives messages from WhatsApp, Slack or Google Chat, hands them to the agent with the right person and conversation attached, and delivers the agent's reply back in each app's own format.

## Why agents need a gateway

Agents are built where engineers work: a terminal, a repo, an internal tool. The people who should use them live in WhatsApp, Slack and Google Chat. Every one of those apps has its own API, identity model, message format, delivery rules and approval process, so each new channel is its own integration project.

Without a gateway, a team that wants its agent on three channels writes and maintains three adapters, three webhook receivers, three ways to map a sender to a conversation, and three sets of retries for failed deliveries. That work does not make the agent smarter. It only makes it reachable.

A gateway turns that into one connection. The agent keeps its logic and tools; the gateway owns everything between the agent and the chat app.

## What a communication gateway handles

| Concern | Without a gateway | With CatalEx |
|---|---|---|
| Channel connections | One adapter per app, each with its own API and auth | Add WhatsApp, Slack or Google Chat from the app or the catalex CLI |
| Hosting | A public server and webhook endpoints for every app | CatalEx Cloud carries the messages. No server, webhook or public address |
| Identity and sessions | Map each sender and thread to a conversation yourself | Each person and conversation reaches the agent with its context |
| Message formats | Rewrite replies for Block Kit, WhatsApp buttons, Chat cards | Replies become text, buttons, chart images and files each app can show |
| Access control | Build allowlists and rate limits | Choose who may message each agent and how often |
| Risky actions | Build an approval flow | The agent asks; a person approves or declines from the chat |
| Visibility | Logs in several places | One activity view of conversations, cost and where the agent got stuck |

## How CatalEx works

CatalEx runs your existing Claude Code or Codex agent on your Mac, in the folder it already works in. CatalEx Cloud carries messages between that Mac and WhatsApp, Slack or Google Chat. The agent keeps its instructions, files, skills and tools; CatalEx only handles the conversation.

- **Your agent stays where it is.** Point CatalEx at the agent's folder. Nothing is migrated, and no SDK goes into your code.

- **Messages travel through CatalEx Cloud.** You open no ports and run no server. The Mac must be awake and online for the agent to answer.

- **Each channel belongs to one agent.** A Slack app, WhatsApp number or Google Chat app answers as one agent at a time, and you can move it to another.

- **You set the rules per agent.** Which tools it may use, which actions need approval, who may message it, and whether it may start conversations on its own.

The same tasks work from the `catalex` command line, so another agent can set CatalEx up for you. See the [agent setup playbook](https://docs.catalex.co/getting-started/agent-setup).

## Gateway vs. notification platform vs. tool connectors

Three kinds of products sit near this space, and they solve different problems:

| Category | Main job | Direction |
|---|---|---|
| Communication gateway for agents (CatalEx) | Let people hold two-way conversations with an existing agent inside their chat apps | People ⇄ agent |
| Notification infrastructure (for example Novu) | Send product notifications across email, SMS, push, in-app and chat from your application | Mostly app → people |
| Tool connectors for agents (for example Composio) | Let an agent call third-party APIs such as Jira, GitHub or Gmail | Agent → tools |

They combine well. An agent can use tool connectors (through its MCP servers) to file a Jira ticket, while CatalEx is how a person asked it to, from Slack.

## Which channels CatalEx supports

| Channel | Status | How people reach the agent |
|---|---|---|
| WhatsApp (business number) | Available | Message your business number. Uses your own Meta WhatsApp Business credentials. |
| WhatsApp Personal | Available Experimental | Message your own number. CatalEx is linked as a device, like WhatsApp Web. |
| Slack | Available | Mention the agent's app in a channel or send it a direct message. |
| Google Chat | Available | Mention the agent's app in a space or send it a direct message. |
| Shared link | Available | Open a public web page and chat. No account or app needed. |
| CatalEx app | Available | The native chat in the CatalEx Mac app. |
| Microsoft Teams | Coming soon | Planned. |
| Telegram | Coming soon | Planned. |
| Discord | Coming soon | Planned. |
| Phone calls | Coming soon | Planned: the agent answers and places voice calls. |

## When you need one

- You have an agent that works, and the people who should use it are not engineers.

- Your customers are on WhatsApp and will not install another app.

- Your team keeps asking an engineer questions an internal agent could answer in Slack or Google Chat.

- You want to reach people on more than one channel without maintaining an integration for each.

If your agent only needs to send one-way alerts, a notification platform may be enough. If it only needs to call APIs, tool connectors are the piece you want.

## Frequently asked questions

### What is an AI agent gateway?

An AI agent gateway, or communication gateway, is software that connects an AI agent to messaging apps such as WhatsApp, Slack and Google Chat. It handles each app's connection, identity, message format and delivery so the agent can hold conversations without channel-specific code.

### Is a communication gateway the same as an LLM gateway?

No. An LLM gateway sits between your code and model providers, routing and metering model calls. A communication gateway sits between your agent and the people talking to it, routing messages from chat apps.

### Do I have to rewrite my agent to use CatalEx?

No. CatalEx works with Claude Code and Codex agents as they are. The agent keeps its folder, instructions, tools and logic.

### Does CatalEx connect agents to Jira?

Jira is a tool, not a chat channel. If your Claude Code or Codex agent has a Jira tool through an MCP server, it keeps it in CatalEx, and you choose per agent whether it may use it. People can then ask the agent from Slack to create or update a ticket.

### What do I need to run CatalEx?

A Mac with Apple silicon, Claude Code or Codex installed and signed in, and a Google account to sign in to CatalEx. The Mac must stay awake and online for the agent to answer.

## Get CatalEx

- Download for Mac (Apple silicon): https://downloads.catalex.co/latest/CatalEx-arm64.dmg
- Docs: https://docs.catalex.co/
