Workflows, Teams & Agency
Understand the AI automation hierarchy in Lasius - from individual workflows to organization-wide agencies.
Lasius organizes AI automation into a clear hierarchy that scales from simple tasks to complex organizational goals.
The Lasius Hierarchy
Workflows → Teams → Agency
| Level | What It Is | Scope |
|---|---|---|
| Workflow | A single automation pipeline built with connected nodes | Individual task |
| Team | Multiple workflows working together | Specialized function |
| Agency | Multiple teams coordinated to achieve complex goals | Organization-level |
Workflows
A Workflow is the fundamental building block in Lasius. It's a visual pipeline where you connect different nodes together to create an automation flow.
Think of a workflow like a flowchart — data flows from one node to the next, getting processed along the way.
What Makes Up a Workflow?
- Nodes — Individual components that perform specific tasks (input, processing, output)
- Edges — Connections between nodes that define how data flows
- Configuration — Settings for each node (model selection, prompts, parameters)
Example Workflow
A simple Q&A workflow might look like:
[User Input] → [AI Model] → [Response Output]
A more complex workflow with knowledge retrieval:
[User Question] → [Knowledge Base Search] → [AI Model + Context] → [Answer]
Node Categories
| Category | Purpose | Examples |
|---|---|---|
| Input | Receive data into the workflow | Text Input, Chat Input, File Upload |
| Output | Return results from the workflow | Text Output, Chat Output, API Response |
| LLM Models | Process with AI models | OpenAI, Anthropic, Bedrock, Gemini, Ollama |
| Tools | Perform specific actions | Calculator, Web Search, API Call |
| Agents | Intelligent reasoning with tool use | LangGraph Agent |
| Memory | Store and recall information | Conversation History, Redis Memory |
| Knowledge Base | Search your documents | KB Retrieval, Document Query |
| Logic | Control flow and data transformation | Conditional Branch, Loop, Transform |
| MCP | External tool integrations | MCP Client nodes |
Agents
An Agent is a special type of node that can reason, plan, and use tools autonomously. Unlike simple LLM nodes that just generate text, agents can:
- Think step-by-step about how to solve a problem
- Choose and use tools based on the task
- Remember context across a conversation
- Recover from errors and try alternative approaches
Agent Capabilities
| Capability | Description |
|---|---|
| Reasoning | Break down complex problems into steps |
| Planning | Decide which actions to take and in what order |
| Tool Use | Call calculators, search the web, query databases |
| Memory | Remember previous messages and context |
| Self-Correction | Recognize mistakes and adjust approach |
When to Use an Agent vs LLM Node
- Use an LLM Node for simple text generation, summarization, or classification
- Use an Agent when the task requires reasoning, multiple steps, or tool use
Teams (Coming Soon)
A Team combines multiple workflows to handle a specialized function — like a department in an organization.
How Teams Work
- Multiple workflows are grouped together
- Conditional routing directs tasks to the right workflow
- Workflows can share context and collaborate
Example: Customer Support Team
[Incoming Request]
↓
[Router: What type of request?]
↓
┌─────────────────┬─────────────────┬─────────────────┐
↓ ↓ ↓ ↓
[Billing] [Technical] [General] [Escalation]
Workflow Workflow Workflow Workflow
Agency (Coming Soon)
An Agency is the highest level of organization — it coordinates multiple Teams to achieve complex, organization-wide goals.
Think of It Like a Real Agency
| Real World | Lasius Equivalent |
|---|---|
| Marketing Agency | Agency |
| Creative Team, Analytics Team, Content Team | Teams |
| Individual campaigns, reports, content pieces | Workflows |
Example: Marketing Agency
┌─────────────────────────────────────────┐
│ Marketing Agency │
├─────────────────────────────────────────┤
│ │
│ ┌──────────┐ ┌──────────┐ ┌───────┐ │
│ │ Content │ │Analytics │ │ SEO │ │
│ │ Team │ │ Team │ │ Team │ │
│ └──────────┘ └──────────┘ └───────┘ │
│ │
└─────────────────────────────────────────┘
Summary
| Concept | Purpose | Status |
|---|---|---|
| Workflow | Single automation pipeline with connected nodes | Available |
| Nodes | Individual components (input, LLM, tools, output) | Available |
| Agent | Intelligent node with reasoning and tool use | Available |
| Team | Group of workflows for specialized functions | Coming Soon |
| Agency | Coordination of teams for complex goals | Coming Soon |