Connect Auvik to Conduit

This walkthrough connects Auvik (network monitoring) to Conduit. Auvik authenticates with your account email (username) plus an API key generated from your Auvik user profile, and an optional Region that selects the Auvik cluster your tenant lives on.

Menu labels can change

The Auvik steps below reflect the user-profile flow at time of writing; menu labels can shift between releases. If a label differs, see Auvik’s user-profile guide and the Auvik APIs section.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• An Auvik login. The API authenticates as that user (email + API key), so its access matches what that user can see in Auvik.
• To know your region — the cluster segment in your Auvik URL. When you’re signed in, the address looks like <yourdomain>.<region>.my.auvik.com (for example us1).

Step 1 — Generate an API key in Auvik

1. Sign in to Auvik.
2. Open your user profile and generate an API key (see Auvik’s guide). Expected: an API key value.
3. Copy the key, and note the email address of the Auvik user it belongs to — the key only works together with that username.

Caution

Copy the key now and store it somewhere safe. Don’t paste it into chat, email, or a shared document — the next step moves it directly into Conduit, which encrypts it at rest. If you accidentally expose the key, regenerate it from your Auvik user profile first; the exposed key becomes useless immediately.

Step 2 — Connect Auvik in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find Auvik in the catalog (under Network) and click Connect. Expected: a credential form with three fields.
3. Fill the fields:
   • Auvik Username (email) (required) — the email of the Auvik user the key belongs to.
   • API Key (required) — from Step 1.
   • Region (optional) — a dropdown with us1, us2, us3, us4, us5, us6, eu1, eu2, au1, ca1, and lnx. Pick the cluster from your Auvik URL (<yourdomain>.<region>.my.auvik.com). Leave it blank to use us1, the default.
4. Click Connect. Expected: Conduit validates the username + key immediately against the selected region’s Auvik API and shows a green Connected status. A bad pair is rejected here, not on the first tool call.

The credential is stored at the organization scope, so every technician in your org shares this Auvik connection. (For per-technician keys, connect at the personal scope instead — see Vendor connections.)

Verify it worked

Connect an MCP client to Conduit — Claude Desktop, Claude Code, Cursor, or any MCP-compatible client (see Connecting an AI client) — and ask it to run a read-only Auvik tool, such as listing tenants or devices. You should get real data back, and the call appears in your audit log with the correct user, vendor (auvik), and a successful status.

Troubleshooting

Symptom	Likely cause
Connect fails with “Invalid Auvik username or API key.”	The email doesn’t match the user the key was generated for, the key was regenerated, or it was copied incompletely. Regenerate the key from the user profile and reconnect with the matching email.
Connect fails with “Auvik returned HTTP …. Check your region selection.”	The credentials reached an Auvik cluster that isn’t yours. Check the region segment in your Auvik URL (<yourdomain>.<region>.my.auvik.com) and reconnect with the matching region.
Tool calls return 403 “no credentials for vendor”	Auvik isn’t connected at a scope this user can resolve. Connect it at the organization scope, or confirm the user’s team has a key.
Tool calls succeed but some data is missing	The API sees what the Auvik user sees. Check that user’s permissions and tenant access in Auvik.
Need to rotate the key	Regenerate the API key from the Auvik user profile, then update the credential at /org/catalog. The old key stops working when you regenerate.

Related

• Vendor connections — credential scopes, rotation, and the full vendor catalog.
• Security — how Conduit encrypts and resolves the credential you just stored.