Skip to main content

Integration library

Prebuilt integrations for the systems you already run

Kinetic Data publishes handlers, bridge adapters, connections and routines for common systems, from Active Directory and ServiceNow to AWS and Salesforce. Each entry lists its parameters, results and version history, and links to the source. If a system is missing but publishes an OpenAPI spec, Kinetic can connect to it without code.

Book a working session How integrations are built

In the library Active Directory, ServiceNow, BMC Remedy, Salesforce, Jira, Microsoft Exchange, AWS IAM and VMware vSphere.

Browse integrations

Filter by category

When your system is not listed

This page lists what Kinetic Data has packaged and published. Plenty of systems Kinetic connects to are not here, Workday and Okta among them, because a REST API needs no packaged artifact.

It has a REST API
Create a Connection in the console, add the Operations you need, and test each call. If the system publishes an OpenAPI spec, Kinetic can connect to it this way, without code.
It is a database or directory
SQL Server, PostgreSQL, Oracle and LDAP directories connect directly, so a form can look up a record while someone fills it in.
It sits behind your firewall
Install the Kinetic Agent in your network, usually in a DMZ. It keeps the connection details and reaches the system from inside, so only the Agent accepts traffic from the platform.
It needs custom logic
Write a handler in Ruby with declared inputs and results. Your developers can start from any handler in this library and change it.

The developer guide covers each option step by step: how Kinetic integrations are built and reused. For where integrations fit in the platform, see the integration layer.

Bring the list of systems one process touches

In a free two-hour working session we check each one against this library, show how the rest would connect, and send you a written plan.

Book a working session