This guide provides ServiceNow administrators with step-by-step instructions for accessing and using Endpoint Central spoke actions within Workflow Studio. Learn how to automate endpoint operations including software deployment, device status monitoring, and encryption key retrieval through six powerful integration actions. Each action includes detailed input requirements, output variables, and troubleshooting guidance to help you build reliable, automated workflows.
Before using Endpoint Central Spoke actions in Workflow Studio, ensure the following:
Follow these simple steps to view and use Endpoint Central Spoke actions in your ServiceNow Workflow Studio:
Once visible, these actions can be dragged directly into your flows and sub-flows.
This action checks whether a target device is currently online and reachable before executing automation tasks.
| Field | Type | Description |
|---|---|---|
| Computer Name | String | Computer name as it appears in Endpoint Central Inventory |
| Domain Name | String | Domain name as it appears in Endpoint Central Inventory |
| Output Variable | Type | Description | Possible Values |
|---|---|---|---|
| Code | String | Operation status code | 0 - Success 1 - Invalid Inputs 2 - API Error 400 - API Call Failed |
| Message | String | Brief explanation of the result |
Code 0: Success |
| Live Status | String | Current status of the machine | Online, Offline, Unknown, or Error |
| Is Online | Boolean | Simple true/false status | true - Device is online false - Device live status is offline, unknown, or error |
This action automatically installs selected software packages on target endpoints.
| Field | Type | Description |
|---|---|---|
| Computer Name | String | Computer name as it appears in Endpoint Central Inventory |
| Domain Name | String | Domain name as it appears in Endpoint Central Inventory |
| Endpoint Central Software Package | List of Records | Software packages from the table 'x_manen_medc_dcsoftwarepackages' These records sync automatically via the scheduled job 'Sync Software details' |
| Output Variable | Type | Description | Possible Values |
|---|---|---|---|
| Code | String | Operation status code | 0 - Success 1 - Invalid Inputs 2 - API Error 400 - API Call Failed |
| Message | String | Brief explanation of the result | Code 0: Success Code 1 (one of the following):
Code 400: API call failed with status code <code_value>. Contact Endpoint Central support and share the application logs. |
| Collection ID | String | Unique ID created by Endpoint Central for the deployment | Example: 76297000000703059 |
This action removes selected software packages from target endpoints.
| Field | Type | Description |
|---|---|---|
| Computer Name | String | Computer name as it appears in Endpoint Central Inventory |
| Domain Name | String | Domain name as it appears in Endpoint Central Inventory |
| Endpoint Central Package | List of Records | Software packages from the table 'x_manen_medc_dcsoftwarepackages' These records sync automatically via the scheduled job 'Sync Software details' |
| Output Variable | Type | Description | Possible Values |
|---|---|---|---|
| Code | String | Operation status code | 0 - Success 1 - Input Error 2 - API Error 400 - API Call Failed |
| Message | String | Brief explanation of the result | Code 0: Success Code 1 (one of the following):
Code 400: API call failed with status code <code_value>. Contact Endpoint Central support and share the application logs. |
| Collection ID | String | Unique ID created by Endpoint Central for the deployment | Example: 76297000000703059 |
This action checks the deployment status of software installation or uninstallation tasks.
| Field | Type | Description |
|---|---|---|
| Collection ID | String | Collection ID returned from Install Software or Uninstall Software actions |
| Output Variable | Type | Description | Possible Values |
|---|---|---|---|
| Code | String | Operation status code | 0 - "Success" or "In Progress" or "Failed" or "Yet to Apply" (see the table below for more details on each status) 1 - Invalid Input 2 - API Error 400 - API Call Failed |
| Message | String | Brief explanation of the result | Code 0: Deployment completed successfully. Code 1: No deployment found for the specified Collection ID. Code 2: Endpoint Central app internal error. Contact Endpoint Central support and share the application logs. Code 400: API call failed with status code <code_value>. Contact Endpoint Central support and share the application logs. |
| Remarks | String | Additional details about the configuration status | This field may be empty or contain messages such as ‘The parameter is incorrect’. |
| URL | String | Direct link to the configuration in Endpoint Central console | Only available when Code is 0 Example: https://endpointcentral.manageengine.in/webclient#/uems/configuration/109832 |
| Status | Description |
|---|---|
| In Progress | The software is currently being installed or uninstalled |
| Failed | The installation or uninstallation process failed |
| Yet to Apply | The configuration is ready and will execute during the next device refresh cycle |
This action retrieves the BitLocker recovery key for Windows devices.
x_manen_medc.bitlocker must be enabled by your administrator.| Field | Type | Description |
|---|---|---|
| Computer Name | String | Computer name as it appears in Endpoint Central Inventory |
| Domain Name | String | Domain name as it appears in Endpoint Central Inventory |
| Recovery Key Identifier | String | The key identifier displayed on the device’s BitLocker recovery screen (BSOD). This value must be provided by the end user. It can also be obtained in Endpoint Central by navigating to BitLocker Management > Managed Computers and clicking the device name. |
| Output Variable | Type | Description | Possible Values |
|---|---|---|---|
| Code | String | Operation status code | 0 - Success 1 - Input Error 2 - API Error 400 - API Call Failed |
| Message | String | Brief explanation of the result | Code 0: Success Code 1 (one of the following):
Code 400: API call failed with status code <code_value>. Contact Endpoint Central support and share the application logs. |
| Encryption Keys | Array of Objects | Contains encryption keys for each encrypted drive | JSON object with array (may be empty or contain one or more keys) |
{
"Encryption Keys": [
{
"drive_letter": "C",
"recover_key": "xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxxxx-xxxxxx"
} ] }
This action retrieves the FileVault recovery key for macOS devices managed through MDM.
The ServiceNow system property x_manen_medc.bitlocker must be enabled by your administrator.
| Field | Type | Description |
|---|---|---|
| Serial Number | String | Serial number of the macOS device managed by MDM |
| Output Variable | Type | Description | Possible Values |
|---|---|---|---|
| Code | String | Operation status code | 0 - Success 1 - Input Error 2 - API Error 400 - API Call Failed |
| Message | String | Brief explanation of the result | Code 0: Success Code 1: ServiceNow system property x_manen_medc.bitlocker must be enabled by an administrator. Code 2: Endpoint Central app internal error. Contact Endpoint Central support and share the application logs. Code 400: API call failed with status code <code_value>. Contact Endpoint Central support and share the application logs. |
| RecoveryKey | String | The actual FileVault recovery key | Format: A1B2-C3D4-E5F6-G7H8-I9J0-K1L2 |