Search
  • Ravi Sharma

Accessing Commerce Cloud APIs Using Ignite Nodes

Updated: Sep 3

Hello again!

As promised, we are here with our latest set of nodes for Salesforce Commerce Cloud's Integration with Ignite. These nodes can not only make your job easier consuming Commerce Cloud APIs but will also give you a whole new way of "connecting to Salesforce Commerce Cloud".


To consume Commerce Cloud APIs inside Ignite with ease, you will need our Ignite-sf-commerce Nodes.


If you are a paid customer, you can install Commerce Cloud Nodes by going to

Options Menu > Manage Palette > Install > and start typing in "commerce" into the search bar >

Click install and you're ready to rock.

If there's an update available, you can always upgrade to our latest nodes for more features.

For this walkthrough, we will be accessing Commerce Cloud Shopper Search API using "Shopper Search" Node.


Let's get started!


Drag and drop an Inject node to tell our flow when to start. Once our flow is ready, we will start our workflow by clicking the inject button to start the process.


Next, we need an access token to access the commerce cloud APIs; our Configuration Node makes this work a lot easier so, don't hesitate to pull out the Configuration Node from the Commerce family. Select a Token Type to access the API and provide the required parameters.

Add a wire from Inject Node to Configuration Node. This flow will get us an access token.

Now that we have an access token to access the APIs, we can make an actual request to the Commerce Cloud to any endpoint.


Note: Our Nodes are smart enough to extract the access token received by the Configuration Node. The token is attached to the headers in the subsequent API requests by default.

You can always choose to override the headers by passing in msg.reqHeaders property using Function node. See the example below.

msg.reqHeaders = {
    "authorization": "Bearer .S*",
    "content-type": "application/json"
}

msg.reqParams = {
    "q": "ties",
    "siteId": "RefArch"
}

return msg;

In this case, we want to access the "Shopper Search" API. For demo purposes, we will search the products for the keyword "Ties."

To set query parameters, we need to take help from the msg.reqParams property.


We are just one step away, drag and drop the "Shopper Search" Node and select the method and endpoint you want to hit.

Note: If there is any variable in the endpoint, provide the value for that variable. An Input field will be available for the same if there are any variables in the endpoints.


The above flow will make an actual request to the Commerce Cloud and will get you the response. To see the response that we received from Commerce Cloud, just attach in a Debug Node that will print out the response object in the debug window.


Great job! Now our flow is ready with the required configuration to call an API, All we need to do is hit that Inject button to see our Nodes in action. You can access the response object from msg.payload property or see the response in the debug window.

Recent Posts

See All

Ignite Platform Deployment Models

Most modern cloud products support various deployment models (e.g. public, private, hybrid). Typically, for SaaS tools, all data at-rest, and in-transit, flows through the vendors cloud. However, Igni

© Cyber Group Inc, 2020