n8n-nodes-defensx

The Partner API provides access to DefensX functions for Partners and MSPs.

To use this API, you must first obtain an API key from the API Keys page in the DefensX portal.

After generating the API token, include it in your requests as an Authorization: Bearer header.

For further details directly from DefenseX, refer to the DefensX Partner API documentation.

Changelog

For a history of by-version changes and updates, see the CHANGELOG.md file.

Installation

n8n Cloud

Currently not verified for use with n8n Cloud.

Self-Hosted n8n

Follow the installation guide in the n8n community nodes documentation.

# From your n8n installation directory
npm install n8n-nodes-defensx
# Restart n8n

You can install this node as a community node on your self-hosted n8n instance from the UI (if community nodes are enabled) since it's published to npm as n8n-nodes-defensx, with the following steps:

1. In your n8n instance, go to Settings → Community Nodes
2. Click Install and enter: n8n-nodes-defensx
3. Click Install to add the node to your instance

Usage

This node provides integration with DefensX API v1.3.0 following their provided OpenAPI 3.0.1 specification as retrieved on Dec. 15, 2025.

You can begin using it in a workflow after installation by adding DefensX nodes to your flow (choose any of the available Actions) and adding a matching DefensX API credential.

Note: Initial testing was performed more heavily on read operations. Please test carefully any write operations before using in production and open GitHub issues if you discover issues. The Create operations allow for a JSON object to be submitted, but the form of that object is not defined in the provided spec and has not been reverse engineered for field-specific object creation.

Credentials

Create a new credential of type "DefensX API" and configure:

• API Key: Your Partner API key from DefensX.
• API Root: The base URL of your DefensX API environment.

The node will automatically call the Partner API under the path api/partner/v1.

Resources and operations

The node exposes the DefensX Partner API as:

• Resource: A top-level grouping (based on OpenAPI tags).
• Operation: A specific endpoint (method + path) within that resource.

Parameters are generated from the OpenAPI definition and shown as fields in the node.

Output mode

For OpenAPI-driven operations, the node supports:

• One Item Per Element: If the API returns an array, output one n8n item per array element.
• Single Item (Raw): Return the full API response in a single item.

If the API response is an array (or a primitive), Raw output is wrapped under { "items": ... }.

Raw Request

If you need to call an endpoint that is not yet modeled (or you need full control over the request), use:

• Resource: Raw Request
• Operation: Custom API Query

Then provide the HTTP method, endpoint, query, and body.

Dynamic dropdowns

Some fields load values dynamically:

• Customer ID: Loaded from GET /customers.
• Browser Extension ID: Loaded from GET /customers/{customerId}/browser_extensions and depends on the selected Customer ID.
• Policy Groups IDs: Loaded from GET /customers/{customerId}/policy_groups and depends on the selected Customer ID and Policy Group ID to show Policies as a dropdown for the Show Policy operation.

Pagination handling

Some operations automatically paginate and return the combined list of results by default. Where supported, pagination settings can be used to:

• Fetch all pages automatically (except logs which default to 100 items).
• Optionally cap the total number of returned items.

Development

npm install
npm run build
npm link

License

MIT

Attribution

All trademarks and logos are the properties of their respective companies and are not owned by the author of this integration.