Integrating with SaaS Applications - Example CRM Connector Integration

DZone 's Guide to

Integrating with SaaS Applications - Example CRM Connector Integration

The continuation of this series presents sample blueprints that demonstrate how an integrated CRM connector might fit in your company's architecture.

· Integration Zone ·
Free Resource

Example CRM connector integration

The previous article in this series looked at a SaaS CRM integration example.

The foundation for this logical diagram was researching a use case where customers were successful with a portfolio solution. It's a starting point for the generic architectural blueprint that arises from several customer solutions that were researched.

Having completed the outline of the blueprint details and the resulting logical diagram elements, it's now time to take a look as specific examples.

In this article we'll go a little deeper than the previous example integration with a SaaS customer relationship management (CRM) applications, exposing how a connector can be tailored to your specific integration needs.

  You may also enjoy: Integrating With SaaS Applications — An Introduction

Blueprint Scenarios

As a reminder, the architectural details covered here are based on real customer integration solutions using open source technologies.

The example scenario presented here is a generic common blueprint that was uncovered researching customer solutions. It's my intent to provide a blueprint that provides guidance and not deep technical details.

This section covers the visual representations as presented. There are many ways to represent each element in this architectural blueprint, but I've chosen icons, text and colors that I hope are going to make it all easy to absorb. Feel free to post comments at the bottom of this post, or contact me directly with your feedback.

Now let's take a look at the details in this blueprint and outline the solution.

Integrating Using Connectors

The example blueprint shown in figure titled External CRM Integration outlines how to integrate an external SaaS CRM application into your architecture. Note that this diagram is focusing narrowly on the aspects related to integrating with an external SaaS CRM application; therefore, it's detailing a small set of integration components.
External CRM Integration
While it's common to represent a collection of integration microservices as the point of contact for your external CRM systems, it's not clear how that's done. While the specific details of connecting to a specific CRM system goes beyond the details of this architectural blueprint, it's not out of scope to expand one level deeper and expose a specific integration connector.

The example blueprint shown in figure titled Example: External CRM Connector Integration shows how a specific integration connector has been implemented. This specific connector is tied closely to the external SaaS CRM's provided API and can ensure data and communications with your organization's internal applications.

External CRM ConnectorFor example, if you are connecting to an external CRM such as Salesforce, you could find that your integration needs are more specific than the existing microservices collection can handle. In this case, it makes sense to facilitate the specific integration needs with a specific Salesforce connector.

Implementation details are left up to the reader to quantify as each organization's needs and usage of a specific SaaS CRM cannot be captured in a generic architectural blueprint beyond the above.

What's next

An overview of the series on integrating SaaS applications portfolio architecture blueprint can be found here:
Catch up on any articles you missed by following one of the links above. Next in this series, taking a look at integration with third-party SaaS or SaaS-like platforms.
architecture ,blueprint ,connectors ,crm ,developers ,how to ,integration ,red hat ,saas ,saas integration

Published at DZone with permission of Eric D. Schabell , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}