Learn how these KanBo’s customization features allow you to create a whole new world of exciting possibilities.
KanBo application programming interface (API)
Automate processes and accelerate work execution with customized solutions
Many KanBo customers create customized solutions using our Application Programming Interface (API). While you can find numerous opportunities to use the KanBo API in your organization, it is often adopted by teams working in Information Technology (IT).
Essentially, an API is a messenger that sends and receives requests for information from one application to another. IT teams use our API to build powerful integrations and solutions that accelerate work execution across their organizations. The key capabilities of the KanBo API can be boiled down to three main functions that help IT teams build effective business solutions:
- Importing and exporting data
- Automating processes
- Enforcing standardization and compliance.
The native way to build on top of KanBo
KanBo allows users to create plugins that can help you extend and customize KanBo in a native way. With KanBo Plugins you can add buttons to the KanBo UI, automate processes, integrate with 3rd party or legacy systems, show previews of attachments on KanBo cards, and much more – all inside of KanBo!
Some KanBo Plugins help you automate your workflows, others give you a new view into the data you have stored on cards. KanBo Plugins add an extra layer of functionality inside of KanBo and let your team work in a truly customized and precise way that paves a way to success.
Notify external applications about changes in KanBo
Webhooks provide a way for KanBo to automatically notify external applications or services when certain events occur in KanBo. Through Webhooks, KanBo offers a more efficient alternative to using the API to periodically poll for changes. Here are some easy to understand Webhook examples in plain English:
When any changes occur in Board A, call https://www.anyapp.com/xyz
When a new card is added to Board B, call https://www.anyapp.com/abc
A webhook monitors a specified scope in KanBo like Board Collection, Board or Card for the specified events and when the specific event occurs, KanBo calls another system that handles what to do in the case of that particular event.
Webhooks are created and managed by using the Direct KanBo API Access or by third-party apps. See Webhooks API Reference for details about the related API operations.
Pushing data in real-time with SignalR
Integrating with the KanBo ASP.NET SignalR Hub
In modern applications the end users want their data up-do-date and in real time. Regardless of whether you are running a pure web application, a native desktop app or a mobile app: everybody wants their data now!
For .NET-minded developers there is a framework called ASP.NET SignalR. KanBo provides the option to connect to its KanBo SignalR Hub. By leveraging ASP.NET SignalR in your applications, you can get easy-to-implement and easy-to-use real-time push communications.
Custom Document Sources and Custom Data Sources for KanBo
Extend your KanBo Card attachments by any type of Document or Data
KanBo’s primary discipline and the aspect where it truly outshines is in building the perfect work context.
KanBo allows you to access content from various Document Sources like SharePoint, Egnyte, OneDrive, Google Drive, Box etc. into a card just by drag & drop. However, KanBo also gives you a more customizable option in the form of custom document sources.
With custom Document Sources you can integrate any legacy, file system or any other document storage system (i.e. proprietary archiving system) to provide its content to be drag & dropped onto KanBo cards.
The same applies to attaching Data Entities (Objects including their data) from various Data Sources to KanBo Cards like:
- Invoice from SAP
- Lead from Salesforce
- Ticket from ServiceNow
- Customer from Microsoft Dynamics
- Employee from PeopleSoft
- Record for an SQL Database
- JSON from any REST Service, etc.
In order to implement custom document & data sources for your own needs you need to implement the IDocSource and IDataSource interface for KanBo to use it natively.
See the API Reference for details about all KanBo interfaces.