Overview
A PowerShell action runs a PowerShell script as one step of a workflow. It runs with a PowerShell profile, on the Callgoose cloud or on your own automation runner.
You need
Permission to manage automation actionsWhere
Automation > ActionsResult
A PowerShell step for your workflowsCreate the action
- Go to Automation > Actions, choose Global or a team, click Add Action and choose PowerShell.
- Optional: Copy From a Callgoose action or one of yours, then change it.
- Fill in the fields below and click Save.
| Field | What to enter |
|---|---|
| Name, Description | What the action does. |
| Have Argument | Yes if the workflow passes arguments. |
| Version | The PowerShell version. |
| Powershell Script File | Write the script in the editor or upload it. |
| Files from Git or Callgoose | Keep the files in SQIBS, or in Git with an action entry file. |
| Success Exit Code | The exit status that means success, usually 0. |
| Expected Run Time(in Minutes) | 1 to 60. Longer than this counts as failed. |
Example
Restart a stopped Windows service and check it is running.
Test the script or command on a test host first. It runs with the rights of the profile's user, so give that user only what the task needs.