search
CATAPA Apps

Digital Employee Detailed Block Diagram

hashtag
Digital Employee Overview

Digital Employee Core is the SDK designed to make building digital employees easier. The SDK contains common connectors, agents, and functions to build or run a digital employee. One of the components is the digital employee class itself.

When creating a digital employee, you will use a pipeline (GL Pipeline) as the foundation. For each step in the pipeline, we can customize the step as desired. We can create many implementations for each step. For example, we can execute an agent in that step (Agent as step), execute a pipeline in that step (Pipeline as step), or implement another simple logic (Non-agent and non-pipeline as step).

hashtag
Why a Pipeline Is Introduced

  1. Efficiency: Fewer LLM calls — reduced operational cost

  2. Maintainability: Modular step design — independent changes without cascading effects

  3. Reproducibility: Deterministic execution — same inputs produce same outputs

  4. Responsiveness: Fewer LLM calls — reduced end-to-end latency

  5. Testability: Isolated step boundaries — independent testing of each step

hashtag
Digital Employee Application

Previously, digital employees ran on an AIP server, but now, by default, each digital employee should have its own server to run the digital employee pipeline so that it doesn't have a dependency on the AIP server.

Since digital employees now have a pipeline component, it is beneficial to run it in the digital employee application itself for scalability reasons, and there is no equivalent AIP runner for the GL pipeline.

The digital employee application will be integrated with GLChat so that GLChat can execute digital employees with the GL pipeline as a foundation instead of executing agents on the AIP server. When the digital employee pipeline consists of a step related to an agent, the execution of that agent also doesn't run on the AIP server; it will run on the digital employee server itself.

The digital employee runner should be isolated from the main digital employee application so that it will not affect the main application when there are errors or any risks in the runner. We can call this running in a sandbox.

We recommend reusing the digital employee application for multiple digital employee instances. For example, CATAPA can create one digital employee application that consists of two digital employee instances: digital employee payroll officer and digital employee payroll analyst. Choosing whether to combine a new digital employee with an existing digital employee application or create a new digital employee application currently depends on your use case and requirements, especially from a scalability perspective.

Last updated