Working with Exchange Assets spans publishing assets your team creates and consuming assets others have published. The workflow below covers both sides, with the assumption that the team is working in the MuleSoft Anypoint Platform with an active Salesforce integration.
- Author the asset in the Anypoint Design Center or Studio
Create the API specification, integration template, or other asset in the appropriate MuleSoft tool: Design Center for API specs and fragments, Anypoint Studio for connectors and full integration applications, the Anypoint Platform console for custom policies. Develop and test the asset locally. Document its purpose, usage, and any prerequisites in the asset's README or description. Tag the asset with relevant categories and keywords for discovery.
- Publish to Exchange with the right visibility
From Design Center or Studio, click Publish to Exchange. Choose the target Business Group (internal scope), the version number, and the lifecycle state. Add a description, tags, and any required documentation. Click Publish. The asset appears in Exchange with its metadata and is now discoverable by other teams in the Business Group. For public assets, additional review may be required by the org's API governance team before broader visibility is granted.
- Discover assets to consume
From Exchange, search for assets relevant to the integration you are building. Filter by asset type (API, Template, Connector, Policy), by category, or by Business Group. Review the asset's documentation, version history, and usage metrics. Open the asset in the appropriate tool (Design Center for API specs, Studio for integration projects). The tool automatically downloads and incorporates the asset into your project, ready for use.
- Maintain and version your published assets
As your published assets evolve, release new versions with clear changelogs. Communicate breaking changes to consumers in advance. Deprecate old versions on a defined schedule once consumers have migrated. Monitor the asset's consumption metrics in Exchange to understand which versions are still in active use. Coordinate with consumer teams when retiring versions to avoid breaking their integrations. This ongoing lifecycle discipline is what makes the Exchange ecosystem trustworthy over time.
- Asset versions are immutable once published. New changes require a new version number; consumers explicitly migrate to it.
- Public assets are visible across the Anypoint Platform; private assets are scoped to specific Business Groups. Choose visibility carefully.
- Connectors built for older MuleSoft versions may not work with newer runtime versions. Confirm version compatibility before consuming.
- Asset deprecation should be communicated to consumers in advance. Sudden deprecation breaks active integrations.
- Internal Exchange assets are organization-specific. Cross-organization sharing requires explicit partner-asset visibility configuration.