Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Configuring outputs for an automation

Updated on April 6, 2022

Define specific outputs in an automation rule to create a contract so that users understand how to use your API. The outputs define the data that the system returns to an external application.

  1. Create a new automation or open an existing automation.
    Create a new automationFollow the steps in Creating an automation.
    Open an existing automation
    1. In the navigation pane of Dev Studio, click Records.
    2. Expand the Technical category and click Activity.
    3. Locate the automation for which you want to simulate a JSON response and click in its row.
      Automations have the AUTOMATION activity type.
  2. On the Definition tab, in the Outputs section, in the Name field, enter a name for the output.
    For example: Automation errors.
    Result: The system automatically populates the ID field with the name that you enter in the Name field.
  3. Optional: Edit the name in the ID field.
  4. In the Description field, enter a description of the output parameter.
  5. In the Data type field, select the data type of the output parameter.
  6. The following data types have additional configuration options:
    Data typeConfiguration
    • Page
    • Page List
    In the Options / Page class field, enter or select the class to which this output belongs.
    TextFor more information on configuring text outputs, see Configuring validation for text inputs and outputs in automations.
  7. Optional: To add additional outputs, click Add output.
  8. Optional: To delete an output, click Delete.
  9. Click Save.
  • Previous topic Configuring inputs for an automation
  • Next topic Configuring validation for text inputs and outputs in automations

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us