Konnectify
KOMP+Konnectify

What is KOMP?

KOMP is a customer-owned iPaaS product. The organization that owns KOMP acts as the admin and can provide integrations to its customers through an iframe or as part of its product.

Customer-owned iPaaSEmbedded integrationsAI agents & workflows

Overview

The organization that owns KOMP administers its environment as the admin. It can configure the integration experience, prepare reusable templates, and provision customer access.

Customers can use KOMP through an embedded iframe or as an integration experience within the KOMP owner’s product.

Getting Started

Setup Overview

Create the account, select its primary app, create an RSA token, activate the apps you need, and add your customers.

1

Create the account

Create the KOMP account using the account-creation APIs provided by Konnectify.

2

Select a primary application

After account creation, the admin selects the organization’s primary app.

Primary application selection screen

Select the primary application for the KOMP organization.

3

Create an RSA token

Select New at the top right, choose RSA Token, name the token, and create it. This token lets the admin access KOMP functionality.

New RSA token menu

Choose RSA Token from the New menu.

Create RSA token screen

Name the token and create it.

4

Activate apps and add credentials

Open Apps, activate the applications you plan to use, and enter the required credentials to authorize each app.

Application credentials setup screen

Enter the credentials needed to connect an application.

5

Create customer accounts

From Customers, select New and create the customer accounts that will use the integration experience.

New customer creation menu

Create a customer from the New menu.

Modules

Use these modules to manage connected apps, templates, customers, execution history, and account settings.

01 · CONNECTIONS

Apps

Browse marketplace apps for AI agents and integration workflows. Activate the apps you need and provide their credentials.

Apps available in the Konnectify marketplace
02 · AI AUTOMATION

Agent templates

Configure reusable AI agent templates. The admin publishes and activates a template for customers. Customers connect their accounts, review or adjust the setup, then turn it on. They can also create custom templates.

Agent templates workspace
03 · WORKFLOW AUTOMATION

Konnector templates

Configure, publish, and activate reusable workflows for customers. Customers connect their accounts, review and adjust a template if needed, then turn it on. They can also create custom templates.

Workflows can use marketplace apps and Konnectify tools such as webhooks, repeaters, delay, paths, filters, code blocks, and PDF Parser.

Konnector templates workspace
04 · CUSTOMER ADMIN

Customers

Create and manage customer accounts that receive access to your KOMP-powered integrations.

Customer management page
05 · EXECUTION HISTORY

Event logs

Review execution history, check successful and failed runs, and inspect failure details.

KOMP event logs page
06 · ADMINISTRATION

Settings

Manage the KOMP account and organization configuration:

  • Users: View user details.
  • Billing: Check plan and task usage.
  • Portal customization: Set the customer portal’s appearance.
  • Tokens: View created tokens.
  • Org settings: Edit the primary app and customer previews.

Users

View users and their account details.

Users settings page

Billing

Review the current plan, task usage, and available plans.

Billing settings page

Portal customization

Configure how the KOMP portal looks for your customers.

Portal customization settings

Tokens

View the tokens created for the account.

Created tokens in settings

How to Use KOMP

Follow these steps to publish an integration and give your customers access to the KOMP v3 portal.

1. Publish an integration

  1. Create an agent template or Konnector template.
  2. Publish the template and turn it on so customers can see it.
  3. Publish KOMP as a marketplace app in your product. Your end users open the app from your product.

2. Create an RSA signing key

In KOMP v3, create an RSA token with POST /settings/tokens:

{ "name": "<token-label>", "tokenType": "RSA" }

The create response’s token field contains the private key. Save it immediately in a server-side secret store. The token list/read response contains the public key. Never expose the private key in browser code.

3. Sign a customer JWT on your server

Use the RSA private key to sign a short-lived JWT with RS256. Install jsonwebtoken in your backend. Set projectId and the configured customer externalTenantId; include externalUserId only when you want to map an existing tenant user.

import jwt from 'jsonwebtoken';


const privateKey = process.env.KOMP_RSA_PRIVATE_KEY;
const projectId = process.env.KOMP_PROJECT_ID; // optional only when a default project is configured
const externalTenantId = process.env.KOMP_EXTERNAL_TENANT_ID;
if (!privateKey || !externalTenantId) throw new Error('Configure the private key and external tenant ID');


const now = Math.floor(Date.now() / 1000);
const token = jwt.sign({
 ...(projectId ? { projectId } : {}),
 externalTenantId,
 // externalUserId: 'customer-user-id', // optional: existing mapped user
 iat: now,
 exp: now + 60 * 60 // example: 1 hour
}, privateKey, { algorithm: 'RS256' });


const domain = process.env.KOMP_DOMAIN; // your KOMP subdomain
const customerUrl = `https://domain.konnectifyapp.co/komp/ui/apps?token={encodeURIComponent(token)}`;

Set iat and exp to Unix timestamps in seconds. Use the customer’s configured external tenant ID; do not invent a tenant or project ID.

4. Build and share the customer URL

Replace {domain} with your KOMP subdomain, without https://. Replace {token} with the signed JWT from step 3.

https://{domain}.konnectifyapp.co/komp/ui/apps?token={token}

5. Embed the portal (optional)

If you want the portal inside your product, use the same domain and JWT in this iframe:

<iframe src="https://{domain}.konnectifyapp.co/komp/ui/apps?token={token}"
 width="100%" height="600" frameborder="0" allowfullscreen>
</iframe>
Keep access secure

Keep the private key on your server, use short-lived JWTs, and redact the token query parameter from access and proxy logs.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article