Updated on by Susanna Fagerholm
Cyclr boasts an impressive 600+ Application Connector library, ranging from the most popular to the more niche ones. With so many applications at our users’ fingertips, Cyclr offers a strong starting point to help teams connect, automate, and deliver better services through seamless integration.
But what exactly is a Connector? And how does it differ from an API or an integration workflow? Let’s break it down.
A Bridge to External Systems
At its core, a Connector is a set of instructions that tells Cyclr how to communicate with an external system. This includes how to authenticate, what operations can be performed, and how to manage requests and responses. While an integration workflow defines what happens, the Connector enables how it happens, safely and efficiently.
Connectors work as access points into another application’s data, features, and services. Most Connectors are built on top of APIs, although some are designed to work directly with databases or file systems.
Each connector in Cyclr is predefined with a set of operations that the external system has made available. These are known as Connector Methods, and include functions such as updating contacts in Salesforce, creating a new lead in HubSpot, or listing rows from a Google Sheet. Users can then drag these methods into the Builder as steps, and connect them with other methods or tools to create powerful integrations.
Connectors vs. Integration Workflows
It’s easy to confuse a Connector with an API, or even with an integration workflow. Especially since they all work so closely together. But there’s an important distinction:
- An API (Application Programming Interface) is the technical interface exposed by an application that defines how data can be accessed or manipulated. It defines how external systems can interact with an application. APIs are written in code and follow strict specifications.
- A Connector is Cyclr’s implementation that often uses an API. It’s the interpretation layer between Cyclr and external systems, and gives users the ability to interact with a system.
- An Integration Workflow, also known as a Cycle within Cyclr, is a sequence of automated steps built inside Cyclr using one or more Connectors to move or transform data across systems.
In this sense, Connectors are the bridge between systems. They remove the need to manage the unique “language” of every API, translating each into a standard format that can be used within Cyclr’s visual workflow builder.
Multi-Use and Configurable Connectors
Connectors in Cyclr are designed to be reusable. A single Connector can be installed onto a console or an account multiple times. This means that users can utilize the same Connector in different contexts, with separate sets of authentication credentials, or mapped to different data structures.
This allows SaaS teams to create integrations that are easy to scale and adapt. By allowing multiple instances of the same Connector, Cyclr supports scenarios where different clients, regions, or departments require their isolated connection to the same service.
Cyclr’s Connector Libraries
Cyclr organizes its Connectors into two main libraries: Application Connectors and Utility Connectors. Each serves a different purpose within the integration process and contains specific connector types.
Application Connector Library
The Application Connector library holds all connectors that connect to a third-party system, such as an application, a database, a file system, or even an on-prem connection:
- Application Connectors give access to third-party platforms like CRMs, marketing tools, project management systems, or eCommerce platforms.
- Database Connectors offer direct access to databases such as MySQL, PostgreSQL, Microsoft SQL Server, and MongoDB. With these, users can pull records from tables, update rows based on external inputs, or synchronize database entries with other connected applications.
- Universal Connectors, such as our FTP or SFTP Connectors offer broader flexibility by allowing users to work with file systems that do not have a dedicated connector in the library.
- On-Prem Connectivity can be achieved through our SSH Connector.
Utility Connector Library
The Utility Connector Library contains Connectors that are not tied to external systems. Instead, they provide functions that make workflows more responsive and adaptable.
Utility Connectors support temporary or persistent data storage, full data synchronization, and advanced workflow controls. These allow data to be stored between workflow runs or enable repeated processing patterns.
Webhook Connectors are also part of the Utility Connector Library. These Connectors listen for real-time events, such as the submission of a form or the update of a record. When such an event occurs, a workflow can be triggered automatically. Cyclr supports both one-way Webhooks and two-way synchronous Webhooks, which are capable of returning data after a process is completed.
Want to see Cyclr in action?
Book a demo with one of our integration experts to see Cyclr in action and how you could use our embedded iPaaS to enhance your commerce stack!
Need Something More?
Cyclr’s Connector Library is extensive and continues to grow. But sometimes businesses need to integrate with a niche or proprietary system that isn’t yet covered.
When a required system is not yet found in our library, users have two main options to have it added to their Connector selection:
- Request a Custom Connector: Cyclr’s in-house Connector Development Team is available to build new Connectors or maintain existing ones as standards evolve. Users can submit a request for Custom Connectors via our Support Desk.
- Build Your Own: Users on qualifying plans can build their own Custom Connector using Cyclr’s Custom Connector Toolkit. This allows teams to define exactly how a new system should be accessed, including custom methods, authentication, and field mapping.
The Foundation of Integration
A Connector in Cyclr is the vital link between your integration workflow and the external systems you need to communicate with. It wraps the complexity of authentication, API interaction, and data handling into a user-friendly, reusable unit.
In other words, Connectors make integration possible. They are not the final product, but the language that makes conversation between systems clear, structured, and manageable.
With our growing Connector Library, Cyclr provides the foundational elements needed to build reliable, scalable integrations between applications, databases, and other services.
