Skip to main content
Version: Current

Connections

Overview

The Connections page allows administrators to create and manage secure, reusable credentials used by processes and workflows to interact with external systems and services.

Connections centralize authentication details and provide:

  • Secure reuse across multiple processes
  • Centralized credential management
  • Simplified maintenance and updates
  • Full audit traceability

The Connections page is available to users with the appropriate connection management permissions.


How to access:
From the AI Command Center, navigate to Assets → Connections from the left navigation panel.


Connections View

The Connections tab displays all configured connections in a structured table layout.

ColumnDescription
Connection NameName of the connection.
TypeType of connection (Database, Email, AI, etc.).
Created ByUser who created the connection.
Modified AtDate and time of last modification.
ActionsAvailable operations such as View, Edit, Clone, Delete, or Audit (based on permissions).

Connection Actions

From the Connections tab, the following actions are available (based on permissions):

ActionDescription
ViewOpens the connection in read-only mode.
EditModify the connection configuration.
CloneCreate a new connection based on an existing one.
DeleteRemove the selected connection (restricted if in use).
AuditView the audit history of the connection.

Viewing a Connection

To view connection details:

  • Open the Connections tab.
  • Select the connection.
  • Click View.

The connection opens in read-only mode, displaying its configuration details.


Editing a Connection

To modify an existing connection:

  • Open the Connections tab.
  • Select the connection.
  • Choose Edit.
  • Update configuration details.
  • Click Update.

Cloning a Connection

To duplicate an existing connection:

  • Select the connection.
  • Choose Clone.
  • Provide a new name.
  • Click Add.

Deleting a Connection

To delete a connection:

  • Select the connection.
  • Choose Delete.
  • Confirm the action.
note

A connection cannot be deleted if it is referenced by any process.
If dependencies exist, the system displays the dependent process name and version.


Auditing a Connection

To view audit history:

  • Select the connection.
  • Choose Audit.

The audit log records:

  • Creation events
  • Configuration changes
  • Deletion attempts

Creating a Connection

To create a new connection:

  1. Open the Connections tab.
  2. Click Add Connection.
  3. Select the required connection type.
  4. Provide the necessary configuration details.
  5. Click Test Connection to validate connectivity.
  6. Click Add to save.
note

You must have the Add Connection permission to create a new connection.


Supported Connection Types

Database Connections

Used for executing database-driven activities such as Select, Insert, Update, Delete, and Stored Procedure execution.

Microsoft SQL Server

Supports both SQL Authentication and Windows Authentication (SSPI).

Key Fields

  • Server Name
  • Database Name
  • Authentication Type (SQL / Windows)
  • User Name & Password (SQL Authentication)

PostgreSQL

Used for connecting to PostgreSQL databases using username/password authentication.

Key Fields

  • Server Name
  • Port
  • Database Name
  • User Name
  • Password

MySQL

Used for MySQL database connectivity.

Key Fields

  • Server Name
  • Port
  • Database Name
  • User Name
  • Password

Oracle

Used for connecting to Oracle databases via SID and credentials.

Key Fields

  • Server Name
  • Port
  • SID
  • User Name
  • Password

File & Storage Connections

File System

Used to access local or network file paths from workflows.

Key Fields

  • Folder Path (absolute or network path)
  • User Name
  • Password
note

The AI Command Center server must have network access to the specified path.


AI & Cognitive Service Connections

These connections can be configured using native provider keys or IB-X Currency via Integration Gateway, where supported.

OpenAI

Used to access OpenAI text generation models.

Modes

  • Native OpenAI Key – Bring your own API key
  • Integration Gateway – Uses IB-X Currency (no API key required)

Additional Resources


Llama

Used to access Meta Llama models.

Modes

  • Native Endpoint – Custom deployed Llama endpoint
  • Integration Gateway – Uses IB-X Currency

Additional Resources


Azure

Used for Azure Cognitive Services and Azure Document Analysis.

Modes

  • Azure Native Key – Direct Azure endpoint and access key
  • Integration Gateway – Uses IB-X Currency

Additional Resources


Email Connections

IMAP

Used to read and manage emails from mail servers.

Typical Use Cases

  • Reading incoming emails
  • Processing attachments
  • Monitoring mail folders

Additional Resources

  • IMAP provider documentation (Gmail / Microsoft 365)

SMTP

Used to send emails from workflows and notifications.

Typical Use Cases

  • Task notifications
  • Alerts
  • Custom email activities

Outlook (Microsoft 365)

Uses Azure AD application authentication to access Microsoft 365 mailboxes via Microsoft Graph.

Authentication

  • Client ID
  • Tenant ID
  • Client Secret

Additional Resources


Google

Used to connect to Google services such as Gmail, Drive, and Sheets.

Authentication Types

  • OAuth 2.0
  • Service Account
  • API Key

Additional Resources


WhatsApp Connections

WhatsApp Connections are used to configure secure integration with the WhatsApp Business Platform for sending messages, receiving incoming events, and managing media operations.

IB-X uses secure HTTPS-based communication with the WhatsApp Business Cloud API authenticated through Meta System User Access Tokens.

The connection is configured using credentials generated from Meta Business Manager, including the WhatsApp Business Account details, Phone Number ID, App credentials, and System User Access Token.

This connection enables IB-X Agents to securely interact with WhatsApp Business APIs for messaging and media handling.

Configuration Fields

FieldDescription
WABA IDWhatsApp Business Account identifier associated with the business account.
Phone Number IDIdentifier of the WhatsApp-enabled phone number used for messaging.
System User Access TokenAccess token generated for the Meta system user with WhatsApp permissions.
App IDMeta application identifier associated with the integration.
App SecretSecret key associated with the Meta application.

Additional Resources


Notes

  • Ensure the configured Meta System User has the required WhatsApp Business permissions assigned in Meta Business Manager.
  • The System User Access Token must remain valid and may require regeneration based on Meta access token policies.
  • Incoming WhatsApp webhook events must be properly configured and reachable for trigger-based activities to function correctly.

Security Considerations

  • Sensitive values (passwords, API keys, secrets) are stored encrypted.
  • Integration Gateway connections consume IB-X Currency.
  • Access is governed by role-based permissions.
  • All configuration changes are audit-tracked.

Connections provide the secure integration foundation of the AI Command Center, enabling reliable and scalable interaction with external systems.