This is an upcoming feature expected to be released during Q2. Please reach out to us for more information.
The Flows Marketplace is a self-service catalogue, built into Cinode itself, where you can browse the integrations available to your organisation, install the ones you need, configure them, and manage them over time. Everything happens inside Cinode.
A deployed integration is called an instance. An instance is the configured, running copy of an integration on your account, for example your specific connection between Cinode and Kleer, or your Notetaker setup linked to a particular calendar.
This article explains how to access the marketplace, install a new integration, configure it at both the company and user level, and manage your instances afterwards.
Permissions required:
Admin + Flows: install a new integration and configure it at the company level.
Flows: configure your own user-level settings on an integration that is already installed.
Access the Flows Marketplace
Open the left-hand menu and go to Integrations > Marketplace. You will see the integrations available to your account, grouped by category, for example Communication, CRM, and File Storage.
Use the search field and the Category and Status filters at the top right to narrow the list. The badge on each card shows the current state of the integration, for example Not deployed for an integration that has not been installed on your account yet.
Note: Some integrations are paid add-ons. If you are unsure, contact your Customer Success Manager (CSM).
Install a New Integration
Installing a new integration is a company-level action and requires both the Admin and Flows permissions. Users without both can see the marketplace, but cannot deploy new integrations.
To install an integration:
Find the integration you want in the marketplace.
Click Add on the card.
Step through the configuration wizard. The wizard collects everything the integration needs to function, for example API credentials, field mappings, sync schedules, pipeline stage selections, and any other rules specific to that integration. The pages and fields differ for each integration.
Save the configuration to deploy the integration.
Once installation completes, the integration moves out of the Not deployed state and is enabled for the rest of your organisation.
Multiple Instances
Some integrations support more than one instance on the same account. This is used when you need separate copies of the same integration with different settings, for example two Inbound mailboxes routed to different pipelines, or two calendar accounts feeding the same workflow.
If an integration supports multiple instances, you can add a new one by selecting the integration in the marketplace and choosing to add another instance. Each instance has its own name, configuration, and status, and is managed independently of the others.
Not every integration supports multiple instances. If only one instance is allowed, you will not see the option to add another.
Configure Your User-Level Settings
Some integrations also need configuration per user. The company-level setup connects Cinode to the external system, but per-user details, for example each user's own calendar, mailbox, or notification preferences, must be supplied by the user themselves.
If you have the Flows permission, you can configure your own user-level settings directly in Cinode. Open the relevant deployed integration from the marketplace and run the user-level configuration step. You only need the Flows permission for this. You do not need to be an administrator.
Not every integration has a user-level configuration. If you do not see one, the integration is fully configured at the company level by an administrator and there is nothing further for you to do as a user.
Manage Your Deployed Integrations
All your deployed instances are accessible from the marketplace. Open any integration card to see its current status and the actions available on it.
From there you can:
Reconfigure an instance: reopen the configuration wizard to change credentials, mappings, schedules, or any other setting.
Pause or resume an instance: temporarily stop the integration from running without losing its configuration.
Remove an instance: deactivate the integration on your account. Removing an instance deletes its configuration. To use the integration again afterwards, you will need to install and configure it from scratch.
Changes to a deployed instance take effect on its next run.