---
title: "Topol Plugin in a CRM Example"
description: "A full end-to-end demo of embedding the Topol Plugin drag-and-drop email editor inside a mock CRM, showing developers how to integrate it into their apps."
url: https://docs.topol.io/email-editor/guide/crm-integration-demo.html
---

# Topol Plugin CRM Integration Example

**DemoCRM is a working example application that embeds Topol Plugin as its email editor.** It shows what the plugin looks like once it is part of a product rather than a standalone tool: users open a template from the CRM, edit it in the drag-and-drop editor, and save it back without leaving the application.

> **Try the live demo here:**
>
> [https://topol-campaign-showcase.lovable.app/](https://topol-campaign-showcase.lovable.app/)

## What the demo shows

The demo covers the integration pattern described in [Getting Started](https://docs.topol.io/email-editor/guide/getting-started.html), applied to a realistic application:

-   **The editor as a native screen.** The plugin fills a container inside the CRM layout, so it reads as one of the application's own screens rather than an embedded third-party tool.
-   **Templates owned by the host application.** DemoCRM holds the template list. Opening one calls `load`, and the `onSave` callback returns the JSON and HTML for the CRM to store.
-   **Interface customization.** Branding and available features are configured to match the surrounding application.

## Why this pattern fits a CRM

CRM and sales tools are a common fit for the plugin because email composition sits in the middle of a workflow that already lives in the product. Keeping it there avoids sending users to a separate tool and back with copied HTML.

The practical benefits for the host application:

-   **No editor to build or maintain.** Email rendering across inbox clients is a large, ongoing problem. The plugin absorbs it.
-   **Templates stay in your database.** The editor holds no template data, so the CRM keeps its existing storage and permission model.
-   **Control over the interface.** Available blocks, branding, and [roles and permissions](https://docs.topol.io/email-editor/guide/roles-and-permissions.html) are configurable, so the editor exposes only what your users should see.

To build the same integration, start with [Getting Started](https://docs.topol.io/email-editor/guide/getting-started.html) and add features from there.