> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://help.crisp.chat/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# How to build Crisp plugins

*Learn where to start when you want to build a Crisp plugin or integration.*

Crisp plugins let developers extend Crisp apps, connect Crisp with external platforms, and build private or public integrations for their own workflows or for the Crisp Marketplace.

---

# ${color}[#0080dd](What plugins can do)

Plugins are useful when a standard Crisp feature or native integration does not cover your use case. They can connect your own platform to Crisp, add new operator tools, receive Crisp events, or expose custom configuration screens to workspace owners.

__Common plugin use cases include:__
* **Sync customer data** → enrich Crisp conversations with account, billing, or product information
* **Automate support actions** → react to events and update external systems
* **Add operator tools** → create widgets or actions inside the Crisp interface
* **Distribute an integration** → publish an app through the Crisp Marketplace

---

# ${color}[#0080dd](Where to start)

Start with the [Plugins quickstart](https://docs.crisp.chat/guides/plugins/quickstart/) on the Developer Hub. It explains how plugins work, how authentication is handled, and which building blocks are available.

If you plan to make the plugin public, also review the [Marketplace submission process](https://docs.crisp.chat/guides/plugins/submissions/) so you understand validation, privacy expectations, and production token requirements before you build.