- SAP Managed Tags:
Introduction
This blog post provides a step-by-step guide on integrating SAP Sales Cloud V2 with SAP Emarsys using the SAP Integration Suite. The focus is on setting up a straightforward integration flow (iFlow) to extract contact data from SAP Sales Cloud V2 and create corresponding contacts in SAP Emarsys.
The goal is to demonstrate how to connect both systems, using APIs and middleware to automate data transfer. This serves as a foundation for more complex integrations in the future, making it easier to extend the process with additional functionality. A key aspect of this integration is OpenID Connect (OIDC, OAuth 2.0, JWT) based API authentication, which is required to securely access SAP Emarsys. We will cover how authentication works in this context and how to configure it properly within the iFlow.
Prerequisites
Before implementing this iFlow ensure that you have the following:
- An active SAP Integration Suite tenant with Cloud Integration enabled
- Access to a SAP Sales Cloud V2 account with API permissions
- Access to an SAP Emarsys account with API permissions
Implementation
Overview of the Integration Flow
- Start Timer – Initiates the iFlow execution at predefined intervals.
- Set Filter – Applies conditions to select only relevant contacts from SAP Sales Cloud V2.
- Get Sales Cloud Contacts – Fetches contact data via the SAP Sales Cloud API.
- Extract Sales Cloud Contacts – Processes and structures the extracted data.
- Configure SAP Emarsys Request –Prepares the Request and Setting Up OAuth Authentication
- Create Contacts in SAP Emarsys – Sends the contact data via an API request to SAP Emarsys.
In the following sections, each step of the iFlow will be explained in detail.
Step 1: Start Timer - Triggering the Integration Flow
Timer Configuration – Scheduling the iFlow to run at regular intervals
The iFlow is initiated by a timer-based trigger, which ensures that contact data is regularly synchronized between SAP Sales Cloud V2 and SAP Emarsys.
As shown in the screenshot, the timer is configured using a Simple Schedule, where the iFlow runs every hour between February 27, 2025, at 09:00 UTC and March 6, 2025, at 18:00 UTC.
Step 2: Set Filter - Filtering Relevant Contacts
In this step, we apply a filter to ensure that only the necessary contacts are fetched from SAP Sales Cloud V2. First, we limit the selection to contacts associated with the United States. Second, we include only those that have been newly created or updated within the last hour.
After adding the timer to trigger the iFlow, the next step is to insert a Content Modifier to define the query parameters for retrieving the relevant contact data.
- Add a Content Modifier
- Navigate to the Message Header tab.
- Create a new header entry:
- Action: Create
- Name: CamelHttpQuery (you can choose your own name)
- Source Type: Expression
- Source Value: $filter=isContactPersonFor/country eq 'US' and (adminData/createdOn gt '${date:now:yyyy-MM-dd}T${date:now:HH}:00:00Z' or adminData/updatedOn gt '${date:now:yyyy-MM-dd}T${date:now:HH}:00:00Z'})
The filter dynamically adjusts the timestamp to the beginning of the current hour, ensuring that each execution of the integration flow retrieves only the latest contact records.
Step 3: Get Sales Cloud Contacts - Fetching Data from SAP Sales Cloud V2
To retrieve contact data from SAP Sales Cloud V2, we need to set up a Request Reply and connect it to an HTTP Receiver Adapter. This ensures that the iFlow sends a request to SAP Sales Cloud V2 and processes the response dynamically.
1. Setting Up the Request Reply Step
The Request Reply step is required to handle synchronous communication with SAP Sales Cloud. It ensures that the request is sent, and the response is processed before moving to the next step in the iFlow.
- Add a Request Reply step after the Content Modifier.
- Connect the Request Reply step to an HTTP Receiver Adapter.
2. Configuring the HTTP Receiver Adapter
The HTTP Receiver Adapter is responsible for sending the request to SAP Sales Cloud V2. The configuration is as follows:
- Address: The endpoint for retrieving contact persons:
https://mytenant.crm.cloud.sap/sap/c4c/api/v1/contact-person-service/contactPersons - Method: GET is selected to fetch data.
- Proxy Type: Set to Internet, ensuring external API communication.
- Authentication: Basic
- Credentials: Since SAP Sales Cloud V2 requires authentication, we must configure Basic Authentication in the Security Material section of the SAP Integration Suite.
- Set up Basic Credentials in the SAP Integration Suite: Go to "Monitor" → "Security Material" → Create a new "User Credentials" → enter a Credential Name, Username and Password → add the Credential Name in HTTP Receiver Adapter
The dynamic filter query that was set up in the Content Modifier is passed automatically in the request to ensure only relevant contact data is retrieved.
Step 4: Extract Sales Cloud Contacts - Extracting Contact Information
In this step, we process the contact data retrieved from SAP Sales Cloud V2, extract the relevant fields, and format them for further use in the integration. To achieve this, we use a Groovy script that structures the data according to SAP Emarsys' requirements. For simplicity, this example extracts only the first name, last name, and email address, but additional fields can be included as needed.
import com.sap.gateway.ip.core.customdev.util.Message;
import groovy.json.JsonSlurper;
import groovy.json.JsonOutput;
def Message processData(Message message) {
def body = message.getBody(String)
def jsonSlurper = new JsonSlurper()
def jsonResponse = jsonSlurper.parseText(body)
if (!jsonResponse || !jsonResponse.value || jsonResponse.value.isEmpty()) {
throw new RuntimeException("No contact data found. API Response: " + body)
}
def contactsList = jsonResponse.value.collect { contact ->
return [
"3": contact.eMail ?: "",
"1": contact.givenName ?: "",
"2": contact.familyName ?: ""
]
}
def emarsysPayload = [
key_id: "3",
contacts: contactsList
]
message.setProperty("EmarsysBody", JsonOutput.toJson(emarsysPayload)) // Store entire JSON in a property
return message;
}
We start by retrieving the API response as a string and parsing it into a JSON object. If no contacts are found, we throw an exception to prevent unnecessary API calls.
Next, we extract the key attributes needed for SAP Emarsys. In this example, we focus on:
- Email Address (3)
- First Name (1)
- Last Name (2)
We iterate over the contact list and map each contact’s attributes into a structured format. If any of these fields are missing, we assign an empty string to ensure consistency in the data structure.
Once we have extracted the required fields, we structure the data into a JSON payload that SAP Emarsys can process. Since SAP Emarsys uses the email address as the unique identifier, we set the key_id to 3
Finally, we store the structured JSON in a message property (EmarsysBody), making it available for the next step in the iFlow.
Step 5: Configure SAP Emarsys Request
In this step, we prepare the data extracted from SAP Sales Cloud V2 for submission to the SAP Emarsys API. This involves setting up a Content Modifier and configuring the necessary OpenID Connect (OIDC, OAuth 2.0, JWT) based API authentication using the Integration Suite.
1. Add a Content Modifier
First, add a Content Modifier step in the iFlow after the Groovy script. The purpose of this step is to store the payload that will be sent to the SAP Emarsys API.
Before creating the new headers, delete the existing CamelHttpQuery header to avoid conflicts with the new request configuration. To do this, add a new row in the Message Header section and select Delete as the action. Enter CamelHttpQuery as the header name and leave the other fields empty.
Message Header
Next, we need to add the required headers for the OAuth 2.0 request and data exchange with the SAP Emarsys API:
- Go to the Message Header tab.
- Add first header:
- Name: Content-Type
- Source Type: Constant
- Source Value: application/json
- Add second header:
- Name: Accept
- Source Type: Constant
- Source Value: application/json
Message Body
Next, we need to define the message body that will be sent to the SAP Emarsys API. This body contains the structured contact data extracted and formatted in the Groovy script:
- Navigate to the Message Body tab.
- Type: Expression
- Body: ${property.EmarsysBody} - we set this property in the groovy script.
2. Configure OAuth 2.0 Authentication
To connect to the SAP Emarsys API, you need to configure OAuth 2.0 authentication in the Integration Suite. This is done by setting up OAuth 2.0 Client Credentials in the Security Material.
You can obtain the OAuth 2.0 credentials directly from SAP Emarsys or configure them using OpenID Connect with SAP Cloud Identity. For detailed steps on setting up credentials via OpenID Connect, refer to the official SAP Emarsys documentation here.
Alternatively, you can create API credentials directly in SAP Emarsys. You can find the detailed steps here. Ensure that the Token Service URL is correctly set to the SAP Emarsys token endpoint.
When configuring OAuth 2.0 credentials in the Security Material of the Integration Suite, make sure to populate the SCOPE field (e.g.'api'). Missing scope values can lead to authentication errors. For more details on setting up OAuth 2.0 authentication, refer to this SAP Community blog.
Step 6: Create Contacts in SAP Emarsys
In this step, we create new contacts in SAP Emarsys using the extracted and formatted data from SAP Sales Cloud V2. To achieve this, we need to configure a Request Reply Step and an HTTP Receiver Adapter to send the contact data to SAP Emarsys.
1. Setting Up the Request Reply Step
- Add a Request Reply after the Content Modifier.
- Connect the Request Reply to an HTTP Receiver Adapter.
2. Configuring the HTTP Receiver Adapter
- Address: The endpoint for creating contacts in SAP Emarsys: https://api.emarsys.net/api/v3/contact
- Proxy Type: Internet
- Method: POST
- Authentication: OAuth2 Client Credentials
- Credential Name: Your credential name from the previous step
At this point, the contact data extracted from SAP Sales Cloud V2 is ready to be created in SAP Emarsys. The HTTP Receiver Adapter sends the formatted data as a POST request to the SAP Emarsys API.
Validating the Integration
After setting up the iFlow and configuring all necessary steps, we can now test the integration to confirm that contact data is successfully transferred from SAP Sales Cloud V2 to SAP Emarsys.
Step 1: Create a Contact in SAP Sales Cloud V2
To validate the integration, we start by creating a new contact in SAP Sales Cloud V2. In this example, a contact named Emma Evans with the email address emma.evans@alpha.cx.demo.sap was created in SAP Sales Cloud V2.
Step 2: Verify That the Contact is Not Yet Available in SAP Emarsys
Next, we search for the newly created contact in SAP Emarsys using the email address. As shown in the screenshot, the search returns no results, confirming that the contact is not yet present in SAP Emarsys.
Step 3: Execute the Integration Flow
We then manually trigger the iFlow to push the newly created contact from SAP Sales Cloud V2 to SAP Emarsys. The iFlow sends a POST request to the SAP Emarsys API with the contact details extracted and formatted in the previous steps.
Step 4: Confirm That the Contact is Now Available in SAP Emarsys
Finally, we search for the contact in SAP Emarsys again using the email address. This time, the contact is successfully found, confirming that the data transfer was successful. The contact's first name, last name, and email address are correctly displayed in SAP Emarsys, indicating that the iFlow is working as expected.
Conclusion
In this post, we walked through the process of setting up an end-to-end integration between SAP Sales Cloud V2 and SAP Emarsys using the Cloud Integration component within the SAP Integration Suite. We started by configuring the connection to SAP Sales Cloud V2, filtering the data to retrieve only relevant contacts, and extracting the necessary fields using a Groovy script. We then prepared the data for SAP Emarsys, set up OpenID Connect (OIDC, OAuth 2.0, JWT) based API authentication, and sent the data to SAP Emarsys using an HTTP Receiver Adapter.
The successful execution of the integration was confirmed when the contact created in SAP Sales Cloud V2 appeared in SAP Emarsys after the process ran. This demonstrates how easily the SAP Integration Suite can be used to connect SAP Sales Cloud V2 and SAP Emarsys - laying the foundation for more complex processes in the future.
By following these steps, you can build a similar integration in your environment, adapting the filter conditions and field mapping to meet your specific business needs.
4 Comments
