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

Trigger

PreviousBuilding Command WorkflowsNextCollection

Last updated 7 years ago

A trigger for a command workflow is a command that triggers actions across various applications. The initiation point is when the user executes that command in the chat window or the YellowAnt native console. This means the workflow carries out the entire chain of events only if this command is executed and in no other circumstances. When you start building a workflow, you will be asked to create a command or it gets created with a default name.

Here we see, the default command name is: my-custom-workflow-name If you create another one with default name, it just gets appended by a number: my-custom-workflow-name-2

Here we see, the user command name is: startmyday You can also see the collection is: demo-collection