The Integration Module lets any plugin declare its options and lets store admins configure them in the Admin, no medusa-config edits and no redeploys. The module takes care of the UI, storage, encryption, and validation.

The Integration Module is a good fit for Medusa developers building plugins, providers, or custom modules with configurable options (API keys, credentials, modes, webhooks) who'd rather not write a separate UI page, data layer, and validation for each one.

• Settings management in Admin: Set in the Settings → Integrations section, no medusa-config/env edits and no redeploys.
• Any plugin, provider, or module: Works across payment, fulfillment, ERP, notification, content, and other extensions.
• Declarative descriptor (defineIntegration): A single description of the options, settings sections, validation, and connection test.
• Flexible typing and validation: Typed fields (string, url, email, uuid, number, boolean, enum, json) with per-option and cross-section rules, conditional visibility, and read-only fields. At runtime, the plugin gets a typed, decrypted object: incomplete or disabled settings never resolve, so an unfilled draft is never returned.
• Encrypted secrets: Fields marked secret are encrypted (AES-256-GCM) and never reach the browser.
• Multiple instances: The same provider can be configured more than once. For example, for several accounts in the same third-party service.
• Connection test: Verify credentials against the third-party service right from the Admin.
• Extensible UI: Sections can be reordered (LayoutComposer). If the generated sections aren't enough, you can implement any UI for your options using custom widgets.
• Integration catalog: Available integrations are shown in the Admin, and any plugin appears there on equal footing with the built-in ones.

---

---

Got questions or ideas about the plugin? Join the Telegram support chat — @gorgojs_chat

Connect with other Medusa developers on Telegram — @medusajs_chat