Use Case Documentation

ENVOY

Integration & Channel Adapter Layer

Reading time: 5 min
Version: 2.1
Last updated: 2026
4+
Channel Types
Messaging & web
<50ms
Latency
Message routing
100%
Context Sync
Cross-channel
Zero
State Lock-in
Stateless adapters
01 — Overview

The Integration Gateway

Envoy is the Integration Layer in the MADEIRA architecture, connecting AI agents to external communication channels and systems. It serves as the bridge between the intelligence layer and the outside world, handling message routing, protocol translation, and channel-specific adaptations.

Built on the Channel Adapter pattern, Envoy enables MADEIRA agents to interact seamlessly across messaging platforms and web interfaces. Each adapter translates platform-specific events into the unified messaging format while respecting platform constraints and capabilities.

Envoy is not a chatbot. It is the gateway that allows intelligent agents to communicate through multiple channels while maintaining consistent behavior and context across all interactions.

02 — Channel Adapters

Multi-Platform Connectivity

Each channel adapter encapsulates the complexity of platform-specific protocols, authentication mechanisms, and message formats. The unified internal format enables agents to operate identically regardless of the originating channel.

Real-Time Messaging

Instant message delivery with support for rich media, inline interactions, and threaded conversations. Handles user authentication and session management transparently.

Instant DeliveryRich MediaThreaded RepliesInline Actions

Team Workspaces

Enterprise collaboration integration with channel mentions, interactive components, and workspace-level permissions. Supports both synchronous and asynchronous communication patterns.

Channel MentionsInteractive UIWorkspace AuthAsync Support

Mobile Communication

Business messaging integration for mobile-first communication. Supports structured templates, media attachments, and delivery confirmations with session management.

TemplatesMedia SupportDelivery ReceiptsSession Windows

Web Dashboard

Full-featured web interface with real-time updates. Provides rich chat UI with typing indicators, file handling, and formatted message rendering.

Real-Time UpdatesFile UploadsRich FormattingTyping Indicators

Capability Matrix

CapabilityMessagingWorkspaceMobileWeb
Real-Time SyncYesEventsWebhookWebSocket
Media SupportFullFullStandardFull
ThreadingReply-toNativeSessionConversation
Interactive UICallbacksBlocksTemplatesCustom
03 — Message Pipeline

Request/Response Flow

Every message flows through a standardized pipeline that ensures consistent processing regardless of the originating channel. This abstraction allows agents to focus on intent and response, not platform mechanics.

Processing Pipeline

1

Ingestion

Channel adapter receives platform event, validates authentication credentials

2

Normalization

Transforms to unified message format with enriched metadata

3

Routing

Gateway routes to appropriate agent based on binding configuration

4

Processing

Agent processes request, may delegate to swarm for complex tasks

5

Response

Adapter transforms response to channel-specific format, delivers to user

04 — Architecture

Control Plane Integration

Envoy adapters connect to the MADEIRA Gateway (Control Plane) which handles authentication, agent routing, and channel multiplexing. All external traffic flows through this secure boundary, with internal services isolated from direct access.

Channels

External Platforms

User touchpoints

Envoy

Integration Layer

Adapters & translation

Gateway

Control Plane

Auth & routing

Each channel adapter is stateless. Session state and conversation context are managed by the MADEIRA Memory Server (Intelligence Layer), allowing seamless cross-channel continuity without adapter-level persistence.

05 — Configuration

Channel Bindings

Channels are bound to agents via declarative configuration. Each agent can optionally declare channel bindings for external routing, with credentials managed through secure environment variable injection.

The configuration model separates agent identity from channel credentials, allowing the same agent to operate across multiple channels while maintaining consistent behavior and context awareness.

Agent Binding Model

  • Identity: Agent name, persona, behavioral traits
  • Capabilities: Enabled tools and resource access
  • Bindings: Channel-to-credential mappings

Credential Management

  • Secure Injection: Environment-based credential loading
  • Rotation: Hot-reload support for credential updates
  • Isolation: Per-channel credential scoping
06 — Deployment

Integration Path

Channel adapters can be added incrementally. Start with the web dashboard for immediate access, then add messaging platforms as organizational needs evolve.

Phase 1

Web Interface

Start with the dashboard for immediate web access. Configure gateway, enable dashboard, begin agent interactions.

Immediate access

Phase 2

Team Messaging

Add real-time messaging or workspace integration for team communication. Configure credentials, update bindings.

1-2 hours setup

Phase 3

Multi-Channel

Add mobile communication, configure cross-channel context sharing, optimize routing for production scale.

Production ready

Contents