CLIODOT CONNECTORS
Connect any system. Make it reusable everywhere.
Build connectors for APIs, applications, databases and internal services.
Define authentication, actions, schemas and execution behaviour once. Then use the connector across workflows, gateways, Surface capabilities and other Cliodot applications.
Stripev2026.07 · OAuth 2.0
ReadyACTION DEFINITION
ONE CONNECTOR. MANY USES.
A connector is not a single API request.
A Cliodot connector is a reusable definition of how a system can be accessed and operated.
It contains the knowledge required to interact with that system consistently:
Authentication Base configuration Actions Triggers Inputs Outputs Validation Pagination Error behaviour Versions Documentation
Once created, the connector becomes infrastructure that can serve many workflows, products and teams.
DEFINE WHAT THE SYSTEM CAN DO
Turn provider operations into reusable actions.
Each connector contains actions that represent a clear operation.
Examples include:
Create a customer Verify a transaction Send an email Fetch a contact Update a database record Generate a report Upload a file Create a subscription Search an internal service
Actions define their method, endpoint, inputs, validation, request mapping and expected output.
Builders can use those actions without repeatedly implementing the provider protocol.
SECURE CONNECTIONS
Model authentication once.
Cliodot connectors can represent common and custom authentication systems, including:
OAuth 2.0 Bearer tokens API keys Basic authentication Custom headers Query credentials Cookies Custom authentication fields No authentication
Authentication configuration remains separate from the reusable connector definition.
That allows the same connector to be installed by multiple organizations using different credentials and environments.
FLEXIBLE CREDENTIAL OWNERSHIP
Managed, customer-owned or hybrid.
Different products require different credential strategies.
Cliodot supports models where:
Cliodot manages the connection
Cliodot securely stores and operates the provider credentials on behalf of the application.
The customer manages the connection
The customer retains credential data and provides the required authorization payload when execution is requested.
Hybrid operation
Cliodot handles selected parts of authorization or verification while the customer controls persistent credential storage.
This allows teams to balance convenience, scale, compliance and infrastructure ownership.
FOR BUILDERS AND ENGINEERS
Create connectors at the level of control you need.
Use structured configuration to define endpoints, authentication and mappings.
Or work directly with the underlying connector definition when precise behaviour is required.
Cliodot can support:
REST services GraphQL services Databases Webhooks Internal APIs Custom protocols System connectors Remote connector execution
The platform provides structure without hiding the implementation.
REUSABLE DEFINITIONS. ISOLATED CONNECTIONS.
Separate the connector from each organization’s access.
The connector defines how a service works.
An installation defines how a specific organization connects to it.
Each installation can carry its own:
Credentials Environment Configuration Authorization state Usage policy Tenant context Version selection
This separation allows one connector definition to serve thousands of isolated installations.
CHANGE WITHOUT CHAOS
Evolve connectors without breaking production systems.
Connector actions and authentication models change over time.
Cliodot supports versioned connector definitions so teams can:
Publish new versions Preserve existing behaviour Test changes safely Pin production workflows Migrate installations deliberately Retire deprecated versions Invalidate affected runtime caches
Production systems remain stable while the connector continues to evolve.
EXECUTION INFRASTRUCTURE
Connectors should not rebuild themselves on every request.
Cliodot compiles and caches the information required to execute connector actions.
The runtime can resolve:
Connector definitions Installed credentials Environment configuration Action schemas Authentication mappings Workflow connector bundles
This reduces repeated database assembly and keeps frequently used integrations ready for execution.
THE FOUNDATION OF CLIODOT
Build once. Reuse across the platform.
A connector action can be used inside:
Workflows
Combine several systems into a business process.
Surface
Publish the action as an SDK method, API, MCP tool, GraphQL operation or WebSocket capability.
Gateways
Expose selected connector operations through managed API routes.
OAuth Apps
Use connector authentication capabilities inside application authorization flows.
Authentication Apps
Power email, SMS and other verification experiences.
Remote
Allow another organization to request and use approved connector capabilities.
The connector remains one reusable source of truth.
DISCOVER AND DISTRIBUTE
A shared ecosystem of integration capabilities.
The Connector Hub gives teams a place to discover, install and publish connectors.
Organizations can:
Use official connectors Publish private connectors Share connectors with selected teams Distribute approved versions Define installation requirements Make eligible connectors discoverable Extend the platform without waiting for Cliodot
The Hub grows the ecosystem while keeping execution and permissions governed.
CONNECT THE SYSTEMS YOUR PRODUCT DEPENDS ON
Build the connector once.
Use it across workflows, APIs, SDKs, applications and organizations.