Itential’s unique automation capabilities enable NetDevOps to trigger workflows via different options best suited for their needs; form trigger, scheduled trigger, event-based trigger, or an API trigger.
As part of Itential’s API Trigger demo series, we’ve shown how teams can map key job variables for automations that can be triggered by single API endpoints. However, there may be times teams need to trigger automations that stem from different versions of the request payload. In part two, see step-by-step how you can use Itential’s data transformation capabilities to build API trigger automations from different calling systems.
In this demo see how to:
- Trigger automations using multiple API endpoints.
- Perform data manipulation through various methods.
- Leverage Itential’s JSON Schema Transformation canvas to transform data from various request payloads to the necessary formats.
Demo Notes
(So you can skip ahead, if you want.)
00:00 Introduction & Demo Overview
02:06 Using JSON Forms to Trigger Automation Workflows
03:48 Comparing Data from Other Systems
04:29 Transforming Data using JSTs
07:09 Triggering an Automation using Itential’s Operation Manager
07:59 Viewing Results of the Automation
