Webhooks
Find the setup guide for incoming channel and billing events.
answerLoops receives webhook events from connected platforms. Each integration has its own registration, permissions, and event format; there is no single payload format for all channels.
Integration guides
| Source | Setup and behavior |
|---|---|
| GitHub | GitHub integration: Issues, Discussions, comments, and repository synchronization. |
| Discourse | Discourse integration: activity in watched categories. |
| Circle | Circle integration: posts and comments in connected spaces. |
| Telegram | Telegram integration: messages delivered to the configured bot. |
| Email integration: inbound messages and reply configuration. | |
| Billing | Stripe integration: subscription events for operators of the hosted service. |
Verify delivery
- Complete the integration's setup guide.
- Send a test message or create the supported event in the connected platform.
- Check that the expected ticket or status change appears in answerLoops.
- If nothing appears, check the platform's delivery history and the answerLoops application logs for that event.
For self-hosted deployments, confirm that the configured callback URL is reachable over HTTPS and points to the intended deployment. Use the exact route and event types in the integration guide.
To build a client that searches knowledge or creates tickets directly, use the Agent API or MCP.
Generate a grounded answer using the organization's knowledge base, without opening a ticket
Counts against the org's monthly deflection limit — if the limit is reached, returns 429 instead of generating for free. Only high-confidence generations count toward that limit.
Data model
A map of the workspace, ticket, knowledge, and configuration records.