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

Using Action Outputs

PreviousActionNextLogical Functions

Last updated 7 years ago

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. You can access the action outputs by using "@" in any text field in the subsequent actions.

Example:

In the trigger "incident assignment in Pagerduty", a whole lot of data is sent along with the event for us to use in the subsequent actions.

In this step, we see action outputs from Pagerduty being used to create an email body for GMail. At the same time, we can a whole lot of action outputs coming from GMail's send function as well.

In this step, we have action outs of both GMail and Pagerduty available to us for use. Also, we can see "create a task" on Asana is generating more action outputs that you can use.