Connect Sherweb to Conduit

This walkthrough connects Sherweb (cloud marketplace / CSP) to Conduit. Sherweb needs three values: an OAuth Client ID and Client Secret, plus a Subscription Key that authorizes access to Sherweb’s API products. All three come from Sherweb’s developer portal.

Menu labels can change

The Sherweb steps below reflect the developer-portal flow at time of writing; labels can shift between releases. If a label differs, see Sherweb’s getting-started guide.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• A Sherweb partner account with access to the developer portal, where API credentials and subscription keys are issued.

Step 1 — Create API credentials in Sherweb

1. Sign in to the Sherweb developer portal.
2. Follow Sherweb’s getting-started guide to create API credentials and subscribe to the API product you need. Expected: a Client ID, a Client Secret, and a Subscription Key.
3. Copy all three values. Secrets are shown at creation — if you lose one, regenerate it.

Caution

Copy the Client Secret and Subscription Key now and store them somewhere safe. Don’t paste them into chat, email, or a shared document — the next step moves them directly into Conduit, which encrypts them at rest. If you accidentally expose a value, regenerate it in the Sherweb developer portal first; the exposed value becomes useless immediately.

Step 2 — Connect Sherweb in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find Sherweb in the catalog (under Marketplace) and click Connect. Expected: a credential form with three fields.
3. Fill the fields:
   • Client ID (required) — from Step 1.
   • Client Secret (required) — from Step 1.
   • Subscription Key (required) — from Step 1.
4. Click Connect. Expected: Conduit validates immediately by requesting an OAuth token from Sherweb with your Client ID and Client Secret, then shows a green Connected status.

One nuance worth knowing: connect-time validation primarily proves the Client ID + Client Secret pair can mint a token. Sherweb enforces the Subscription Key when actual API calls are made — so a mistyped subscription key can pass Connect and only surface as failures on the first tool call. If tools fail right after a successful connect, re-check the subscription key.

The credential is stored at the organization scope, so every technician in your org shares this Sherweb connection. (For per-technician credentials, 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 Sherweb tool. You should get real data back, and the call appears in your audit log with the correct user, vendor (sherweb), and a successful status.

Troubleshooting

Symptom	Likely cause
Connect fails with “Invalid Sherweb client credentials or subscription key.”	The Client ID / Secret pair is wrong or revoked (or the subscription key was rejected outright). Re-copy all three values from the developer portal and reconnect.
Connect fails with “Sherweb returned HTTP …”	Sherweb’s token endpoint answered with an unexpected status — often a transient service issue. Wait a moment and retry.
Connect fails with “Sherweb request failed: …”	Conduit couldn’t reach the Sherweb API at all (network error or timeout). Retry; if it persists, check Sherweb’s service status.
Connect succeeds but tool calls fail	The Subscription Key is checked when API calls are made, not at connect time. Verify the key in the developer portal (and that it’s subscribed to the right API product), then update the credential at /org/catalog.
Tool calls return 403 “no credentials for vendor”	Sherweb isn’t connected at a scope this user can resolve. Connect it at the organization scope, or confirm the user’s team has a credential.
Need to rotate a value	Regenerate the secret or subscription key in the Sherweb developer portal, 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.