Collections

Workflow Collections provide organizational structure for your automation workflows. Think of them as folders that help you group related workflows together, making it easier to find, manage, and organize your automations as your team grows.

​

Creating Collections

When you create a new collection, you can give it a clear name and description that explains its purpose. Add visual elements like emojis, icons, and colors to make collections easy to identify at a glance. Collections are scoped to your workspace and can be organized in hierarchical structures with parent and child relationships.

Choose descriptive names that indicate the collection’s purpose, such as “IT Operations”, “HR Processes”, or “Customer Support Automation”. Add detailed descriptions explaining what types of workflows belong in each collection to help team members understand the organization system.

​

Collection Hierarchy

Collections support nested structures that mirror your team’s organization or business processes. For example, you might have an “IT Operations” parent collection containing child collections for “Server Monitoring”, “User Onboarding”, and “Security Alerts”. Similarly, an “HR Processes” collection could contain “Employee Onboarding”, “Time Off Requests”, and “Performance Reviews”.

This hierarchical approach makes it easy to find relevant workflows and maintains logical groupings as your automation grows. You can reorganize collections by changing parent-child relationships without affecting the workflows themselves.

​

Organization Strategies

Organize collections based on what makes most sense for your team. Department-based collections work well for larger organizations where different teams manage their own automations. Process-based collections group workflows by business function, which helps when multiple teams work on similar processes. Team-based collections give each team their own space to manage workflows.

Consider creating collections by automation complexity, with separate areas for simple automations, complex workflows, and experimental projects. This helps team members find appropriate templates and examples for their skill level.

​

Collection Management

Collections remain active during normal use and can be edited to update their name, description, visual elements, or organizational structure. When you delete a collection, all workflows within it are also marked for deletion to maintain data consistency and prevent orphaned workflows.

Regular maintenance helps keep your collection structure clean and useful. Review your collections quarterly to remove unused ones, consolidate similar collections, and update descriptions as your processes evolve. Document collection ownership and ensure proper access permissions are maintained.

​

Working with Collections

Once your collections are organized, you can create workflows directly within them, move workflows between collections as processes change, and filter or search workflows by collection. Collections also enable bulk operations when you need to make changes across multiple related workflows.

The collection structure provides the foundation for scaling your workflow usage across teams and departments while maintaining clear organization and governance.