Connect Syncro to Conduit

This walkthrough connects Syncro (RMM) to Conduit. You create an API token in Syncro, then add it — optionally with your account subdomain — as an organization connection in Conduit. Once connected, any MCP client your organization uses can call Syncro tools through Conduit’s gateway.

Menu labels can change

The Syncro-portal steps below stay deliberately generic; menu labels can shift between Syncro releases. Follow Syncro’s API tokens guide as the authority for creating a token.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• A Syncro account that can create API tokens. The token carries the permissions it was created with, so scope it to cover whatever you want the AI to do.
• Your Syncro subdomain — the first part of the address you sign in at (https://<subdomain>.syncromsp.com).

Step 1 — Create an API token in Syncro

1. Sign in to Syncro.
2. Create an API token following Syncro’s guide. Expected: an API key value, shown at creation.
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 Syncro and create a new one; the exposed key becomes useless immediately.

Step 2 — Connect Syncro in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find Syncro in the catalog (under RMM) and click Connect. Expected: a credential form with two fields.
3. Fill the fields:
   • API Key (required) — from Step 1.
   • Subdomain (optional) — just the first label of your Syncro address (e.g. yourcompany for yourcompany.syncromsp.com), not a full URL. If you leave it blank, Conduit uses app.syncromsp.com.
4. Click Connect. Expected: Conduit validates the key against your Syncro instance immediately and shows a green Connected status. A bad key or subdomain 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 Syncro 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 Syncro tool, such as listing customers or recent tickets. You should get real data back, and the call appears in your audit log with the correct user, vendor (syncro), and a successful status.

Troubleshooting

Symptom	Likely cause
Connect fails with “Invalid Syncro subdomain.”	The subdomain must be a single DNS label — letters, digits, and hyphens only. Enter just yourcompany, not a full URL, a path, or anything containing /, ., or @.
Connect fails with “Invalid Syncro API key or subdomain.”	The key is wrong or revoked, or the subdomain doesn’t match the account the key was created in. Verify both against your Syncro sign-in address.
Connect fails with “Syncro returned HTTP <status>.”	Syncro returned an unexpected error — often transient, or the subdomain points at an instance that exists but isn’t yours. Retry and double-check the subdomain.
Tool calls return 403 “no credentials for vendor”	Syncro 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 specific actions are denied	The API token was created with limited permissions. Create a token with the scopes the AI needs, then update the connection.
Need to rotate the key	Create a new API token in Syncro, 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.
• Syncro API documentation — full API reference.