Connect TimeZest to Conduit

This walkthrough connects TimeZest (productivity — appointment scheduling for MSPs) to Conduit. TimeZest keeps it simple: a single API token is all Conduit needs. You create the token in TimeZest, then add it as an organization connection in Conduit.

Menu labels can change

The TimeZest steps below reflect the current flow; menu labels can shift between releases. If a label differs, see TimeZest’s authentication docs — they are the authority for this flow.

Before you start

You need:

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

Step 1 — Create an API token in TimeZest

1. Sign in to TimeZest as an administrator.
2. Create an API token following TimeZest’s authentication docs. Expected: a token value, shown at creation.
3. Copy the token immediately.

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

Step 2 — Connect TimeZest in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find TimeZest in the catalog (under Productivity) and click Connect. Expected: a credential form with a single API Token field.
3. Paste the TimeZest API token from Step 1 into the API Token field (required).
4. Click Connect. Expected: Conduit validates the token against TimeZest 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 TimeZest 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 TimeZest tool, such as listing agents. Real data should come back, and the call appears in your audit log with vendor timezest.

Troubleshooting

Symptom	Likely cause
Connect fails with “Invalid TimeZest API token.”	The token was mistyped, revoked, or copied incompletely. Create a fresh token in TimeZest and re-connect.
Connect fails with “TimeZest returned HTTP …”	TimeZest responded with an unexpected status — often transient; retry, then check TimeZest’s developer docs for service notices.
Connect fails with “TimeZest validation failed: …”	Network-level failure reaching TimeZest’s API — usually temporary. Retry; if it persists, verify outbound connectivity to api.timezest.com.
Tool calls return 403 “no credentials for vendor”	TimeZest 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	Create a new token in TimeZest, 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.