Command View
Visual map of all your automation resources showing agents, workflows, integrations, and how they connect
See your entire automation landscape at a glance - every agent, workflow, integration, and how they connect to each other.
What It Does
Command View provides a visual map of all automation resources in your organization. See every AI agent, workflow, trigger, integration, and human checkpoint displayed as connected nodes. Understand relationships instantly: which agents call which workflows, what integrations each process uses, and where human approvals are required. Answer questions like "What happens if Shopify goes down?" or "Show me everything connected to our CRM" without digging through documentation.
Why It Matters
As automation grows, complexity grows with it. You add agents for different tasks, workflows for different processes, and integrations for different systems. Without a map, it becomes impossible to understand dependencies, identify risks, or onboard new team members.
Command View solves this by making your automation architecture visible. Instead of tribal knowledge about "which agent does what" or spreadsheets tracking integrations, you have a live visual map that everyone can understand.
Business Impact
Reduce onboarding time for new team members from weeks to hours - they can see exactly how your automation works. Identify single points of failure before they cause problems. Plan changes with confidence because you can see downstream impacts before making them.
What You See
Resource Types
Command View displays six types of automation resources:
- Triggers - Entry points that start automations (webhooks, schedules, events, manual triggers)
- Agents - AI agents that think and adapt to complete tasks
- Workflows - Step-by-step automations with defined processes
- Integrations - Connections to external systems (CRM, email, Slack, databases)
- External Resources - Third-party automation platforms (n8n, Make, Zapier) that connect to your system
- Human Checkpoints - Points where human approval is required before continuing
Relationship Types
Connections between resources show how they interact:
| Connection | Meaning |
|---|---|
| Triggers | A trigger starts an agent or workflow |
| Invokes | One resource calls another (agent invokes workflow) |
| Uses | A resource uses an integration (agent uses CRM) |
| Approval | A resource requires human approval before continuing |
How It Works
Resources Declared
When you set up agents, workflows, and integrations, the system records what exists and how resources relate to each other.
Map Generated
Command View reads all resources and relationships, then generates a visual graph showing everything connected.
Explore Visually
Pan, zoom, and click on nodes to see details. Hover over a resource to highlight everything connected to it.
Understand Dependencies
See at a glance what depends on what. If you need to change an integration, you can see every agent and workflow that uses it.
Use Cases
Common Questions
Does the map update automatically?
Yes. When you add new agents, workflows, or integrations, Command View reflects the changes. The map always shows the current state of your automation landscape.
Can I edit automations from Command View?
Command View is read-only for visualization. To make changes, you use the specific configuration pages for agents, workflows, or integrations. Command View shows you what exists and how it connects.
How do I see what a specific resource does?
Click on any node to see details: what it does, what tools or steps it uses, and its current status. For agents, you see tool count and model info. For workflows, you see step count. For integrations, you see connection status.
Can I filter the view?
Yes. Filter by resource type (show only agents), by status (production vs development), or search by name. Useful when you have many automations and want to focus on a specific area.
Last Updated: 2025-11-26