Skip to main content

Orchestrator Components

1. Core​

The Core component is the backbone of every orchestration flow. It defines the entry points and triggers that determine how and when the orchestration begins.

It primarily includes two essential nodes:

Start Node​

The Start Node represents the entry point of the application flow. Every orchestration begins from this node. It initializes the execution context, defines what inputs are expected, and prepares the flow for subsequent actions.

You can think of it as the "on switch" for your orchestration, it activates the process when triggered by predefined events.

Channel Trigger Node​

The Channel Trigger Node serves as the bridge between communication channels and the Orchestrator. When a specific channel event occurs such as a message being sent, received, or updated, this node triggers the corresponding orchestration flow.

It allows the Orchestrator to be embedded directly within a channel, ensuring real-time responsiveness to user or system events.

Together, these nodes form the control layer of the Core component, defining how orchestration flows are initiated and connected to ART’s communication framework.

2. Processing​

The Processing component manages how data is transformed, validated, and routed within the orchestration flow. It acts as the logic layer, executing the intermediate steps that shape how input data evolves before reaching its final outcome.

At its heart, the Processing component is powered by Interceptors, the functional units that perform specific processing tasks.

Interceptors​

Each interceptor is a custom processing unit you create within the application. They can handle a variety of operations such as:

  • Message validation and filtering
  • Data transformation or formatting
  • Conditional routing based on message content
  • Security and access control checks

Multiple interceptors can be chained together to form processing pipelines, allowing for complex data flows to be designed visually.

This structure allows developers to implement granular control and flexible logic, ensuring that every step of the workflow can be tailored to specific use cases.

Webhooks​

The Webhook component facilitates one-way, event-driven communication with external URLs, particularly useful when direct WebSocket connections are not required for interaction. Developers can configure Webhooks to send messages or data directly to specified endpoints, enabling seamless integration with external services and systems for tasks like notifications or data forwarding.

3. Agentic AI​

The Agentic AI component is where intelligence comes into play. It integrates the agents you’ve built using Agent Builder directly into your orchestration flow, enabling adaptive, context-aware automation.

Agents​

Agents act as decision-making nodes that can interpret data, apply logic, and execute intelligent responses. They can perform tasks like:

  • Analyzing messages or events
  • Generating responses or summaries
  • Triggering actions based on AI-driven insights
  • Collaborating with other agents within the flow

Each agent can be configured to operate independently or in coordination with others, allowing the creation of multi-agent workflows.

Through Agentic AI, your orchestration gains the ability to reason, adapt, and act dynamically, turning static workflows into living, intelligent systems that evolve with real-time data.