YellowAnt Help Center
  • Overview
  • How to Signup
    • Signup with Slack
    • Signup with MS Teams
    • Signup with Email
    • Inviting Team Members
  • Managing Dashboard
    • Applications
    • Command Workflows
    • Event Workflows
    • Select Teams
    • Console
    • Settings
    • External Links
  • Integrating Applications
    • Marketplace and App Categories
    • Adding an Integration
    • Applications on YellowAnt
      • Airbrake
      • Airtable
      • Alexa
      • Asana
      • AWS Cloudwatch
      • Azure DevOps
      • Bitbucket
      • Circle CI
      • Evernote
      • Freshdesk
      • Github
      • Gmail
      • Google Analytics
      • Google Calander
      • Google Contacts
      • Google Drive
      • HubSpot
      • Jenkins
      • Jira
      • JiraO
      • New Relic
      • Outlook Mail
      • Pagerduty
      • Pivotal Tracker
      • RSS
      • Salesforce
      • Sentry
      • ServiceNow
      • StackExchange
      • Trello
      • Twitter
      • VictorOps
      • Wikipedia
      • YouTube
      • Zendesk
  • Commanding Apps
  • Notifications
  • Workflows
    • Command Workflows
      • Building Command Workflows
        • Trigger
        • Collection
        • Action
        • Using Action Outputs
        • Logical Functions
        • Using Conditional Actions
    • Event Workflows
      • Building Event Workflows
        • Trigger
        • Collection
        • Action
        • Using Action Outputs
        • Logical Functions
        • Using Conditonal Actions
    • Using Templates
  • System Commands
  • Plans and Pricing
  • Developer Community
Powered by GitBook
On this page
  1. Workflows
  2. Command Workflows
  3. Building Command Workflows

Collection

PreviousTriggerNextAction

Last updated 7 years ago

A collection is a way of segregating workflows into sets in order to keep them more organized for every individual. This is totally up to the user and can be treated as having different set of workflows where each set forms a collection with some specific set of tasks. Watch out for custom collections for different domains which will soon launch on YellowAnt.

For command triggered workflows, collections also change the way the workflow is executed.

If you create a new command triggered workflow and do not select/create a collection, by default it gets added to a collection called workflow.

The way to execute such a command workflow would be to simply type: workflow command-name In case you select/add it to a workflow named myset, then the command changes to: myset command-name

Example 1:

In this case, the workflow command is "startmyday" and it belong to the collection "workflow" so the command to execute is "workflow startmyday".

Example 2:

In this case, the workflow command is "startmyday" and it belong to the collection "demo-collection" so the command to execute is "demo-collection startmyday".

We see that you can use the same command name, but place it uner different sets i.e. collections and use it in different contexts altogether without one interfering with the other.

This also makes it very easy for the user to view their workflows in the "My Workflows" panel by giving them an option to view them filtered by collections.