Skip to main content

Connectors & Integrations

Building on the foundational understanding of SyncHive's hub & spoke architecture, let's dive deeper into how Connectors and Integrations operate within this framework, and how they facilitate data exchange between SyncHive—the hub—and the external applications—the spokes.


As the bridges to external systems, Connectors are developed by third-party developers and serve a specific application, like SAP ERP, Salesforce, or AWS S3. These Connectors are not confined to specific instances within those applications; rather, they ensure that data can be accurately sent to and received from the general application environment. They require initial setup within SyncHive to create the pathway for data communication, aligning with the hub & spoke model to enhance scalability and flexibility in data integration.


Integrations are where the specificity of data exchange is defined, managed by SyncHive users themselves. They dictate how a Connector interacts with specific instances of an external application, such as directing data to a specific Salesforce environment or an AWS S3 bucket. This level of detail includes configuring instance-specific information like IDs and webhook keys, ensuring that the data reaches its correct destination.

Connectors & Integrations in Practice

The hub & spoke model simplifies adding or modifying Connectors and Integrations without disrupting existing data flows. As SyncHive acts as the centralized hub, it processes and routes data between the various spokes—external applications—through the defined Connectors and Integrations.

In practice, SyncHive engages with a Connector rather than the external system directly. Taking Salesforce as an example, the Salesforce Connector acts as an intermediary, allowing SyncHive to interface with Salesforce. It is through specific Integrations, tailored for different Salesforce regional instances, that detailed instructions are provided on the precise locations within Salesforce where data should be sent or received from.

Refer to the diagram below: