SugarCRM is a customer relationship management platform that collects all the data that you need across departments.
You can use IBM App Connect to pass key data between SugarCRM and other apps – automatically, in real time. You can do so using configuration and data mapping without a need for coding, and can achieve a return on your investment in minutes/hours, not days/months.
This guide shows you how.
If you can’t find what you want, or have comments about the “how to” information, please either add comments to the bottom of this page or send us comments by email.
A business scenario
You’re a busy Sales professional with a lot on your plate. You want to make sure that you’re getting the right information to your customers at the right time. For that, you need to understand your customers and their needs. So you’re using SugarCRM as your CRM to stay on top of your sales processes at every step ‐ from initial lead management and customer communication, through reporting, invoicing, and customer payment.
To make the most of SugarCRM’s powerful features, you want to make sure that it has access to all the valuable customer information handled by your other apps, like leads from your sales apps, attendees at events, and completed questionnaires. But you don’t have the time to transfer all this information manually.
How App Connect can help
When a new lead, contact, or other customer data is added to SugarCRM, App Connect automatically passes key data to other applications. So no more time wasted manually transferring your lead data to other applications.
Similarly, you have other applications that generate contacts, leads, opportunities, and other customer data. You would waste precious time adding the data manually to SugarCRM. Again, IBM App Connect can help, automatically updating SugarCRM in real time, adding the leads (or other customer data) that other applications generate. IBM App Connect automates the sharing of this valuable data across these different apps.
What should I consider first?
Before you use App Connect Designer with SugarCRM, take note of the following considerations:
Before you can use SugarCRM in App Connect flows, you need to connect App Connect to SugarCRM. For this you need to find the required values for the following settings in SugarCRM:
- Client ID (SugarCRM Consumer Key value)
- Client secret (SugarCRM Consumer Secret value)
- User ID (SugarCRM User Name value)
- Host name
For Client ID and Client secret, use the SugarCRM OAuth Keys tab to get the values from an existing OAuth key or create an OAuth key for use with App Connect. A SugarCRM admin can set any value but should make the secret long to make it sufficiently difficult to identify.
For User ID and Password, use the SugarCRM Administration (User Management) tab to get the values from a user created for use with App Connect. (In SugarCRM, if the same user is used on two computers, one computer is logged out. A user created for App Connect prevents a real user being logged out if their user name and password are used to connect App Connect to SugarCRM.)
For Host name, use the host name from the address when you are connected to your SugarCRM; for example:
https://zkoptk7946.trial.sugarcrm.eu/#bwc/index.php (as shown in the preceding screen captures).
Example of settings used in App Connect to connect to SugarCRM
In App Connect Designer, when you choose to connect to SugarCRM you are given a form to complete and save. Here is an example of the form, with the values used in the preceding examples:
Create an event-driven flow that adds a new Eventbrite attendee as a SugarCRM lead and sends different emails for new or existing leads
Learn how easy it is to use App Connect Designer to create an event-driven flow that when someone registers for an event in Eventbrite, creates a lead in SugarCRM and sends the attendee an email depending on whether or not they are an existing lead.