Skip to main content
Organize related workflows using collections. Group automation by team, department, or business process to keep workflows organized as your automation scales.

​
Why use collections

Organized structure

Group related workflows together for easy navigation and management

Team ownership

Assign collections to specific teams or departments

Visual identification

Use icons, colors, and emojis to quickly identify collections

Scalable growth

Maintain clear organization as workflow count grows

​
Creating collections

1

Navigate to workflows

Open Workflows from your workspace sidebar
2

Create collection

Click New Collection and provide a clear name
3

Add description

Explain what types of workflows belong in this collection
4

Customize appearance

Add an icon, emoji, or color to make the collection easily identifiable
5

Set parent collection

Optionally nest this collection under a parent for hierarchical organization

​
Organization strategies

Choose an organizational approach that matches your team structure and workflow needs.
Organize collections by team or department:Example structure:
  • IT Operations
    • Server Monitoring
    • User Onboarding
    • Security Alerts
  • HR Processes
    • Employee Onboarding
    • Time Off Requests
    • Performance Reviews
  • Customer Support
    • Ticket Routing
    • Escalations
    • CSAT Surveys
Best for: Larger organizations where different teams manage their own automations

​
Collection hierarchy

Collections support nested structures that mirror your organization or business processes.
Create hierarchical structures by nesting collections:
  • Parent collections contain related child collections
  • Child collections inherit context from parent
  • Unlimited nesting depth supported
  • Reorganize by changing parent-child relationships
Example: “Engineering” parent collection contains “Backend”, “Frontend”, and “DevOps” child collections
Hierarchical organization provides:
  • Logical grouping of related workflows
  • Clear ownership boundaries
  • Easy navigation for large workflow counts
  • Flexible reorganization as needs change

​
Managing collections

Update collection name, description, appearance, or parent relationship at any time. Changes don’t affect workflows within the collection.
Move workflows between collections as processes change. Workflows retain their history and configuration when moved.
Deleting a collection also deletes all workflows within it. Export workflows before deletion if you want to preserve them.
Collection deletion is permanent and affects all contained workflows. Ensure you have backups before deleting.
Control who can create, edit, or delete workflows within collections based on workspace roles and permissions.

​
Best practices

Choose names that clearly indicate the collection’s purpose. Avoid vague names like “Misc” or “Other” that become catch-alls.
Indicate which team or person owns each collection in the description. This clarifies who maintains workflows within.
Limit nesting to 2-3 levels deep. Deeper hierarchies become difficult to navigate and maintain.
Quarterly review collections to remove unused ones, consolidate similar collections, and update descriptions as processes evolve.
Begin with a simple structure and add complexity only as needed. It’s easier to split collections than merge them later.