Cyclr has a number of features available to you when connecting to external systems.
For example, you could use the Quick Connector’s “HTTP Request” to drag in and setup a Step that makes a call to pull in some data, or build a Custom Connector for a system’s API to give you a whole suite of Methods to use in your integrations.
To help identify which features to use when, we’ve provided this table so you can quickly understand and compare them:
| Feature: | Quick Connector | Custom Connectors | Managed Library Connectors | Custom Categories |
|---|---|---|---|---|
| Primary Use Case | Rapid testing or one-off connectivity | Full control over connectors (library or private APIs) | Applications that you do not wish to manage or maintain yourself | Systems with custom objects |
| Best When | Confirming method functionality for workflow integration | Working with rapidly changing APIs, Private APIs or specific requirements | Working with mainstream applications | Adding custom objects with minimal configuration |
| Configurability | Medium | High | Low | Low-Medium |
| Maintenance | Self-managed | Self-managed | Cyclr Managed | Minimal |
| Rate Limits | Not Supported | Fully Supported | Fully Supported | Inherits from parent Connector |
| Pagination | Inbound Supported | Fully Supported | Fully Supported | Inherits from parent Connector |
| Time to set-up | Fastest | Most time-intensive | Fast | Fast |
| Field Management | Basic | Complete | Streamlined | Streamlined |
| Use in Production | Custom integrations only | Templates and Custom integrations | Templates and Custom integrations | Templates and Custom integrations |
