How to initiate Automation from Hexnode?

What is the “Initiate Automation” Remote Action?

The Initiate Automation action is a Hexnode UEM feature that allows administrators to trigger existing, pre-defined automation routines directly from the console, thereby streamlining the deployment of operational resources across managed devices.

• Objective: To provide an on-demand mechanism for running configured Automations against targeted devices.
• Key Function: Ensures the operational integrity of devices by remotely enforcing updates, patches, and configurations.

Understanding the Initiate Automation Feature

Hexnode’s Automate tab is used to create complex workflows with Time (scheduled) or Activity (enrollment, compliance change) triggers. The Initiate Automation action bypasses these triggers, allowing an administrator to execute the complete workflow immediately and manually.

This feature is deployed as a Remote Action directly from the Manage tab.

Key Scenarios for On-Demand Execution

• Immediate Policy Update: Force an immediate association or disassociation of a new policy bundle on a specific group of devices after a successful manual test.
• Emergency Script Execution: Instantly run a custom PowerShell or Bash script (e.g., to patch a zero-day vulnerability or change a local admin password).
• Post-Troubleshooting Cleanup: Apply a comprehensive cleanup or configuration profile after a remote troubleshooting session.
• Compliance Audit: Immediately check the compliance status of a group of devices against a defined automation trigger.

Configuration options for Automation execution

When initiating automation, administrators can leverage filtering options to ensure the automation executes only on devices that meet specific criteria.

Step-by-Step Guide: Initiating Automations from the Hexnode UEM console

The Initiate Automation action can be deployed on a single device or across a selected group of devices.

1. Initiating Automation on a Single Device

   To deploy a pre-configured automation to an individual device:

   1. Log in to your Hexnode UEM console.
   2. Go to the Manage tab.
   3. Click on the required device to open the Device Summary page.
   4. Click on Actions > Deployments > Initiate Automation.
   5. Select the automations to apply from the list of configured automations.
   6. Optional: Enable the option Apply target filters to verify if the selected device meets the filter conditions configured during automation creation.
   7. Then, click Initiate.

   

2. Initiating Automation on Multiple Devices (Bulk Action)

   To trigger automations on multiple devices simultaneously:

   1. Go to the Manage tab.
   2. Select the required devices for the automation deployment.
   3. Click on Actions > Deployments > Initiate Automation.
   4. Select the automations to apply from the list of configured automations.
   5. Configure the following options (optional):
      • Apply target filters: Enabling this option executes the automation only on devices that meet the original target filter conditions.
      • Apply platform: Enabling this option executes the automation only on devices that meet the target platform condition of the automation.
   6. Then, click Initiate.

   

   Creating an Automation Profile (Prerequisite)

   Before you can use the Initiate Automation action, you must first create and save the desired workflow within the Automate tab.

   1. Navigate to the Automate tab and click New Automation.
   2. Define Basics: Provide an Automation Name, Description, and select the target Platform (Windows, macOS, etc.).
   3. Define Actions: Select the specific tasks to be bundled (e.g., deploy a policy, run a script, manage registry settings).
   4. Define Trigger/Schedule: While you must define a trigger (Time or Activity), using the Initiate Automation action overrides this trigger for manual execution.
   5. Define Target Filters: Specify the Included/Excluded groups or custom filters. These filters can be re-applied when the automation is manually initiated.
   6. Save the automation profile.

   Monitoring and Reporting

   After initiating an automation, you can monitor its progress in two key locations:

   Location	Purpose	Details Provided
   Action History (Device Level)	Tracks the execution status for a specific device.	Success/Failure status, initiation time, completion time, and output (useful for checking script results).
   Action History Reports (Automation Level)	Provides a centralized view of the action’s execution across all targeted devices.	Device name, action name, created/completed time, and the overall status of the action.

   Frequently Asked Questions (FAQs)

   Does “Initiate Automation” override the original automation’s schedule or triggers?

   Yes. The Initiate Automation action is an immediate, manual trigger. It bypasses the scheduled time or activity-based trigger defined in the original automation profile, forcing execution on demand.

   Can the “Initiate Automation” action run a custom script?

   Yes. If the automation profile includes the action “Execute Custom Script” (e.g., PowerShell, Bash), the Initiate Automation action will run that script immediately on the target devices.

   Can admin stop the automation once it has been initiated?

   Once the command is sent to the device, it is difficult to immediately revoke it. (You can check the Action History to see if the action is pending or failed.)

   Is there a limit to how many devices I can initiate automation on at once?

   While Hexnode supports bulk actions, performance may be affected by the complexity of the automation (e.g., large app deployments) and network conditions. It is recommended to test complex automations on smaller groups before large-scale initiation.