Centreon

Overview

This node integrates with the Centreon monitoring platform via its Web API, allowing users to manage Centreon resources programmatically within n8n workflows. Specifically, for the Service - Delete operation, it enables deleting a specified service from Centreon.

Typical use cases include:

• Automating cleanup of obsolete or decommissioned services in Centreon.
• Integrating service lifecycle management into broader IT automation workflows.
• Removing services based on external triggers or conditions without manual intervention.

For example, when a service is no longer needed or has been migrated, this node can be used to delete it automatically, ensuring Centreon's configuration stays up-to-date.

Properties

Output

The node outputs a JSON object containing the response from the Centreon API after attempting to delete the service. The output includes:

• success: Boolean indicating if the deletion was successful.
• message: A string message confirming the completion of the DELETE request.
• timestamp: ISO timestamp of when the operation completed.
• operation: The string "delete".
• resource: The string "service".
• resourceId: The ID of the deleted service.

Example output JSON:

{
  "success": true,
  "message": "DELETE /configuration/services/{serviceId} completed successfully",
  "timestamp": "2024-06-01T12:34:56.789Z",
  "operation": "delete",
  "resource": "service",
  "resourceId": "123"
}

No binary data is produced by this operation.

Dependencies

• Requires valid credentials for Centreon API access, including base URL, username, and password.
• The node uses the Centreon Web API; thus, the Centreon server must be accessible from where n8n runs.
• The API version parameter must correspond to a supported Centreon API version.
• No additional external dependencies beyond the configured Centreon API credentials.

Troubleshooting

• Authentication errors: If the node fails to authenticate, ensure the provided Centreon API credentials are correct and that the Centreon server is reachable.
• Invalid service ID: Selecting or specifying a non-existent service ID will cause the deletion to fail. Use the dynamic options list to select valid services or verify the ID manually.
• API version mismatch: Using an unsupported or incorrect API version may result in unexpected errors. Confirm the API version matches your Centreon instance.
• Network issues: Connectivity problems between n8n and Centreon will cause request failures. Check network settings and firewall rules.
• Error messages: The node throws errors with messages like "Cannot authenticate to Centreon" or "Failed to fetch services". These indicate credential or connectivity issues and should be resolved by verifying credentials and network access.

If continueOnFail is enabled, the node will continue processing other items even if one deletion fails, returning error details in the output.

Links and References

• Centreon Web API Documentation
• n8n Expressions Documentation
• n8n Node Development Guide