Getting Started

Endpoints

Patch Management

Vulnerability Management

Software Deployment & IT Assets

Automation & Remote Desktop

Real-Time Reports & Alerts

Account Access & Management

SSO Authentication

Security Concerns

Need Help?

Action1 5 Documentation 5 Creating an Automation

Creating an Automation

This is a general instruction on creating an Action1 automation. For a certain automation type, please follow the corresponding reference link.

Important! To create or modify an automation, a role with Manage Automations permission is required.
For Deploy Updates automation:

  • To use the ‘Auto-approve updates’ option, the Approve Updates permission will be required.
  • To disable automatic Windows updates during the automation execution, the “Deactivate Updates in Windows Settings” script is used. So, the underlying Use Scripts permission will be granted automatically, with the Script permission scope and ‘Include scope’ set to that script only.

For Run Script automation:
To use the ad-hoc scripts or scripts from the Script Library, the Use Scripts permission will be required.

  • Using scripts from the Script Library will require the Script scope.
  • Using ad-hoc scripts will require the Ad-Hoc Script scope.
    See also: Permissions in Detail

 

  1. Navigate to the Automations page.
  2. Click + New Automation and specify an action to be performed by the new automation.

Tip: Alternatively, you can go to the Endpoints page, select the required endpoints, and start the automation wizard from the Actions menu.

  1. Configure the settings for the action to be executed:

Available Actions for Automations on Windows, Mac, and Linux Endpoints

Action Description Available for Windows?
Available for Mac? Available for Linux?
Deploy Software Use to install more apps from the Action1 Software Repository. Yes Yes No
Deploy Update Use to install missing patches and critical updates. Yes Yes Yes
Reboot Use to reboot the endpoint. Yes No No
Run Script Use to enter a new script or select an existing one from the Script Library. You can also select to execute the script only if the automation condition script returns a non-zero error code. Yes Yes Yes
Uninstall Software Use to uninstall the software. Yes No No
Update Ring Use to roll out updates in stages. Yes Yes No
  1. On the Select Endpoints step, specify the target endpoints. Action1 enables you to add endpoints individually or as an endpoint group.

NOTE: Consider the following:

  • To specify ALL as the automation’s target endpoints, the Organization scope will be required. 
  • Creating an automation for a group of endpoints is only allowed if all endpoints in the group are visible. Visibility may be limited if the group contains endpoints that belong to another group excluded by the View Endpoints permission. Similarly, specifying individual endpoints by ID is restricted if those endpoints are part of a group that has been excluded through the View Endpoints permission.
  1. On the Schedule step, provide an automation name and define how often you want to run the automation. You have the following options:
      • One-time action: run the automation once, now or at a specified time.

NOTE: If the action (e.g., script execution) is configured with the Run Now option selected, it will not be included in the list of automations, since only actions with schedules are considered automations. However, its execution records will be displayed in the History page.

    • Scheduled: run the automation every X hours, every day, every week, or every month.
    • Not scheduled: run the automation later when needed.
  1. Set the Missing schedule time frame setting so that the powered-off endpoints can catch up with the automation. Make sure the time frame does not exceed the frequency of the execution, i.e., do not set it to 3 days for automations running daily.
  2. Once ready, click Finish.
Reboot - step 1

New automation will be added to the list on the Automations page.