Create a Named Credential for Remote Vehicle Notification
Turn on Automotive Cloud Integrations and use the predefined app and its named
credential to connect your external telematics system to Salesforce. Use the app to send
notifications related to Salesforce records to a driver remotely via MuleSoft.
Required Editions
Available in: Enterprise, Unlimited, and Developer
Editions.
User Permissions Needed
To create a named credential:
Manage Connected Apps
If you use an integration layer other than MuleSoft, or a telematics provider other than
Qualcomm Car-to-Cloud, contact your integration admin for help.
From Setup, in the Quick Find box, enter Integrations Setup, and
then select Integrations Setup.
For Automotive Cloud Integrations, select I accept the terms and
conditions.
Click Enable for the Auto Send Notification asset.
Select a business group that you want to enable the integration for.
Select the environment where you want to enable the integration.
Select a deployment target where you want to deploy the integration.
Click Next.
Connect each dependent app to an external system.
Enter a connection display name.
Select the authentication protocol, and then enter the relevant details.
Click Done.
Click Proceed and wait for the enablement process to complete.
From Setup, in the Quick Find box, enter Named Credential, and then
select Named Credential.
Verify that a named credential is added for the connected MuleSoft instance.
Note the API name of the named credential to use it later. If you modify the named
credential name, make a note of the updated API name.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.