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
  • Using Action Outputs
  • In the trigger command, since no parameters are being passed, we don't see any outputs available in the next step. And using "@" gives us no options.
  • In this case, a parameter was passed in the trigger command, so we see "build" appearing as a data option.
  1. Workflows
  2. Event Workflows
  3. Building Event Workflows

Using Action Outputs

PreviousActionNextLogical Functions

Last updated 7 years ago

Using Action Outputs

One important feature while creating workflows is to use action outputs. Action outputs are the outputs of a previously added action or coming right from the trigger event itself. In case of command workflows, if no parameter is passed then the action outputs of the trigger remains empty. You can access the action outputs by using "@" in any text field in the subsequent actions.

Example 1:

In the trigger command, since no parameters are being passed, we don't see any outputs available in the next step. And using "@" gives us no options.

In this case, a parameter was passed in the trigger command, so we see "build" appearing as a data option.