Connect SaaS Alerts to Conduit

This walkthrough connects SaaS Alerts (SaaS security monitoring) to Conduit. You create an API key in SaaS Alerts, then add it as an organization connection in Conduit. Once connected, any MCP client your organization uses can call SaaS Alerts tools through Conduit’s gateway.

Menu labels can change

The SaaS Alerts steps below reflect the Kaseya/SaaS Alerts flow at time of writing; menu labels can shift between releases. If a label differs, follow SaaS Alerts’ guide to using the API.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• A SaaS Alerts login with access to the account’s API settings.

Step 1 — Create an API key in SaaS Alerts

1. Sign in to your SaaS Alerts portal. Expected: the SaaS Alerts dashboard.
2. Create or locate your API key following SaaS Alerts’ API guide. Expected: an API key value you can copy.
3. Copy the key. (The SaaS Alerts API reference describes the endpoints the key unlocks.)

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 in SaaS Alerts first; the exposed key becomes useless immediately.

Step 2 — Connect SaaS Alerts in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find SaaS Alerts in the catalog (under Security) and click Connect. Expected: a credential form with a single API Key field.
3. Paste the SaaS Alerts API key from Step 1 into the API Key field.
4. Click Connect. Expected: Conduit validates the key against SaaS Alerts immediately and shows a green Connected status. A bad key 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 SaaS Alerts 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 SaaS Alerts tool, such as pulling a recent alert report. You should get real data back, and the call appears in your audit log with the correct user, vendor (saas-alerts), and a successful status.

Troubleshooting

Symptom	Likely cause
Connect fails with “Invalid SaaS Alerts API key.”	The key is wrong, was regenerated in SaaS Alerts after you copied it, or was copied incompletely. Generate a fresh key and re-connect.
Connect fails with “SaaS Alerts returned HTTP <status>.”	SaaS Alerts answered with a non-auth error — usually a transient vendor-side issue. Wait and retry; if it persists, check SaaS Alerts’ status.
Tool calls return 403 “no credentials for vendor”	SaaS Alerts 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.
Vendor health shows yellow/degraded	Conduit’s health check sees SaaS Alerts responding slowly. Usually a transient vendor-side load spike — recovers automatically.
Need to rotate the key	Generate a new API key in SaaS Alerts, then update the credential at /org/catalog. The old key stops working once revoked in SaaS Alerts.

Related

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