Connect IT Glue to Conduit

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

Menu labels can change

The IT Glue-portal steps below reflect IT Glue’s API-key flow at time of writing; menu labels can shift between IT Glue releases. If a label differs, look for the nearest equivalent in the same area of the portal.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• An IT Glue account with permission to create API keys (an IT Glue Manager or Administrator). If you don’t have it, ask your IT Glue administrator to do Step 1 and hand you the key.

Step 1 — Create an API key in IT Glue

1. Sign in to IT Glue as a Manager or Administrator. Expected: the IT Glue dashboard.
2. Open the account menu (top right) and click Account → Settings. Expected: the Account settings page.
3. In the settings navigation, click API Keys. Expected: the list of existing API keys (empty if you’ve never made one).
4. Click + New API Key (or Generate API Key). Expected: a new-key form.
5. Give the key a recognizable name — for example, Conduit — so you can identify and revoke it later. Leave the default access unless your policy requires read-only.
6. Click Generate (or Save). Expected: the key value is displayed.

Caution

Copy the key now and store it somewhere safe. IT Glue shows the full key value at creation; treat it like a password — anyone with it can read your IT Glue data through the API.

Step 2 — Connect IT Glue in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find IT Glue in the catalog and click Connect. Expected: an API Key field and a Region field.
3. Paste the IT Glue API key from Step 1 into the API Key field.
4. Choose Region (US, EU, or AU). Leave it blank for the US cloud API. Conduit calls api.itglue.com, api.eu.itglue.com, or api.au.itglue.com from that choice. Do not paste app.itglue.com or your IT Glue website address — those hosts redirect and are not the API.
5. Leave Self-hosted unchecked unless IT Glue runs on your own server. That checkbox is the only place an API host is entered.
6. Click Connect. Expected: Conduit validates the key against IT Glue 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 IT Glue 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 IT Glue tool, such as listing your IT Glue organizations. You should get real data back, and the call appears in your audit log with a 200 status.

Troubleshooting

Symptom	Likely cause
Connect fails immediately in Conduit	The key is wrong, was revoked, or the account lacks API access. Re-check Step 1 and paste the key again. If the error says the address is a website, clear Self-hosted and pick Region instead of pasting app.itglue.com.
Tool calls return 403 “no credentials for vendor”	IT Glue 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 fail with an upstream auth error after working	The IT Glue key was rotated or revoked on the IT Glue side. Re-connect at /org/catalog with a fresh key.
IT Glue tools don’t appear for a user	A tool allowlist may restrict them for that role — see tool allowlists.
Firewall/IP-allowlisting note	IT Glue often enforces an IP allowlist on the API key itself. Conduit’s outbound calls all leave from a single static IP, 20.242.40.128 — allowlist this IP on the key (Account → Settings → API Keys) if your tenant restricts which addresses may call the API. See Static egress IP. A tunnel is only for a self-hosted IT Glue server on your own network. Cloud IT Glue uses the static IP above.

Related

• Static egress IP — the address to allowlist when IT Glue restricts API keys by source IP.
• Vendor connections — credential scopes, rotation, and the full vendor catalog.
• Security — how Conduit encrypts and resolves the credential you just stored.