You can give each of your customers an account in Cyclr. The account stores all of the cycles, connectors and authentication details for the customer. This allows you to keep information and data for each customer separate. For more information, see the User accounts overview.
An account connector is a connector that is installed into an account and authenticated against an application that the customer uses.
The Builder is an area of the Cyclr application that allows you to create cycle templates and custom integrations.
A connector allows Cyclr to take and add data to an application. Most connectors use an external application’s API, but some also work with databases and files. For more information, see the Connector introduction page.
The console is your control panel and allows you to set up and manage your application and integrations. Your customers can’t access the console. See the section on Console configuration in the Cyclr documentation.
A custom connector is a connector that you can make within Cyclr to connect with an application of your choice.
Cycles are integrations that run in an account. You can build custom cycles for a specific customer in an account, or create a template that you can use for multiple customers. For more information, see the Template introduction page.
Cycles are composed of a number of steps. A step is usually a call to an application using the connector, but you can also use logic steps to help process data.
When you trigger a cycle, it creates a cycle transation. This separates the request and response data that relates to each step in the cycle from other data, allowing each cycle to have multiple transactions in progress simultaneously.
Embedding is the term Cyclr uses to refer to the process of providing Cyclr integrations to your customer base.
LAUNCH is one of Cyclr’s tools that you can use to embed your Cyclr integrations into your application. You can use LAUNCH to offer a list of cycles to your customers for them to select and self-install into their account.
A Marketplace allows you to set up a store of integrations that you offer to your customers. The Marketplace is a flexible method of providing cycles to your customers as you can offer packages of cycles in a tree-like browsable structure.
You can add sub accounts to accounts within your Cyclr application. Sub accounts allow you to organise multiple related accounts.
Templates are definitions of cycles that you can create and add to any number of accounts. You can run templates for testing but they aren’t usually live. For more information on templates, see the section on Cycle templates in the Cyclr documentation.
Cyclr provides tools as steps that you can add to a cycle in order to process data.