Each of a Cyclr Parterns Customers will have an account in Cyclr. Templates can be copied to the account or custom integrations can be developed. This provides segmentation between integrations running for different customers. Connectors in an account are specifically authenticated for that customer.
A Connector is a Cyclr implementaion of a an application’s API. The connector handles all aspects of the protocols and methods which Cyclr uses to pull or push data to the application.
Once a Connectors is installed in an account it is referred to as an Account Connector. It holds authentication details specific to that account.
Users can be given access to Accounts, allowing them to install and modify the Account Connectors and Cycles.
Integration Templates are pre-made integrations that can be installed by Users into Accounts as Cycles.
Cycles are integrations in an Account that when activated will perform the integration flow. Cycles can be triggered on a scheduled interval or by a webhook event in a third party application.
A Cycle Transaction is created each time a Cycle is triggered. It segregates the request and response data relating to each Cycle Step from other data, allowing the Cycle to have multiple Transactions in progress simultaneously.
A Cycle is made up of a collection of Cycle Steps. Each Cycle Step may connect with a third party API to send and/or receive data, perform a logic action such as delaying the Cycle Transaction for a period of time, or perform different actions depending on the data received from the third party API.Edit me