> ## Documentation Index
> Fetch the complete documentation index at: https://meepa.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Connectors

> Connect MeepaGateway to chat platforms

Connectors link MeepaGateway agents to chat platforms. Each agent connects to one platform, configured in its `agent.yaml` under `connectors`.

```yaml theme={null}
connectors:
  - type: "meepachat"  # "meepachat" | "discord" | "telegram" | "slack" | "whatsapp"
```

## Supported Platforms

<CardGroup cols={3}>
  <Card title="MeepaChat" icon="comments" color="#F59E0B" href="/gateway/connectors/meepachat">
    WebSocket bot gateway + REST API
  </Card>

  <Card title="Discord" icon="discord" color="#5865F2" href="/gateway/connectors/discord">
    Gateway v10 WebSocket + REST API
  </Card>

  <Card title="Slack" icon="slack" color="#4A154B" href="/gateway/connectors/slack">
    Socket Mode WebSocket + Web API
  </Card>

  <Card title="Telegram" icon="paper-plane" color="#26A5E4" href="/gateway/connectors/telegram">
    Long polling or webhook
  </Card>

  <Card title="WhatsApp" icon="whatsapp" color="#25D366" href="/gateway/connectors/whatsapp">
    Meta Cloud API webhook
  </Card>
</CardGroup>

## Multi-Agent Routing

Even with a single connector, you can route messages to different agents based on server or channel. Messages not matched by any binding go to the agent marked `default = true`.

Binding resolution order:

1. Exact `channel_id` match
2. `channel_name` glob match (e.g., `"coding-*"`)
3. `server_id` match
4. Default agent

```yaml theme={null}
bindings:
  - agent: "coder"
    channel_name: "coding-*"
  - agent: "support"
    server_id: "abc-123"
    channel_id: "help-desk"
```

See [Configuration](/gateway/configuration) for the full bindings reference.