How to Build an Itential Workflow Series: Part 4 – Building Your Modular Automation Library

Getting started with automating network infrastructure requires a logical, step-by-step approach. You should start simple with a relevant use case and translate the process into a series of logical tasks. Then, you can build out integrations and surrounding processes to ensure it works with your infrastructure and meets your standards. Last, you will implement your tasks until the workflow is complete.

In the fourth part of the Building Network Automation Workflows with Itential demo series, we continue building on the previous workflow. Now that you can fully automate your use case end-to-end, it’s time to take it a step further and explore how you can build flexible and reusable content pieces that can be standardized and centralized for maximum control and compliance for end-to-end network automation.

In this demo, Rich Martin, Director of Technical Marketing at Itential, shows step-by-step how to:

• Build modular child workflows for common processes that can be reused by other team members in other workflows.
• Use a ServiceNow integration for common tasks like ‘Open and Update Change Request Tickets’.
• Access MS Teams integration to notify teams of an automation’s status.
• Leverage Data Transformations for formatting data between workflows.
• Extend current workflow to use any modular, child workflows.