Connect SalesBuildr to Conduit

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

Menu labels can change

The SalesBuildr steps below reflect the current portal flow; menu labels can shift between releases. If a label differs, see SalesBuildr’s public 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 SalesBuildr login with permission to create API keys.

Step 1 — Create an API key in SalesBuildr

1. Sign in to the SalesBuildr portal.
2. Create an API key following SalesBuildr’s public API article. Expected: an API key value, shown at creation.
3. Copy the key immediately.

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 and generate a new one in SalesBuildr first; the exposed key becomes useless immediately.

Step 2 — Connect SalesBuildr in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find SalesBuildr in the catalog (under Sales) and click Connect. Expected: a credential form with a single API Key field.
3. Paste the SalesBuildr API key from Step 1 into the API Key field (required).
4. Click Connect. Expected: Conduit validates the key against SalesBuildr 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 SalesBuildr connection. (For per-technician keys, 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 SalesBuildr tool, such as listing companies. Real data should come back, and the call appears in your audit log with vendor salesbuildr.

Troubleshooting

Symptom	Likely cause
Connect fails with “Invalid SalesBuildr API key.”	The key was mistyped, revoked, or copied incompletely. Generate a fresh key in SalesBuildr and re-connect.
Connect fails with “SalesBuildr returned HTTP …”	SalesBuildr responded with an unexpected status — often transient; retry, then check SalesBuildr’s API article for known limits.
Tool calls return 403 “no credentials for vendor”	SalesBuildr 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.
Need to rotate the key	Generate a new key in SalesBuildr, 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.