EmbedKit implementation methods
Boomi EmbedKit provides two ways to embed experiences into your application:
- EmbedKit CDN: A drop-in script that adds AI agents to any HTML page with no build tools or server-side code required.
- EmbedKit Integration: An npm package that gives you authenticated sessions, integration components, and programmatic control through a shared Node.js server and your choice of frontend framework, such as React, vanilla JS, or others.
Use the comparison below to choose the method that matches your requirements.
When to use EmbedKit CDN
- You want to add a Boomi AI agent chat widget to a website with no server changes.
- Your site runs on a CMS platform such as WordPress, Salesforce Experience Cloud, or a similar platform.
- You want to be up and running in less time without writing server code.
- You need only Agent Chat, not Integrations, Connections, Schedules, or Data Mapping.
When to use EmbedKit Integration
- You need components beyond agent chat, such as Integrations, Connections, Schedules, Data Mapping, or Execution History.
- Your users are authenticated, and each user must view only their own Boomi data.
- You need per-user scoping through Boomi child accounts.
- You want full programmatic control over authentication, theming, and component configuration.
- You need custom components built with EmbedKit SDK hooks in React or vanilla JS.
Key differences
| Feature | EmbedKit CDN | EmbedKit Integration |
|---|---|---|
| Package | @boomi/embedkit-cdn (via jsDelivr) | @boomi/embedkit (npm) |
| Setup | Paste two HTML tags | Build a server auth endpoint and client init |
| Server required | No | Yes |
| Authentication | Public token from Admin Console | Delegated — your server exchanges Boomi credentials for a nonce; the browser never accesses credentials |
| Components | Agent chat only (single, tiles, list layouts) | All components: Agents, Integrations, Connections, Schedules, Mapping, Execution History |
| User identity | Anonymous or optional userId string | Authenticated user, mapped to a Boomi child account |
| Per-user data scoping | Not supported | Supported — each user views only their child account context |
| CORS setup | Admin Console → CORS | Admin Console → CORS |
| Configuration | Admin Console (GUI + JSON editor) | boomi.config.js in your codebase |
| Theming | CSS variables via Admin Console JSON | Full cssVarsByTheme + cssVarsByKey design token system |
| Environments | Any HTML page — React and ReactDOM are bundled in, no framework required | React, vanilla JS (ES Modules), CommonJS — React and ReactDOM must be installed separately |
Next steps
- Getting Started with EmbedKit CDN — Embed an AI agent chat widget into any HTML page with no build tools.
- Getting Started with EmbedKit Integration — Embed Integrations, Connections, Schedules, and Mapping using the EmbedKit npm package.
Was this topic helpful?
