Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Boomi development inside Claude Code: build and deploy integrations, APIs, Event Streams, and Flow Services via CLI; scaffold projects from templates; clean up development artifacts; and visually organize process canvas layouts.
npx claudepluginhub officialboomi/boomi-companion --plugin bc-integrationSet up your local Boomi template folder and configure the command to spin up a new workspace profile
Interactive guide for setting up Boomi platform credentials
Clean all Boomi development artifacts while preserving directory structure
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Use this agent when you need to design and implement complex external enterprise system integrations for B2B applications. This agent specializes in connecting your platform with Salesforce, HubSpot, Microsoft 365, Google Workspace, SAP, Oracle ERP, and other critical third-party business software. Handles external API orchestration, data synchronization with enterprise systems, webhook management for third-party services, and enterprise-grade integration patterns. Examples:
Enterprise integration solutions using SAP Integration Suite on BTP. Covers Cloud Integration (iFlows), API Management, Event Mesh, Edge Integration Cell, Integration Advisor, Trading Partner Management, and Migration Assessment. Use for building integration flows, managing API proxies, event-driven architectures, B2B/EDI integrations, hybrid deployments, adapter configuration, Groovy/JavaScript message processing, and troubleshooting.
Corezoid AI Documentation and Templates — skills and MCP server for working with Corezoid BPM processes.
Advanced plugin marketplace platform with intent-based composition, supply chain security, contextual intelligence, dev studio hot-reload, and federated registry protocol. Transforms the marketplace from a package manager into an enterprise orchestration platform.
Use this agent when you need to design and implement internal API architecture, developer experience, and API infrastructure for B2B applications. This agent specializes in REST API design, GraphQL implementation, API documentation, SDK development, and developer portal creation. Handles API performance optimization, versioning strategies, and internal service communication. Examples:
Create Make.com (Integromat) scenarios with AI assistance - visual automation design
Search and install Boomi Marketplace recipes as reference samples
The official Boomi Companion — a Claude Code plugin for Boomi platform development. It wraps the boomi-integration skill with plugin-level commands, agents, and workspace tooling.
Important: Boomi Companion is a publicly available developer offering, not an officially supported Boomi product. It is provided as-is and is not covered by Boomi support agreements or SLAs. Boomi curates and maintains this tool on a best-effort basis — treat it as a self-service resource. Boomi reserves the right to modify or discontinue it at any time without notice.
This project is licensed under the BSD-2-Clause License. If you fork or modify this code, you should not use the name "Boomi" for your version.
For a full overview of Boomi Companion, including concepts, usage guidance, and additional resources, see the Boomi Companion overview on the Boomi Developer Portal.
Other plugins available in Boomi Companion:
| Plugin | Description |
|---|---|
| bc-marketplace | Skill for searching and installing Boomi Marketplace recipes |
The underlying skills are also available as standalone packages for use with other AI agents, or to fork and modify for your own needs:
| Skill | Description |
|---|---|
| boomi-integration | Skill for building Boomi integrations |
| boomi-marketplace | Skill for searching and installing Boomi Marketplace recipes |
See the Boomi Companion marketplace for the complete registry.
Found a bug or have a feature idea? Email developer-offerings@boomi.com with a clear description, steps to reproduce, and any relevant error messages.
/plugin marketplace add OfficialBoomi/boomi-companion
/plugin install bc-integration@boomi-companion
Or browse and install via /plugin interactively.
| Command | Purpose |
|---|---|
/bc-integration:env-setup-guide | Interactive Boomi credentials setup |
/bc-integration:configure-template-workspace | Create a reusable project template |
/bc-integration:tidy-up | Clean development artifacts |
After running configure-template-workspace, use /freshies from any empty directory to scaffold a new project.
Platform configuration credentials (.env file): Your .env stores the Boomi API token, account ID, environment IDs, and other platform config needed by the CLI tools. These are necessary for the agent to push, pull, deploy, and test on your behalf.
How the agent interacts with .env: The project settings and agent instructions steer the agent away from directly reading your .env file. The CLI tools load credentials internally — the agent invokes the tools without seeing the credential values. This is a default convenience buffer, not a hard security boundary. Be aware that:
.env file is a plaintext file on your machine.claude/settings.json guide the agent away from common file-reading paths, but a sufficiently motivated or creatively prompted agent could find indirect ways to access file contentsIf you need stricter isolation, consider Claude Code's sandboxing options or OS-level file permissions.