![]() |
VOOZH | about |
Through standards-based interfaces like OData and Swagger, the CData API Server provides a native experience in Logic Apps and Power Automate with Adobe Commerce. OData enables real-time connectivity to data; Swagger enables scaffolding, or code generation, of wizards in Logic Apps and Power Automate, as well as scaffolding Power Apps. This article shows how to add Adobe Commerce to an IFTTT (if-this-then-that) workflow in a Logic App.
If you have not already done so, download the CData API Server. Once you have installed the API Server, follow the steps below to begin producing secure Adobe Commerce OData services:
To work with Adobe Commerce data in a Logic App, we start by creating and configuring a Adobe Commerce connection. Follow the steps below to configure the API Server to connect to Adobe Commerce data:
Adobe Commerce uses the OAuth 1 authentication standard. To connect to the Adobe Commerce REST API, obtain values for the OAuthClientId, OAuthClientSecret, and CallbackURL connection properties by registering an app with your Adobe Commerce system. See the "Getting Started" section in the help documentation for a guide to obtaining the OAuth values and connecting.
You will also need to provide the URL to your Adobe Commerce system. The URL depends on whether you are using the Adobe Commerce REST API as a customer or administrator.
Customer: To use Adobe Commerce as a customer, make sure you have created a customer account in the Adobe Commerce homepage. To do so, click Account -> Register. You can then set the URL connection property to the endpoint of your Adobe Commerce system.
Administrator: To access Adobe Commerce as an administrator, set CustomAdminPath instead. This value can be obtained in the Advanced settings in the Admin menu, which can be accessed by selecting System -> Configuration -> Advanced -> Admin -> Admin Base URL.
If the Use Custom Admin Path setting on this page is set to YES, the value is inside the Custom Admin Path text box; otherwise, set the CustomAdminPath connection property to the default value, which is "admin".
Next, create a user to access your Adobe Commerce data through the API Server. You can add and configure users on the Users page. Follow the steps below to configure and create a user:
Having created a user, you are ready to create API endpoints for the Adobe Commerce tables:
Having configured a connection to Adobe Commerce data, created a user, and added resources to the API Server, you now have an easily accessible REST API based on the OData protocol for those resources. From the API page in API Server, you can view and copy the API Endpoints for the API:
π API EndpointsYou can use the API Server in a Logic App to create process flows around Adobe Commerce data. The HTTP + Swagger action provides a wizard to define the operations you want to execute to Adobe Commerce. The following steps below show how to retrieve Adobe Commerce data in a Logic App.
If your table has a column containing the creation date of a record, you can follow the steps below to write a function to check the column values for any new records. Otherwise, skip to the Create a Logic App section to send out emails to entities that match a filter.
To find new Adobe Commerce entities since a certain time, you can write a function that retrieves a datetime value for the start of the interval:
module.exports = function (context, data) {
var d = new Date();
d.setHours(d.getHours()-1);
// Response of the function to be used later.
context.res = {
body: {
start: d
}
};
context.done();
};
Follow the steps below to create a trigger that searches Adobe Commerce for results that match a filter. If you created the function above, you can search for objects that were created after the start of the interval returned.
http://MySite:MyPort/api.rsc/@MyAuthtoken/$oas
Use the descriptions for each property to specify additional parameters such as the columns to retrieve, filters, etc. Below is an example filter:
Style eq 'High Tech'
The API Server returns the descriptions and other documentation in the swagger document. You can find more information on using the OData API and supported OData in the API Server help documentation.
To use the datetime value returned from the getInterval function, use the "ge" operator with a datetime column in the Products table and select the Body parameter in the dialog. Note that quotes must be used to surround the datetime value.
π An OData filter on the results of an Azure Function App, getToday. (Salesforce is shown.)Switch to Code View and modify the $filter expression to extract the property containing the start of the interval. Use the syntax '@{body('MyFunc')['MyProp']'.
"getAllAccount": {
"inputs": {
"method": "get",
"queries": {
"$filter": "CreatedDate ge '@{body('getInterval')['start']}'"
},
"uri": "https://MySite:MyPort/api.rsc/@MyAuthtoken/Products"
}
You can now access Adobe Commerce as data sources and destinations in your workflows.
Follow the steps below to email a report with any new Products entities.
Click Save and then click Run to send email notifications on any Adobe Commerce records created in the last hour.
π Dynamic columns added to template the body of an email. (Salesforce is shown.)Learn more or sign up for a free trial:
CData API Server