Embabel Workflow Visualizer

A Spring Boot starter that adds a live workflow visualization UI and REST API for Embabel agents — zero code required.

---

Project structure

This is a multi-module Maven project:

Module	Purpose
embabel-workflow-visualizer-starter	Spring Boot auto-configuration, REST API, actuator endpoint, and visualization UI
embabel-sample-application	Runnable sample Embabel application that uses the starter

Build and test

# Build and test everything from the repository root
mvn test

# Test only the starter module
mvn -pl embabel-workflow-visualizer-starter test

Usage

Compatibility note: this project is currently validated against Embabel 0.4.0-SNAPSHOT (see module POM properties). Because this is a snapshot line, behavior and APIs may change between builds.

1. Add the dependency

The library is published to Maven Central.

<dependency>
    <groupId>com.patbaumgartner.embabel</groupId>
    <artifactId>embabel-workflow-visualizer-starter</artifactId>
    <version>0.1.1</version>
</dependency>

If your project uses Embabel snapshot dependencies, also add the Embabel snapshot repository:

<repositories>
  <!-- Required for com.embabel.agent.* snapshot dependencies -->
  <repository>
    <id>embabel-snapshots</id>
    <name>Embabel Snapshot Repository</name>
    <url>https://repo.embabel.com/artifactory/libs-snapshot</url>
    <releases><enabled>false</enabled></releases>
    <snapshots><enabled>true</enabled></snapshots>
  </repository>
</repositories>

2. Configure your application.properties

# Expose the actuator endpoint over HTTP
management.endpoints.web.exposure.include=health,info,embabel

# Enable the REST API (GET /embabel-workflows/api) and the visualization UI
embabel.workflow.visualizer.enabled=true

Endpoints

Endpoint	Requires	Description
GET /actuator/embabel	management.endpoints.web.exposure.include=embabel	Returns the workflow catalog as JSON
GET /embabel-workflows/api	embabel.workflow.visualizer.enabled=true	REST API — returns the workflow catalog as JSON
GET /embabel-workflows	embabel.workflow.visualizer.enabled=true	Interactive pan/zoom workflow visualization UI

Auto-configuration

The starter activates automatically when:

• The application runs in a servlet web environment (@ConditionalOnWebApplication(SERVLET))
• Spring Boot Actuator is on the classpath

Bean	Always registered	Condition
EmbabelWorkflowCatalogService	✅	Discovers @Agent beans via the ApplicationContext
EmbabelWorkflowActuatorEndpoint	When exposed	Requires management.endpoints.web.exposure.include=embabel
EmbabelWorkflowApiController	Off by default	Requires embabel.workflow.visualizer.enabled=true
WorkflowVisualizerPageController	Off by default	Requires embabel.workflow.visualizer.enabled=true

All beans use @ConditionalOnMissingBean — declare your own bean to replace any of them.

Visualization UI

The UI (GET /embabel-workflows) renders each discovered @Agent as an interactive flow diagram:

• Drag individual nodes to rearrange the layout · Drag the background to pan · Scroll to zoom · Double-click background to auto-fit
• Hover over any node to spotlight its connected edges and neighbours
• Per-agent controls: Fit, Zoom In, Zoom Out, Reset Layout
• Node types color-coded with the 42talents brand palette (cyan, yellow, green, pink, orange)
• Animated flowing arrows on pre-condition edges; AchievesGoal nodes glow green
• Light / dark mode toggle, respects prefers-color-scheme

Sample agents

The embabel-sample-application module ships six demo agents covering common enterprise use cases. Each agent intentionally demonstrates a different workflow pattern so you can see how the Embabel planner handles linear flows, fan-in, branching, converging branches, dynamic cost methods, and static cost declarations.

Agent	Workflow pattern	Description	Endpoint
KycVerificationAgent	Branching + 2× @AchievesGoal	Screens a customer against risk indicators; routes to enhanced due diligence or a direct risk assessment.	POST /api/kyc/verify
FraudDetectionAgent	Linear pipeline, readOnly enrichment	Pure three-step pipeline: data enrichment (no LLM), pattern screening, final decision. Single @AchievesGoal.	POST /api/fraud/detect
SentimentAnalysisAgent	@Cost method + costMethod=	Dynamic cost calculations drive planner decisions; static cost= on the cheap first step. Single @AchievesGoal.	POST /api/sentiment/analyze
ResumeScreeningAgent	Fan-in (no conditions)	Two independent analyses (analyzeResume, assessCultureFit) both start from the same input and converge into a single @AchievesGoal.	POST /api/recruitment/screen
ContentModerationAgent	Converging branches → single @AchievesGoal	Two condition-gated branches both produce TaggedContent; the terminal action operates on that type regardless of which branch ran.	POST /api/moderation/evaluate
LoanApplicationAgent	Branching + static cost= on every action	Two @Conditions split the flow; every @Action declares a static cost= so the planner can weigh paths. Two @AchievesGoal actions.	POST /api/loan/apply

Ready-to-run HTTP request examples for all six agents are in embabel-sample-application/requests/.