Incident fires → PSA ticket pre-populated
When Huntress logs a critical or high-severity incident, the Vectis alert card surfaces the incident type, affected hosts, and severity, and lets you open a PSA ticket pre-filled with all of it.
Endpoint Security integration
See Huntress MDR agent health, open incident reports, and escalation status next to every ticket, backup job, and RMM alert — without opening the partner portal.
What Vectis syncs
Vectis syncs every Huntress agent across your customer organizations — OS, agent version, and last-active time. Open incident reports are pulled with severity, type, and affected hosts; escalation cases sync alongside. Agent status feeds the customer health strip; Unresponsive agents raise protection-gap alerts.
What you can do
Resolve a Huntress incident report from the Vectis alert card without opening the partner portal. Approve a Huntress-proposed remediation via a rules engine action — useful for automating the approval flow when the incident type and severity meet your criteria. Vectis does not support agent isolation or tag management — those are not available via the Huntress REST API.
Honest about the limits
Huntress uses a single partner-scoped API credential (key + secret) that covers all your customer organizations. A single Vectis connection syncs every customer simultaneously. The API rate limit is 60 requests per minute; Vectis backs off automatically on HTTP 429. Customer matching uses organization names — exact match first, partial match fallback.
How it correlates
Huntress on the customer account hub alongside every other system you run — not a standalone dashboard. A few of the most common shapes this takes:
When Huntress logs a critical or high-severity incident, the Vectis alert card surfaces the incident type, affected hosts, and severity, and lets you open a PSA ticket pre-filled with all of it.
Unresponsive Huntress agents appear on the same asset row as your RMM patch count and last check-in — one view of full endpoint posture.
When Huntress proposes a remediation and the incident severity is critical, a Vectis rule can automatically approve it — or route it to a PSA ticket for manual review first.
Setup snapshot
Log in to the Huntress Partner Portal at partners.huntress.io. Navigate to Account Settings → API Credentials and click Generate API Key. Copy the API secret immediately — it is shown only once. In Vectis Admin → Integrations → Huntress → Add connection, enter the API key and API secret. Click Test connection — you should see the number of organizations on your account. Save and run a first sync. Vectis maps Huntress organizations to Vectis customers by name; any organization without a matching customer is skipped until the customer is created.
# In the Vectis hub, add the connector:
category Endpoint Security
vendor Huntress
status Read + WriteOther Endpoint Security integrations
Pricing
Huntress is available on every Vectis tier — $299/mo and up. See pricing
Also reachable over MCP — bring your own client → /mcp