Introduction
A white-label, AI-powered email editor for your product.
What is the Aurora SendCloud Editor Plugin?
The Aurora SendCloud Editor Plugin is a white-label, AI-driven email editor designed for seamless integration into your own platform.
It enables your users to create and edit email content directly within your product, while your server manages authentication, email logs, content delivery, and usage tracking.
With this plugin, you can provide your users with a comprehensive, native-feeling email creation experience—complete with AI email generation, AI-powered rewriting, drag-and-drop editing, prebuilt templates, Inbox Preview, and flexible import/export capabilities.
Who it is for
The Editor plugin is built for platforms looking to offer powerful email creation capabilities without building an editor from scratch, including:
- SaaS platforms
- CRMs
- ESPs
- Marketing platforms
- Customer portals
- Internal campaign or lifecycle marketing tools
Your users remain seamlessly within your existing authentication system. They can launch the editor directly from your product, customize their email content, and securely save it back to your server via a Push URL callback.
What your users can do
With the Editor plugin, your end users can:
- Generate complete email content using AI.
- Rewrite selected sections, text, or images with AI.
- Design emails effortlessly with a drag-and-drop builder.
- Start quickly with prebuilt email templates.
- Preview how emails render across various email clients and devices.
- Import existing HTML or JSON templates.
- Export completed email HTML and editor JSON configurations.
What your team controls
Your team manages the plugin centrally from the Platform Console and Application workspace, where you can configure:
- Applications: Separate configurations for different products, customers, or environments.
- API Credentials: Keys for secure backend access.
- Embed Methods: Custom embedding options and editor launch behaviors.
- Push URL Callbacks: Automated endpoints for capturing saved email content.
- Brand Appearance: Customized styling, including logos and interface themes.
- Domain Settings: Dedicated domains for editor access.
- Editor Controls: Managed variables, permissions, and supported content options.
- End-User Credits: Credit allocation and usage tracking for your users.
What you need to integrate
Before integrating the Editor plugin, ensure you have the following components ready:
| Requirement | Why it is needed |
|---|---|
| Backend service | Calls Editor plugin APIs, stores credentials, manages sessions, and receives saved content. |
| Frontend entry point | Triggers the creation or editing flow, then opens the editor URL returned by your backend. |
| Application | Acts as the central hub for API keys, branding, custom domains, Push URLs, and end-user data. |
| API credentials | Authenticate your backend's API requests to Aurora SendCloud Editor Plugin. |
| Push URL endpoint | Receives webhook payloads containing saved email content when a user saves inside the editor. |
Security Note: To maintain account security, your frontend should never call Aurora SendCloud APIs directly. Keep all API credentials and end-user tokens securely on your backend, and pass only short-lived editor access codes to the client browser.
Core Object model
The Editor plugin uses four main objects:
Account
-> Platform Console
-> Application
-> End User| Object | Description |
|---|---|
| Account | The login identity for a person on your team. One email address maps to one Account. |
| Platform Console | The organization-level workspace for your team. It contains Applications, teammates, and Console settings. |
| Application | The core Plugin unit. Each Application has its own API keys, brand settings, domain, editor controls, End Users, credits, and usage. |
| End User | A user from your own product. End Users do not log in to AuroraSendCloud directly. They are mapped by your external user identifier. |
For detailed definitions, see Core Concepts.
How it works
At a high level, the integration workflow follows these steps:
- Set up your Application: Create or select an Application within the Platform Console.
- Secure credentials: Store the application's API credentials securely on your backend server.
- Map users: Connect your product's users to Aurora SendCloud End Users using your external identifiers.
- Generate an access code: Initialize an email record on your server to request a short-lived, temporary editor access code.
- Launch the interface: Open the editor on your frontend via an iframe or a new window using the generated URL.
- Trigger the callback: When a user clicks save, the Editor plugin automatically sends the content payload to your Push URL.
- Save and resume: Your server captures the returned email content and resumes your product's standard workflow.
Your Frontend Your Backend
│ │
├─ 1. Requests editor URL ──────────────>│
│ ├─ 2. Calls Aurora SendCloud APIs
│ <─ 3. Receives token & short-lived code
<─ 4. Returns editor URL ────────────────┤
│ │
├─ 5. Opens the editor │
│ │
│ [ User saves content ] │
│ │
└────────────────────────────────────────┼─ 6. Editor sends content to Push URL
└─ 7. Saves content & continues workflow
For the complete frontend, backend, API, and Push URL sequence, see the Complete Embed Flow guide.
Editor launch methods
The Editor plugin supports two launch methods:
| Method | Best for |
|---|---|
| iframe | Embedding the editor seamlessly directly inside your existing product pages. |
| New window | Opening the editor layout in a dedicated browser tab or window. |
Both methods use the same backend authentication flow and the same Push URL callback flow.
