om-integration-builder

To scaffold an integration provider, use the builder to generate a complete npm workspace package structure, including core adapters, DI wiring, credentials handling, health checks, and tests aligned with marketplace patterns.

Creating a payment gateway or shipping carrier integration is best handled by scaffolding the provider package automatically, which generates the required adapter, webhook processing, and i18n files to meet the marketplace contract.

Yes, integration scaffolding includes health checks and i18n setup alongside core adapter implementation, widget injection, and test generation to ensure the provider package follows official marketplace patterns.

You can use this to add data sync connectors and webhook endpoints by triggering the scaffolding process, which automatically structures the external integration package within the npm workspace environment.

Building a new external integration generates core adapter files, DI configurations, credentials handlers, health check modules, i18n resources, widget scaffolds, and test suites within the npm package structure.

You should use an automated scaffold instead of manual creation when adding new external integrations like payment gateways or storage providers, ensuring all core files and templates strictly align with the marketplace contract.