Actions34
- Devices Actions
- Endpoints Actions
- Guest Users Actions
- Local Users Actions
Overview
This node integrates with the Aruba ClearPass API, specifically allowing users to update an Endpoint resource within the "Endpoints" domain under "Identities". It enables modifying details of a network endpoint such as its description, status, MAC address randomization flag, device insight tags, and additional custom attributes.
Typical use cases include:
- Updating endpoint metadata in response to changes in the network environment.
- Managing endpoint statuses (e.g., marking devices as known, unknown, or disabled).
- Adding or modifying tags and attributes for better device categorization and policy enforcement.
For example, a network administrator could automate updating endpoint descriptions and statuses after a security scan or asset inventory process.
Properties
| Name | Meaning |
|---|---|
| Domain | API domain to access. Options: Identities, Policy Elements, Enforcement Profile |
| Endpoint ID | Numeric identifier of the endpoint to update (required when updating an endpoint) |
| Description | Textual description of the endpoint |
| Status | Current status of the endpoint. Options: Known, Unknown, Disabled |
| Randomized MAC | Boolean flag indicating if the MAC address is randomized |
| Device Insight Tags | Comma-separated list of tags associated with the device for insight purposes |
| Attributes | JSON object containing additional key/value pairs representing custom attributes for the endpoint |
Output
The node outputs an array of JSON objects representing the updated endpoint(s). Each item contains the updated data fields as returned by the Aruba ClearPass API after the update operation.
If errors occur and "Continue on Fail" is enabled, the output will contain an error object with a message describing the failure.
No binary data output is produced by this node.
Dependencies
- Requires an active connection to the Aruba ClearPass API.
- Needs an API authentication credential configured in n8n (an API key or token).
- The node depends on an internal helper module (
executeOperation) that handles the actual API request execution.
Troubleshooting
Common issues:
- Invalid or missing Endpoint ID when performing update operations.
- Incorrect or expired API credentials causing authentication failures.
- Network connectivity problems preventing access to the ClearPass API.
- Malformed JSON in the Attributes property leading to request errors.
Error messages:
- Authentication errors typically indicate invalid API credentials; verify and update them.
- Validation errors may arise if required properties are missing or have invalid values; ensure all mandatory fields are correctly set.
- If the node throws an error but "Continue on Fail" is enabled, the error message will be returned in the output JSON under
error.