--- schema_version: "1" id: 190ba4ad16f89f623e93dc5542576653d64afb6453f80caa518a1976a9a4b4da title: Set Up the MuleSoft Direct Connector (Beta) collection: developer version: current locale: en-us portal_url: https://docs.salesforce.com/developer/current/en-us/data-cloud/data-cloud-int/guides/mulesoftdirect/c360-a-mulesoft-direct-setup.md canonical_url: https://developer.salesforce.com/docs/data/data-cloud-int/guide/c360-a-mulesoft-direct-setup.html source_site: developer.salesforce.com content_type: documentation content_hash: 547e7ae78603094374d0bf2cdff99ebccd0f290f94e73cf5e5361d6f725a83b8 products: - Data 360 Integration Guide - Data 360 Developer Documentation --- # Set Up the MuleSoft Direct Connector (Beta) To set up the MuleSoft Direct connector, you need to create a connected app, add the connector in Data 360, and create unstructured data lake objects (UDLOs) for the data. See the [Unstructured Data File Formats and Connectors](https://help.salesforce.com/s/articleView?id=data.c360_a_unstructured_data_connect.htm&type=5) for a list of supported file formats. ## Before You Begin Review these prerequisites. - You should have some familiarity with MuleSoft business groups, environments, and deployment targets. - Make sure that you have the necessary credentials to connect to the external sources. Refer to the [MuleSoft Direct Reference](https://developer.salesforce.com/docs/data/data-cloud-int/guide/c360-a-mulesoft-direct-reference.md#external-source-credentials) for details. 1. From Setup, enter `External Client Apps` in the Quick Find box, and then select **External Client App Settings**. 2. Turn on **Allow creation of connected apps**. 3. Select **New Connected App** and set these values. | Value | Description | | ------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Connected App Name | Enter the connected app’s name, which displays in the App Manager and on its App Launcher tile. The connected app name must be unique within the org, for example, My MuleSoft Direct. | | API Name | Enter the API name used when referring to your app from a program. It defaults to a version of the name without spaces for example., My_MuleSoft_Direct. | | Contact Email | Enter the contact email for Salesforce to use to contact you or your support team. | 4. In the API (Enable OAUTH Setting) area, select **Enable OAuth Settings**. 5. Select **Enable for Device Flow**. 6. Select these OAuth scopes. - Manage user data via APIs (api) - Perform requests at any time (refresh_token, offline_access) - Manage Data 360 Ingestion API data (cdp_ingest_api) 7. Select **Enable Client Credentials Flow**. 8. When you understand the security risks, accept the warning and save your changes. 9. Click **Manage Consumer Details** and copy the consumer key and secret values. 10. At the top of your newly created connected app click **Manage**. 11. Select **Edit Policies**. 1. Change IP Relaxation to **Relax IP restrictions**. 2. Change Permitted Users policies to **All users may self-authorize**. 3. Under Client Credentials Flow, for Run As, click the search icon, and find the user who you want to assign the client credentials flow to. For Enterprise Edition orgs, we recommend that you select an execution user who has the API Only User permission. 12. Save your changes. 13. In Setup search for “OAuth and OpenID Connect Settings”, and then turn on **Allow Authorization Code and Credentials Flows**. ## Set Up MuleSoft Direct in Data 360 1. In Salesforce, click **Setup**. 2. Select **Integrations** > **Integration Solutions** > **MuleSoft Direct Setup**. 3. Click **Connect to MuleSoft**. 4. Select the US or EU server. 5. Authenticate to the Anypoint Platform using your user credentials or to the connected app using your client ID and secret. 6. (For orgs with Industry and Data Cloud licenses) In the Available Assets section, select the Data Cloud filter. 7. Select the application asset that you want to use, and click **Enable Instance**. 8. Add the necessary details to enable the instance | Display Name | The unique name of the application | | ----------------- | --------------------------------------------------------------------------------- | | App Name | The unique name of the application instance | | Business Group | The MuleSoft business group in which you’re deploying the app instance | | Environment | The MuleSoft environment in which you’re deploying the application instance | | Deployment Target | The MuleSoft deployment target in which you’re deploying the application instance | 9. Click **Next**. 10. Authenticate to the external source, and click **Next**. 11. Each source has different authentication options. 12. Wait for the asset instance to deploy. When the instance is ready, its status changes to Active. An application instance can also be in an error state or still require authentication. After the application instance deploys and is active, Data 360 creates a read-only connector for that application instance. Use the connector to create unstructured data lake objects (UDLOs) to ingest data from the external source. ## Create an Unstructured Data Lake Object from MuleSoft Direct 1. From App Launcher, select **Data Cloud**. 2. Click **Data Lake Objects** and then click **New**. 3. From the New Data Lake Object menu, select **From External Files**, and click **Next**. 4. Click **MuleSoft Direct** and click **Next**. 5. From the Select Connection dropdown list, select a connection to an application instance. 6. For File Details, use wildcard characters to specify a file name pattern for multiple files. 7. To add more directories, click **Add more files**, and add up to five file name patterns. 8. Click **Next**. 9. Add an object name and an object API name for the UDLO. See Data Lake Object Naming Standards. 10. From the Data Space dropdown list, select the data space where you want to create the UDMO, or select a data space that has an existing UDMO. 11. Map the UDLO to a UDMO. 1. To create a new UDMO, click **New**. 2. To use an existing UDMO, click **Existing**, and select a UDMO from the list. 12. (Optional) Select the option to create a search index configuration for the UDMO using system defaults. You can deselect this option and create a search index configuration later. 13. Click **Next**, or if you chose to create a search index configuration, review the details, and save your work. 14. To initiate data ingestion, go to the details page for the new UDLO and click **Refresh Now**. ## See Also - [_Salesforce Help_: Unstructured Data Workflow](https://help.salesforce.com/s/articleView?id=data.c360_a_unstructured_data_workflow.htm&type=5) - [_Salesforce Help_: Use Data 360 Search for AI, Automation, and Analytics](https://help.salesforce.com/s/articleView?id=data.c360_a_search_index_ground_ai.htm&type=5) - [_Salesforce Help_: Create a Vector Search Index](https://help.salesforce.com/s/articleView?id=data.c360_a_search_index_create_vector_index_config.htm&type=5) - [_Salesforce Help_: Create a Hybrid Search Index](https://help.salesforce.com/s/articleView?id=data.c360_a_hybridsearch_index_create.htm&type=5) - [_Salesforce Help_: Using Retrivel Agumented Generation](https://help.salesforce.com/s/articleView?id=data.c360_a_rag_overview.htm&type=5)