SugarCRM REST Connector
Before we explore the SugarCRM REST connector – One of the many application connectors provided by Boomi, we should know what it is.
What is SugarCRM?
SugarCRM is a cloud-based application that helps in sales-force automation, marketing automation, customer support, and account management. Coming back to SugarCRM REST Connector, as already mentioned, it’s an application connector provided by Boomi to connect to and exchange data from the SugarCRM platform. Using this connector, you can directly connect with the SugarCRM platform and GET, CREATE, UPDATE, QUERY, and DELETE data stored in the SugarCRM platform.
Like every other connector in Boomi, SugarCRM REST Connector also requires the SugarCRM Connection and SugarCRM Operation components to connect to the SugarCRM platform.
Stores the essential details required for establishing the Boomi- SugarCRM connectivity.
- Name: One can set the desired name for the connection in this field.
- Base URL: This field is used to store the base URL for the SugarCRM platform.
- Username: Stores the SugarCRM account username.
- Password: Stores the SugarCRM account password.
- Client Id: Stores the Client ID to log into the SugarCRM account.
- Client Secret: Stores the Client Secret of the SugarCRM account used to log onto the SugarCRM platform.
Defines the action that needs to be performed on a specific SugarCRM REST object using the SugarCRM Connection.
- Name: One can set the desired operation name in this field.
- Object: The SugarCRM REST Object against which you want to perform the said action.
- Request Profile: Defines the schema/structure of the request sent to the SugarCRM platform.
- Response Profile: Defines the schema/structure of the response received by the SugarCRM platform.
- Tracking Direction: This enables you to choose whether to track the input or output document and display the same in process reporting.
- Error Behavior: Helps store the error response received from the SugarCRM platform.
- Return Application Error Response: If selected processing continues and passes the error response to the next component processed as the connection output, otherwise stops the processing and reports an error in process reporting.
Cover Photo by Lukas Blazek on Unsplash