Create an Integration Definition for Remote Vehicle Action
To connect Automotive Cloud with an external telematics system via MuleSoft, and perform
remote actions, create an integration definition by using a predefined Apex class. You can use
this integration definition, or create your own. Depending on your choice of telematics provider
and integration layer, you can create an integration definition with the required
attributes.
Required Editions
Available in: Enterprise, Unlimited, and Developer
Editions.
User Permissions Needed
To create an integration definition:
Industry Service Excellence
From Setup, in the Quick Find box, enter Integrations Definitions,
and then select Integrations Definitions.
Click + New.
Create an Integration Definition with these settings.
For Type, select Apex Defined.
For Name and Developer name, enter
REMOTE_OPERATION_INTEGRATION_DEFINITION.
You can also provide a different name but make sure you use the same name later in the
flow.
Click Next.
Select Apex Class as
automotiveconnectedvehicle.VehicleRemoteOperationProcessIntegrationProvider.
The attribute value for the attribute name Get Status URL Path is automatically
populated. If you use an integration service other than MuleSoft, modify the value to the
required URL path.
For the attribute name Connected Vehicle Named Credential, enter the attribute value as the
API name of the named credential that’s automatically created. See Create a Named
Credential for Vehicle Remote Action.
If you modified the autogenerated API name of the named credential, use the modified
name.
Save your changes.
Click Activate.
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.