Contact Us 1-800-596-4880
  1. Homepage
  2. Connector Builder

  3. Releasing Connectors

Releasing Connectors

Learn how to release your connector. Releasing is the process of making your connector available to others.

Connector Builder supports releasing your connector to Anypoint Platform and to Salesforce Flow.

Release Connectors to Anypoint Platform

To make your connector available on Anypoint Platform, release it to Anypoint Exchange. Connector Builder supports private releases to Anypoint Exchange only. The connector can still be shared with other accounts or teams.

After you release your connector, you should see your published connector in Anypoint Exchange. If you’re unable to see the published connector, click Back to legacy search to switch the search mode. For more information about publishing to Exchange, see Publishing Assets Using Maven.

Release Connectors to Anypoint Platform Using the UI

  1. Open your IDE and go to Connector Builder - Editor.

  2. Click Publish…​.

  3. In the UI, complete all checklist items to ensure you meet the release requirements.

  4. Click Publish to Anypoint Exchange. This runs mvn deploy from the {projectname}-anypoint-connector-model directory.

Release Connectors to Anypoint Platform with MCP Tools (Cursor)

  1. Open the Connector Builder extension in Cursor.

  2. Select Settings and ensure Enable Mcp Tools is enabled.

  3. Open the Cursor chat window (if not already open).

  4. Ask the agent to release the connector. For example, enter Publish this connector to Anypoint Exchange. This calls the uc_connector_lifecycle MCP tool with type='publish', which releases the connector to Anypoint Exchange. The same tool with type='build' builds the connector locally.

  5. Enter the required inputs when prompted.

  6. Confirm your inputs. Connector Builder releases the connector to Anypoint Exchange.

For more information, see MuleSoft DX MCP Server Tool Reference.

Release Connectors to Salesforce Flow

You can deliver a custom Flow connector in two ways:

  • Publish to AgentExchange as a standalone connector listing

    Package the connector as its own managed 2GP solution. Submit the AgentExchange Security Review. Then list it publicly on AgentExchange, or distribute it privately by sharing a direct package URL.

  • Deploy to a single customer org

    A Salesforce customer can build a custom connector and deploy it directly to their own org. No AgentExchange listing is required.

In both cases, the connector runs in the customer org and requires the MuleSoft for Flow add-on. Each connector operation consumes Automation Credits.

Release Connectors to AgentExchange

  1. Package Your Connector as a Standalone Managed 2GP Solution

    Package your custom connector as a standalone 2GP managed package, one package per connector, with no other app content. This is the format AgentExchange requires for distribution and installation in subscriber orgs. For more information, see Package a Custom Flow Connector as a 2GP Managed Package.

  2. Check Listing Readiness

    Before submitting your custom Flow connector for security review, verify that your package version is ready to be listed. For more information, see Security Requirements for AppExchange Partners and Solutions.

  3. Pass the AgentExchange Security Review

    Your custom Flow connector must pass the AgentExchange Security Review before it gets listed on AgentExchange. This applies to both public AgentExchange listings and private listings distributed by direct package URL. For more information, see Pass the AgentExchange Security Review.

  4. Create and Publish Your AgentExchange Listing

    After your custom connector package passes security review, create the listing in Partner Console. For more information, see Manage Your AppExchange Listings.

  5. Maintain and Update Your Connector

    If you revise a published custom connector, update your AppExchange listing so that customers get access to the latest version. For more information, see Manage Your Published Listings.

Release Connectors Directly to a Salesforce Org

To deploy a Flow connector directly to a Salesforce org, deploy the connector JAR as an IntegArtifactDef metadata component using Salesforce CLI. This is the Flow connector JAR produced from Packaging Connectors. The JAR file name follows the pattern {projectname}-flow-connector-model-{version}-dw-library.jar.

  1. Log in to your org from Salesforce CLI:

    sf org login web -r <org-url>
    Lightning URLs are not supported.

  2. Generate a Salesforce project to host the connector metadata:

    sf project generate --output-dir my-workspace --name my-project

  3. In my-workspace/my-project/sfdx-project.json, set "sourceApiVersion": "66.0".

  4. Inside the project folder, create a folder for the connector under force-app/main/default/integArtifactDefs/:

    mkdir -p force-app/main/default/integArtifactDefs/<ConnectorName>/

  5. Inside that folder, create a <ConnectorName>-meta.xml file:

    <?xml version="1.0" encoding="UTF-8"?>
<IntegArtifactDef xmlns="http://soap.sforce.com/2006/04/metadata" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <description>{description}</description>
    <displayName>{displayName}</displayName>
    <groupId>{groupId}</groupId>
</IntegArtifactDef>

  6. Create a versioned subfolder for the connector JAR and place the JAR inside it:

    mkdir -p force-app/main/default/integArtifactDefs/<ConnectorName>/<VersionString>/

  7. Deploy the connector to the org:

    sf project deploy start -m "IntegArtifactDef:<ConnectorName>" --target-org <your-org-username>