AppConnector class for managing webhook-based AI integrations

This class represents a specialized integration that connects external applications with AI agents through webhook-style interactions. AppConnectors enable automated responses and workflows by bridging the gap between applications and AI capabilities.

Features:

  • Webhook endpoint management
  • Secure API key handling
  • Agent/group assignment
  • Response routing
  • Event handling

AppConnectors are particularly useful for:

  • Chat platform integrations (Slack, Discord, etc.)
  • Custom application webhooks
  • Automated response systems
  • Event-driven AI interactions
  • Secure API access management

Basic connector setup:

import { AppConnector } from 'mosaia-node-sdk';

// Create a Slack integration bot
const slackBot = new AppConnector({
app: 'slack-app-id',
response_url: 'https://slack.example.com/webhook',
agent: 'support-agent-id',
name: 'Slack Support Bot'
});

await slackBot.save();
console.log('Bot API Key:', slackBot.api_key);

Custom webhook integration:

// Create a custom webhook bot
const webhookBot = new AppConnector({
app: 'custom-app-id',
response_url: 'https://api.example.com/ai-webhook',
agent_group: 'expert-team-id',
name: 'API Integration Bot',
metadata: {
team: 'engineering',
environment: 'production'
}
});

// Configure and activate
await webhookBot.save();
if (webhookBot.isActive()) {
console.log('Webhook URL:', webhookBot.response_url);
console.log('API Key:', webhookBot.api_key);
}

Hierarchy (View Summary)

Constructors

  • Creates a new AppConnector instance

    Initializes an app connector that connects external applications with AI agents through webhook-style interactions. The bot manages webhook endpoints, API keys, and routing of responses.

    Parameters

    • data: Partial<AppConnectorInterface>

      Configuration data including: - app: Parent application ID - response_url: Webhook endpoint URL - agent: Associated agent ID (optional) - agent_group: Associated agent group ID (optional) - name: Bot display name - metadata: Custom metadata object

    • Optionaluri: string

      Optional custom URI path for the bot endpoint

    Returns AppConnector

    Basic webhook connector:

    const connector = new AppConnector({
    app: 'app-123',
    response_url: 'https://api.example.com/webhook',
    agent: 'agent-456',
    name: 'API Bot'
    });

    Advanced configuration:

    const connector = new AppConnector({
    app: 'app-123',
    response_url: 'https://chat.example.com/events',
    agent_group: 'group-789',
    name: 'Chat Integration',
    metadata: {
    platform: 'slack',
    channel: 'support',
    team: 'customer-success'
    }
    }, '/integrations/connector');

Methods

  • Check if the entity is active

    This method checks the active status of the entity. Most entities in the system can be active or inactive, which affects their availability and usability in the platform.

    Returns boolean

    True if the entity is active, false otherwise

    const user = new User(userData);
    if (user.isActive()) {
    // Perform operations with active user
    } else {
    console.log('User is inactive');
    }
  • Convert model instance to interface data

    This method serializes the model instance to a plain object that matches the interface type. This is useful for:

    • Sending data to the API
    • Storing data in a database
    • Passing data between components
    • Debugging model state

    Returns AppConnectorInterface

    The model data as a plain object matching the interface type

    const user = new User({
    email: 'user@example.com',
    firstName: 'John'
    });

    const data = user.toJSON();
    console.log(data); // { email: '...', firstName: '...' }

    // Use with JSON.stringify
    const json = JSON.stringify(user);
  • Convert model instance to API payload

    This method creates a payload suitable for API requests by:

    • Converting the model to a plain object
    • Removing read-only fields (like 'id')
    • Ensuring proper data format for the API

    Returns Partial<AppConnectorInterface>

    A clean object suitable for API requests

    const user = new User({
    id: '123', // Will be removed from payload
    email: 'new@example.com',
    firstName: 'John'
    });

    const payload = user.toAPIPayload();
    // payload = { email: '...', firstName: '...' }
    // Note: 'id' is removed as it's read-only

    await apiClient.POST('/users', payload);
  • Update model data with new values

    This method updates the model's data and instance properties with new values. It performs a shallow merge of the updates with existing data, allowing for partial updates of the model's properties.

    Parameters

    Returns void

    const user = new User({
    email: 'old@example.com',
    firstName: 'John'
    });

    // Update multiple properties
    user.update({
    email: 'new@example.com',
    lastName: 'Doe'
    });

    // Save changes to API
    await user.save();

    This method only updates the local model instance. To persist changes to the API, call save after updating.

  • Save the model instance to the API

    This method persists the current state of the model to the API using a PUT request. It requires the model to have an ID (existing instance). For new instances, use the collection's create method instead.

    The method:

    1. Validates the model has an ID
    2. Sends current data to the API
    3. Updates local instance with API response

    Returns Promise<AppConnectorInterface>

    Promise resolving to the updated model data

    When model has no ID

    When API request fails

    const user = new User({
    id: '123',
    email: 'user@example.com'
    });

    // Update and save
    user.update({ firstName: 'John' });
    await user.save();

    Error handling:

    try {
    await user.save();
    } catch (error) {
    if (error.message.includes('ID is required')) {
    // Handle missing ID error
    } else {
    // Handle API errors
    }
    }
  • Delete the model instance from the API

    This method permanently deletes the model instance from the API and clears the local data. This operation cannot be undone.

    The method:

    1. Validates the model has an ID
    2. Sends DELETE request to the API
    3. Clears local instance data on success

    Returns Promise<void>

    Promise that resolves when deletion is successful

    When model has no ID

    When API request fails

    Basic deletion:

    const user = await users.get({}, 'user-id');
    if (user) {
    await user.delete();
    // User is now deleted and instance is cleared
    }

    Error handling:

    try {
    await user.delete();
    console.log('User deleted successfully');
    } catch (error) {
    if (error.message.includes('ID is required')) {
    console.error('Cannot delete - no ID');
    } else {
    console.error('Deletion failed:', error.message);
    }
    }