Before
An operator likely had to search the endpoint management portal for the relevant computer, submit a restart job, and repeatedly check whether the lookup and restart operations had completed. The operator then had to copy the computer and job details back to the requesting workflow or team.
How it works
- Receive a request from a parent workflow and obtain the authentication tokens needed to access endpoint management data.
- Find the target computer, monitor the asynchronous lookup until it completes, and submit a restart job with the configured restart behavior.
- Monitor the restart job until it reaches DONE, then return the computer and execution details to the parent workflow.
Workflow details
- Trigger and authentication: A parent workflow starts the process through a secure webhook. The automation invokes an authentication subflow to obtain the tokens required to work with the endpoint management environment.
- Target identification: The workflow searches for the computer associated with the supplied identifying value, such as the last logged-in user. Because the lookup runs asynchronously, the automation repeatedly checks its status until the computer information is available.
- Restart submission: After identifying the target computer, the workflow submits a restart job for that device. The request informs the user, allows postponement, and forces application shutdown as part of the restart operation.
- Completion monitoring: The restart operation is also asynchronous. The workflow polls the resulting job until its status reaches DONE, stopping the process if a service step fails.
- Parent-workflow handoff: Once processing is complete, the webhook response sends the target computer ID, computer owner, restart job status, and execution timestamp back to the parent workflow for downstream handling.
What changed
A parent workflow can now initiate the endpoint restart through one webhook call. Target identification, asynchronous status checks, restart submission, and completion reporting happen automatically, with the final status delivered directly to the requesting workflow.
Work removed
Searching for the target computer, manually submitting the restart job, repeatedly checking the computer lookup and restart job statuses, and copying completion details back to the parent workflow.
Expected outcome
Each execution removes at least two recurring monitoring activities—the computer lookup check and the restart job check—while consistently returning a completion record to the parent workflow.
