Java SDK documentation
July 28, 2026 ยท View on GitHub
Build durable workflow workers and AI agents with Conductor. This repository documents both OSS and Orkes in place; pages call out capabilities that need Orkes.
Start here
| Goal | Guide | Expected result |
|---|---|---|
| Connect to a server | Server setup and connection/authentication | A local or remote API endpoint accepts SDK requests. |
| Build a workflow and Java worker | Core quickstart | Hello World prints Result: PASSED. |
| Build an AI agent | Agent quickstart | An LLM-backed agent completes through Conductor. |
Build
- Workflows and workflow lifecycle
- Workers, workflow testing, files, and schemas
- Schedules and events
- AI agents, tools, and agent framework bridges
- Curated examples; the complete catalog remains machine-generated.
Operate
- Reliability: timeouts, retries, idempotency, and domains
- Security and secrets
- Deployment, scaling, and graceful shutdown
- Metrics and logging
- Debugging incidents
Integrate
- Spring Boot integration selector
- Spring Boot 3 module
- Spring Boot 4 module
- Google ADK, LangChain4j, and LangGraph4j
Reference and upgrades
- API map and generated Javadocs
- Compatibility matrix
- Upgrade guide
- Agent client control plane, agent runtime, and agent schema
Documentation conventions
- Replace
<VERSION>with a published SDK version from Maven Central. - Runnable commands link to maintained examples and state an expected result. Short Java blocks labeled Fragment need surrounding application setup and link to a complete path.
- Provider credentials belong on the Conductor server, not only in the Java client process. Never place secrets in workflow input or source control.
- Primary guide authors follow the documentation standard.
- Maintainers keeping this tree aligned with the Python SDK follow the documentation parity map.