> For the complete documentation index, see [llms.txt](https://sentineldocs.metatable.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sentineldocs.metatable.dev/webhooks/introduction-to-webhooks.md). # Introduction to Webhooks {% hint style="danger" %} Webhooks **require** an **Premium** workspace membership plan. {% endhint %} **Webhooks** in **Sentinel** allow you to create custom integrations with other services or self-hosted tools, giving you flexibility in how you handle moderation events outside of the platform. By utilizing webhooks, you can automate tasks or trigger external actions whenever key events occur in your community. ## Available Webhook Events Currently, Sentinel supports a few main events for webhook triggers: * **GAME\_BANNED:** When a player is banned from a game. * **GAME\_UNBANNED:** When a player is unbanned from a game. * **DISCORD\_BANNED:** When a player is banned from the discord. * **DISCORD\_UNBANNED:** When a player is banned from the discord. * This event is only fired when they are unbanned via Sentinel Commands! ## Use Cases How you use webhooks is entirely up to you! Here are a few potential use cases: * **Notifications:** Send real-time alerts to your custom dashboard or communication channels when a player is banned or unbanned. * **Automated Reporting:** Automatically log ban/unban events into your self-hosted tools for analytics, record-keeping, or moderation oversight. * **Cross-Service Integration:** Use webhooks to synchronize ban actions across multiple platforms, ensuring that players banned in one game or service are reflected in others. Webhooks provide a powerful way to extend Sentinel’s moderation capabilities to external systems, allowing you to tailor actions to suit your community's needs. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://sentineldocs.metatable.dev/webhooks/introduction-to-webhooks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.