Connect Domotz to Conduit

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

Menu labels can change

The Domotz-portal steps below stay deliberately generic; menu labels can shift between Domotz releases. Follow Domotz’s API guide as the authority for creating an API key.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• A Domotz account that can create API keys.
• To know which region hosts your Domotz account — US (us-east-1) or EU (eu-central-1). Keys authenticate against their own region’s API endpoint.

Step 1 — Create an API key in Domotz

1. Sign in to Domotz.
2. Create an API key following Domotz’s API guide. Expected: an API key value.
3. Copy the key.

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, revoke it in Domotz and create a new one; the exposed key becomes useless immediately.

Step 2 — Connect Domotz in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find Domotz in the catalog (under Network) and click Connect. Expected: a credential form with two fields.
3. Fill the fields:
   • API Key (required) — from Step 1.
   • Region (optional) — pick us-east-1 (api-us-east-1-cell-1.domotz.com) or eu-central-1 (api-eu-central-1-cell-1.domotz.com), matching where your Domotz account is hosted. If you leave it blank, Conduit uses the US endpoint.
4. Click Connect. Expected: Conduit validates the key against your region’s API immediately and shows a green Connected status. A bad key or wrong region 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 Domotz 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 Domotz tool, such as checking connection status or listing monitored agents. You should get real data back, and the call appears in your audit log with the correct user, vendor (domotz), and a successful status.

Troubleshooting

Symptom	Likely cause
Connect fails with “Invalid API key.”	The key is wrong, revoked, or was pasted incompletely. Create a fresh key in Domotz and reconnect.
Connect fails with “Domotz returned HTTP <status>. Check your region selection.”	The key may be valid but pointed at the wrong region — a US key sent to the EU endpoint (or vice versa) fails. Set the Region field to match where your Domotz account is hosted.
Tool calls return 403 “no credentials for vendor”	Domotz 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	Domotz API keys carry the visibility of the account they belong to. Confirm the account can see the agents/sites you expect in the Domotz portal.
Need to rotate the key	Create a new API key in Domotz, then update the credential at /org/catalog.

Related

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