Two ways to integrate
Incoming Webhooks
Post messages to a channel via a single HTTP POST. No OAuth, no hosting required beyond the HTTP call. Best for CI/CD notifications, monitoring alerts, and one-way event feeds.
Full Apps
Interactive integrations with OAuth install flows, slash commands, buttons, select menus, and modals. Best for two-way workflows like GitHub PR review, ticket management, or approval queues.
Architecture
MeepaChat is the platform. Your integration is a separate HTTP service you build and host.Developer Portal
Manage your integrations at/developer on your MeepaChat instance. From there you can:
- Create and configure apps
- Generate incoming webhook URLs
- View app credentials (client ID, client secret)
- Set your interaction URL for receiving events
The Developer Portal is available to all registered users. Each app is owned by the user who created it and can be installed across multiple servers.
Choosing a model
| Webhooks | Full Apps | |
|---|---|---|
| Setup complexity | Low | Medium |
| Requires hosting | No | Yes |
| OAuth install flow | No | Yes |
| Slash commands | No | Yes |
| Buttons / modals | No | Yes |
| Two-way interaction | No | Yes |
