n8n-nodes-autoelevate

An n8n community node for the AutoElevate Partner API, providing MSP automation for endpoint inventory, elevation activity, approval workflows, and partner usage.

n8n is a workflow automation platform that lets you connect AutoElevate to your PSA, reporting, security, and notification workflows.

AutoElevate API Beta Status

Beta notice: AutoElevate identifies its Partner API as beta and states that it may change without notice. This node pins requests to /api/v1 and automatically sends the mandatory beta acknowledgment header required by the API. Test workflows before using approval or denial actions in production.

Features

• Complete coverage of all endpoints published in the AutoElevate Partner API v1 specification
• API Token (AE-BEARER) and signed HMAC (AE-HMAC-SHA256) authentication
• Searchable company, computer, location, elevated-session, and elevation-request selectors
• Automatic offset and cursor pagination
• Picker searches that scan all available API pages when AutoElevate has no server-side search parameter
• Automatic 429 retries honoring Retry-After
• Server-side company, location, computer, status, approval-state, action, entity-type, and date filters
• n8n item pairing and Continue On Fail support
• Actionable errors for authentication, permissions, missing records, and rate limits

Installation

Follow the n8n community-node installation guide.

Community Nodes

1. In n8n, go to Settings → Community Nodes.
2. Select Install.
3. Enter @joshuanode/n8n-nodes-autoelevate.
4. Accept the community-node risk notice and install the package.

Manual Installation

In a self-hosted n8n installation:

npm install @joshuanode/n8n-nodes-autoelevate

Restart n8n after installation if the node does not appear immediately.

Prerequisites

• An AutoElevate partner account with access to the Partner API
• An AutoElevate service user
• An API key with the permissions required by your workflows
• n8n 1.0 or newer
• Node.js 18.17.0 or newer for self-hosted installations

Credentials

In the AutoElevate admin portal, open a service user and create an API key. Grant only the permissions needed by your workflows.

API Token (recommended)

1. Create a key using the API Token (AE-BEARER) scheme.
2. Copy the aeb_ token when it is displayed.
3. In n8n, create an AutoElevate Partner API credential.
4. Select API Token (AE-BEARER) and paste the token.

HMAC

1. Create a key using the HMAC (AE-HMAC-SHA256) scheme.
2. Copy both the aeh_ wire token and the separate HMAC signing key.
3. In n8n, select HMAC (AE-HMAC-SHA256) and enter both values.

AutoElevate displays secrets only once. Store them securely and revoke any key that may have been exposed.

Resources and Operations

| Resource | Operations | Filters | | --- | --- | --- | | Audit Log | Get Many | Entity type, action, start, end | | Company | Get, Get Many | — | | Computer | Get, Get Many | Company, location | | Elevated Session | Get, Get Many | Company, computer, status | | Elevation Event | Get Many | Company, start, end | | Elevation Request | Approve, Deny, Get, Get Many | Company, approval state, start, end | | Elevation Rule | Get Many | Company | | Location | Get, Get Many | Company | | Usage | Get | — |

Example Workflows

Notify on Pending Elevation Requests

Resource: Elevation Request
Operation: Get Many
Approval State: Pending
Return All: true

Run this on a schedule, then route each request to Slack, Teams, email, or your PSA.

Approve a Request

Resource: Elevation Request
Operation: Approve
Elevation Request: Select from list or provide a UUID
Elevation Type: Admin
Create Rule: false

Enable Create Rule only when you intentionally want future matching requests handled automatically.

Inventory Computers for a Company

Resource: Computer
Operation: Get Many
Company: Select from list
Return All: true

API Limits

During beta, AutoElevate documents a default limit of 100 requests per hour for each MSP, HTTP method, and route path. Get Many uses pages of up to 200 records, so large result sets consume multiple requests. A 429 response includes a Retry-After value.

Error Handling and Troubleshooting

| Error | Meaning | Recommended action | | --- | --- | --- | | 400 Bad Request | Invalid parameters or a changed beta API contract | Review the node fields and compare the request with the current AutoElevate documentation | | 401 Unauthorized | Invalid, expired, or incorrectly configured API credentials | Confirm the selected authentication scheme and rotate the API key if needed | | 403 Forbidden | The service user or API key lacks permission for the operation | Add the required API permission in AutoElevate or use a properly scoped service user | | 404 Not Found | The record does not exist or is outside the partner account | Verify the selected company, computer, location, session, request, or rule | | 429 Too Many Requests | The route-specific API limit has been reached | The node retries twice using Retry-After; reduce polling frequency if the limit persists |

AutoElevate error messages and error codes are preserved in n8n when the API returns them. For example, a missing audit-log permission should surface AutoElevate's original authorization message rather than a generic request failure.

Node Does Not Appear

• Restart n8n after installing the package.
• Confirm @joshuanode/n8n-nodes-autoelevate appears under Settings → Community Nodes.
• For Docker deployments, confirm the package is installed in the same environment and user context that runs n8n.

Picker Search Is Slow

The Partner API does not currently expose server-side search parameters for picker resources. When search text is entered, the node scans all available API pages and filters the results locally. Large partner accounts may therefore consume several requests while searching.

Compatibility

• n8n: 1.0 or newer
• Node.js: 18.17.0 or newer
• AutoElevate Partner API: v1 beta

Development

npm install
npm run build
npm run lint
npm test
npm pack --dry-run

For local n8n testing, use npm link or install the generated package tarball in your test instance.

Workflow type warning: Loading the node directly from n8n's custom-node directory registers it as CUSTOM.autoElevate. Installing the published package registers it as @joshuanode/n8n-nodes-autoelevate.autoElevate. Workflows created with the custom-directory build must have that node type migrated before they can use the npm-installed package. For durable test workflows, install the generated package tarball instead of loading the source directory as a custom node.

Security

• Use a dedicated AutoElevate service user.
• Prefer short-lived API keys for testing.
• Scope keys to least privilege.
• Never commit API tokens or HMAC signing keys.
• Treat elevation approval and rule creation as privileged actions.

Please report security issues privately rather than opening a public issue containing credentials or customer data.

Contributing

Bug reports, feature requests, and pull requests are welcome in the GitHub repository.

Support

• For node bugs or feature requests, open a GitHub issue.
• For AutoElevate account access, API permissions, or platform behavior, contact AutoElevate support.
• Do not include API keys, HMAC signing keys, customer names, computer names, or other sensitive tenant data in public issues.

Version History

0.1.0

• Initial public release
• Complete coverage of the currently published AutoElevate Partner API v1 beta endpoints
• Bearer and HMAC authentication
• Searchable resource selectors, pagination, filtering, rate-limit retries, and preserved API errors

Resources

• AutoElevate Partner API documentation
• n8n Community Nodes documentation
• n8n Community Nodes installation guide

Author

Joshua Smith

License

MIT

Disclaimer

This is an independent community integration and is not an official AutoElevate product. AutoElevate is a trademark of its respective owner. Use of the AutoElevate Partner API remains subject to AutoElevate's terms, permissions, rate limits, and beta API conditions.