1.0.1 (December 30, 2019)
To see the full changelog please use the following link.
To authenticate this component you need to get the details of the project from
inside the project. The information is in the Client Credential Flow part of
Developers > API CLIENTS.
Here are the values to copy to use in the account authentication part:
Project Name- This is the name of your project that you are trying to get the data from.
Client ID- This is the value in the
Client Secret- This is the long alpha-numeric code which can be copied from
You can configure the credentials in the Credentials section by selecting the component and giving a memorable name for your credential.
After adding the credential there is only one field here to configure - an Additional predicate to filter customers.
Additional predicate to filter customers is an optional field which you can use to filter and include only the customers needed for the particular integration flow. More information about how to use this field can be learned from the Commercetools help pages.
After adding the credential there are two possible configuration fields:
As an action component the Commercetools can help with the following activities:
For this action we have only Customer id and External id fields to map from which Customer id is a required field. It is worth to mention that you can use the External id optional field to sync your data about the same customer.
The Create Product action has more than 10 fields to map the incoming data from your trigger component. The number and the language settings of the fields depend on your Commercetools setup and can be different but there are two required fields which you must use for this component to work:
In case we want to add or update Price to Variant then there are only 4 required fields to map your incoming data - Price amount, Price currency, Product ID and Variant ID.
When we wish to map the incoming data with Product Variant by SKU then there are 3 required fields to fill-in:
This case is straightforward since only the Customer id is required.
Only Order id is required to perform this action.
If we wish to map the Product Variant with incoming data then there are 2 required field - Master Variant SKU and Sku. There is also one optional field Variant Custom attribute which you can use to further filter the results.
This particular action has two required fields to map with the incoming data:
When Add a Delivery action component is selected then we have 3 required fields - ID of the line item being delivered, Order Number and Quantity. There are 2 optional fields to configure - Tracking ID to track the delivery and Unique parcel ID. Use this particular action for reporting the status of delivery back to your system.
You can use this particular action component to track different types of Order IDs which is a required field. To select use the drop-down menu near the component section to choose.