This is my first blog post related to common resource of open connectors. SAP Integration suite Open connectors is the capability which provides the services that simplifies and accelerates the connectivity to third party cloud applications.
The library of SAP Integration suite open connectors has Common Resources, which define your own resource and create mappings to the apps.
The common resource template has the necessary field mapping and transformations to transform the data provided by resources.
Common Resource provides a standardized format of a specific resource that is not related to any API provider, but applicable to all providers with similar resources.
While mapping common resource to connectors will transform the connector resources to a consistent request and response payload, also can transform the payload types and values.
- SAP BTP
- SAP Open Connector capability added to the Integration suite.
Before going to common resources, first we have to create instance.
The below are the steps to be followed for creating instance,
Select the HubSpot CRM connector and authenticate type of configuration as apiKey and provide the HubSpot API Key and click create Instance.
Now the instance is created.
Ok. Let us see the types of Common Resources.
There are two types of common resources,
- Templated resources.
- Customization based on prebuilt resources.
Let’s check how to create both of the common Resources.
The templated resource will have already filled standard fields on which the transformations can be done through mapping.
Template resources include: /contacts, /leads mapped, /companies to CRM and other marketing apps like HubSpot CRM, Hubspot Marketing, Salesforce Sales Cloud, Marketo etc…
In order the build the new common resource, click on the “Build New Common Resource”.
Here, I am choosing the “contacts template” for creating the common resource.
Now, Let’s select the HubSpot CRM instance.
In this step we select the object which we want,
Here, the common resource is named as “hubcontacts”
Here we map the field names to respective vendor’s Field name,
Lets us execute the GET operation,
After execution, we got the respective transformed data in the Body.
Now we will move to the second option.
Customization based on prebuilt resources:
Build new common resources by clicking the option start without a template
We can add the fields based on the requirement.
Respective Transformed output:
We can use Common Resource feature of Open Connectors Capability to extract data by mapping the fields which can be corelated. This common resource can be used in multiple scenarios and reduce the repetitive task or mapping and extracting the general data which is required frequently. This can be achieved by either using the standard templates or by creating our own specific templates.