Customization, what for?

Well, you have your Akeneo Connector for Salesforce already up and running.
Now you think about how you can customize things, because you have additional requirements?

Congratulations, now all your product data is transferred to Salesforce or just heading there. 
You have your Categories, Products, and Assets in sync - but you need more.

Maybe you plan to run a commerce shop, but it requires you to have your Assets in product media objects as well as it also would require to synchronize your catalog records into the Product Catalog.

The Akeneo Connector is designed to be multi-cloud compatible. Because of this, no objects are used that will require extra licenses like commerce or digital experience as the above-mentioned Salesforce objects would do.

Customization helps to achieve things the Connector is not capable of, out of the box, now.

There are different possibilities like doing things programmatically i.e. by using Apex, Triggers, and so on, but on the other hand, you can use declarative tools like flows to achieve this and apply customizations.

Now we focus on how to do things as an admin, which means declarative.

Flows

Flow is the most powerful automation tool of Salesforce and it gives the admins the powers of developers. You can either use flows to further transform the data transfered from Akeneo or use the flow capabilities to call the Akeneo APIs .

HTTP Callout 

Using the new HTTP Callout (Beta) button from the action element, you can now make calls to Akeneo APIs using the configured Named credential when the package was installed. 

Click on Next and continue like here:

After clicking on Done the last form appears:

You can now use the output of the callout to further transform the data using the flow standard elements such as assignments, loops, create, and update. 

Copy data from one object into another

This example shows a flow being triggered if an Akeneo Product Category record is created or updated and then copies data into a Product Category record.

Create a record-triggered flow:

Now configure it to run if a related record is been created or updated: 

Next is to read the record-related data, by adding and linking a Get Records action:

In the end, we need to write the new record by using a Create Records action:

The full final flow should look like this: