Icon

06_​SugarCRM_​meets_​Salesforce

SugarCRM meets Salesforce

This workflow blends data from two popular Customer Relationship Management (CRM) tools: SugarCRM and Salesforce. This is done by using the REST APIs of these services.

SurgarCRM and Salesforce both use OAuth 2.0 for authentification. This authentification method requires two steps:
1) Pass API credentials via POST Request to get Access Token
2) Use Access Token in GET Request to query API.

Note: This workflow requires the Palladian Nodes for KNIME. This extension can be installed from the KNIME Trusted Community Extensions.

Access token is used as flow variable in requestheader. SQL query is appended to URL string Access token is used as flow variable in requestheader. Query parameters are added to URL string Execute this workflow to blend data from SugarCSM and Salesforce.In order to access the REST API, please provide your credentials in the parameter inputcomponents. Process results and prepare for blending SugarCRMEnter username and password- Client Secret can be left blank- Client ID is sugar SalesforceAPI credentials needed to create HTTP request body:- Username- Password- Client ID- Client Secret Process results and prepare for blending GET OpportunitiesParse JSON resultfor opportunity fieldsPOST to getaccess_tokenfor SalesforceParse resultAuthorization: Bearer<access_token>GETAccountsGETOpportunitiesParse JSON resultfor account fieldsParse JSON resultfor opportunity fieldsJoin account datato opportunity dataPOST to getaccess_tokenfor SugarCRMParse JSON resultfor account fieldsGET AccountsParse resultJoin account datato opportunity dataBlendSugarCRMandSalesforceAdd sourceidentifier forSugarCRMAdd sourceidentifier forSalesforcePass tokenas flow variablePass tokenas flow variableGET Request JSON Path POST Request JSON to Table String Manipulation(Variable) GET Request GET Request JSON Path JSON Path Joiner POST Request JSON Path GET Request JSON to Table Joiner Concatenate ConstantValue Column ConstantValue Column Parameter input Parameter input Process result Process result Process result Process result Table Rowto Variable Table Rowto Variable Access token is used as flow variable in requestheader. SQL query is appended to URL string Access token is used as flow variable in requestheader. Query parameters are added to URL string Execute this workflow to blend data from SugarCSM and Salesforce.In order to access the REST API, please provide your credentials in the parameter inputcomponents. Process results and prepare for blending SugarCRMEnter username and password- Client Secret can be left blank- Client ID is sugar SalesforceAPI credentials needed to create HTTP request body:- Username- Password- Client ID- Client Secret Process results and prepare for blending GET OpportunitiesParse JSON resultfor opportunity fieldsPOST to getaccess_tokenfor SalesforceParse resultAuthorization: Bearer<access_token>GETAccountsGETOpportunitiesParse JSON resultfor account fieldsParse JSON resultfor opportunity fieldsJoin account datato opportunity dataPOST to getaccess_tokenfor SugarCRMParse JSON resultfor account fieldsGET AccountsParse resultJoin account datato opportunity dataBlendSugarCRMandSalesforceAdd sourceidentifier forSugarCRMAdd sourceidentifier forSalesforcePass tokenas flow variablePass tokenas flow variableGET Request JSON Path POST Request JSON to Table String Manipulation(Variable) GET Request GET Request JSON Path JSON Path Joiner POST Request JSON Path GET Request JSON to Table Joiner Concatenate ConstantValue Column ConstantValue Column Parameter input Parameter input Process result Process result Process result Process result Table Rowto Variable Table Rowto Variable

Nodes

Extensions

Links

Download

To use this workflow in KNIME, download it from the below URL and open it in KNIME:

Download Workflow
Created by: rb
Created at: 2017-02-01
On NodePit since: 2021-02-05
Last update: 2026-01-07
Created with KNIME version: v4.1.1
Tags: data blendingRESTSalesforceSugarCRMPalladian

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!