Skip to main content

Developers · Integrations

How Kinetic integrations are built and reused

Kinetic reaches other systems through Connections and Operations, Ruby handlers and Java bridge adapters; WebAPIs and webhooks let other systems start work in Kinetic. An integration is defined once per space and reused by every form and workflow. When a system is not covered, you add one without changing the platform.

Read Integrations Overview (opens in a new tab) Browse the library

Published integrations include Active Directory, ServiceNow, Salesforce, Jira, BMC Remedy, NetSuite, Microsoft Exchange and AWS IAM. Browse the library

Integration types

Six ways Kinetic connects to other systems

Outbound types reach your systems from forms and workflows. WebAPIs and webhooks work the other way, letting other systems and platform events start work in Kinetic.

Kinetic integration types: direction, where they are used, how they are built and where they run
Type Direction Used from Built with Runs in Use it for
Connections and Operations (opens in a new tab) Outbound Forms, workflows, portals Low-code, in the console Integrator Recommended for new REST, PostgreSQL and SQL Server integrations.
Handlers (opens in a new tab) Outbound Workflows Ruby Workflow engine Custom logic or other protocols, such as SOAP.
Bridges (opens in a new tab) Outbound, read Forms, portals Java bridge adapter Kinetic Agent Live lookups, such as Active Directory users in a dropdown.
Filestores (opens in a new tab) Outbound, read Portals Java adapter Kinetic Agent Stream documents and large files from external stores.
WebAPIs (opens in a new tab) Inbound External systems, agents A workflow with Return nodes Workflow engine A REST endpoint that runs a workflow and returns its result.
Webhooks (opens in a new tab) Event Platform events Configuration Core Post events such as Submission Submitted or User Created to a workflow or URL.

How integrations are reused

Integrations belong to the space. A Connection holds a system's base URL and authentication, and its Operations are named calls any form or workflow can use, so the second application that needs a system reuses what the first one built.

  • Credentials stay out of builds

    Integrator holds credentials apart from users and masks secret values. A workflow references an Operation, never a password.

  • Package multi-step logic as routines

    A routine is a workflow with defined inputs and outputs. Wrap a sequence such as "create the account, then assign groups" once and call it from any Kapp.

  • Configure per environment

    Handlers and Connections are configured per space, so a development space can point at test systems while the workflows stay identical.

Start from what is already built

Kinetic Data publishes handlers, bridge adapters, connections and routines for systems such as Active Directory, ServiceNow, Jira and AWS. Each artifact lists its parameters, results and version history.

Add your own

How to add a new integration

Choose by what the system offers. Most new integrations are Connections and Operations and need no code.

  1. 01

    The system has a REST API or a SQL database

    Create a Connection and its Operations in the console and test each one. If the system publishes an OpenAPI spec, Kinetic can connect to it this way, without code.

    Creating Your First Integration (opens in a new tab)

  2. 02

    You need custom logic or another protocol

    Write a handler in Ruby with declared inputs and outputs. Test it locally, then import it under Plugins and configure it in each space.

    How to Use the Task Test Harness (opens in a new tab)

  3. 03

    A form needs live data the API cannot serve

    Build a bridge adapter in Java and deploy it to a Kinetic Agent you run.

    Building a Bridge Adapter (opens in a new tab)

  4. 04

    Another system needs to start work in Kinetic

    Create a WebAPI, attach a security policy, and build the workflow it runs. Its Return node sends the response.

    WebAPIs (opens in a new tab)

Systems behind a firewall: see Private Network Access (Kinetic Agent) (opens in a new tab) for installation and network rules.

Where to go next

Integration questions

Answered by Kinetic Data. Last updated .

  • Which integration type should I use for a new system?

    Connections and Operations, if the system has a REST API or a PostgreSQL or SQL Server database; the docs recommend them for new work. Use a handler for custom logic or another protocol, and a bridge when a form needs live data the platform cannot reach directly.

  • How do I reach systems behind our firewall?

    Install the Kinetic Agent in your network, usually in a DMZ, and allow traffic from the platform to it. Connection details stay with the Agent, and by default it refuses remote plugin uploads, so your team installs only adapters it has reviewed.

  • Can I modify a prebuilt handler?

    Yes. Copy it, change it, and import your version into the space. Published handlers are versioned, so your copy can sit alongside the original.

  • Can AI agents use these integrations?

    Yes, indirectly. An agent starts a workflow through the MCP server, the Core REST API or a WebAPI, and the workflow calls your integrations with credentials the agent never sees. An AI client with the right permissions can also create Connections and Operations through MCP.

Map the integrations for one of your processes

Bring the systems one process touches. In a free two-hour working session we show which integrations already exist, which you would add, and how the workflow calls them.

Book a working session