Comment on page


This section covers specific details for each of Kubiya's connectors. Kubiya offers native integration with a variety of common cloud providers and solutions. For users who require a customized solution or want to extend functionality, the platform also supports integration with any RestAPI or platform through custom connections. For more information on connectors specifically, please refer to the custom connections SDK section.
Connections are a pivotal part of Kubiya workflows, allowing developers to establish a centralized repository of actions that can be reused across various workflows. They offer a uniform method to access and manage actions, hence enhancing modularity and promoting code reuse.

What are connectors?

Connections are collections of actions that can be executed during a chatbot conversation. Actions are concise, independent units of code designed to accomplish a particular task and deliver a result. They can be summoned using the action type within a workflow.
For instance, a connection might comprise an action that fetches the current time or an action that lists available virtual machines.

How do connectors work?

Connections are realized as a suite of APIs provided by the Kubiya SDK, ready to be called by Kubiya. When a Kubiya workflow calls an action, it supplies any necessary parameters to the connection and obtains a result in return. This result is then utilized as input for other actions or workflow stages.
Connections can be designed for specific tasks, such as accessing a database or engaging with a cloud platform. They also support various programming languages, though currently, only Python is endorsed.