Connect Crewhu to Conduit

This walkthrough connects Crewhu (productivity — CSAT, gamification, and employee recognition) to Conduit. You create an API token in Crewhu, then add it as an organization connection in Conduit. Once connected, any MCP client your organization uses can call Crewhu tools through Conduit’s gateway.

Menu labels can change

The Crewhu steps below reflect the current portal flow; menu labels can shift between releases. If a label differs, see Crewhu’s Open API article — it is the authority for this flow.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• A Crewhu administrator login (to obtain an API token).

Step 1 — Create an API token in Crewhu

1. Sign in to Crewhu as an administrator.
2. Obtain an API token following Crewhu’s Open API article. Expected: an API token value.
3. Copy the token.

Caution

Copy the token 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 token, regenerate it in Crewhu first; the exposed token becomes useless immediately.

Step 2 — Connect Crewhu in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find Crewhu in the catalog (under Productivity) and click Connect. Expected: a credential form with a single API Token field.
3. Paste the Crewhu API token from Step 1 into the API Token field (required).
4. Click Connect. Expected: Conduit validates the token against Crewhu immediately and shows a green Connected status. A bad token 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 Crewhu connection. (For per-technician tokens, connect at the personal scope instead — see Vendor connections.)

Verify it worked

Connect an MCP client to Conduit (see Connecting an AI client) and ask it to run a read-only Crewhu tool, such as listing users. Real data should come back, and the call appears in your audit log with vendor crewhu.

Troubleshooting

Symptom	Likely cause
Connect fails with “Invalid Crewhu API token.”	The token was mistyped, revoked, or copied incompletely. Obtain a fresh token in Crewhu and re-connect.
Connect fails with “Crewhu returned HTTP …”	Crewhu responded with an unexpected status — often transient; retry, then check Crewhu’s help center for service notices.
Connect fails with “Crewhu validation failed: …”	Network-level failure reaching Crewhu’s API — usually temporary. Retry; if it persists, verify outbound connectivity to api.crewhu.com.
Tool calls return 403 “no credentials for vendor”	Crewhu isn’t connected at a scope this user can resolve. Connect it at the organization scope, or confirm the user’s team has a token.
Need to rotate the token	Regenerate it in Crewhu, 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.