Connect Ironscales to Conduit

This walkthrough connects Ironscales (email security, in Conduit’s security category) to Conduit. Ironscales needs two values: an API key generated in the Ironscales partner portal, and the Company ID of the Ironscales tenant you want the AI to operate in.

Menu labels can change

The Ironscales steps below reflect current portal flows; labels can shift between releases. If a label differs, see the Ironscales API docs or this integration reference for how the key and company ID are obtained.

Before you start

You need:

• A Conduit role that can manage connections — owner or admin on your organization.
• An Ironscales login with access to the partner portal, where API keys are generated.
• To know which company (tenant) you want the AI to work in — tool calls are scoped to one Company ID.

Step 1 — Generate an API key in the Ironscales partner portal

1. Sign in to Ironscales.
2. Generate an API key under Settings > Account Settings > General & Security (see the integration reference). Expected: an API key value.
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 Ironscales and generate a new one; the exposed key becomes useless immediately.

Step 2 — Find your Company ID

Locate the Company ID — the Ironscales tenant/company identifier — for the company you want the AI to operate in. This value is required: it scopes every tool call, and Conduit’s connect-time validation checks the key against this specific company.

Step 3 — Connect Ironscales in Conduit

1. In Conduit, go to Connections (/org/catalog). Expected: the vendor catalog.
2. Find Ironscales in the catalog (under Security) and click Connect. Expected: a credential form with two fields.
3. Fill the fields:
   • API Key (required) — from Step 1 (the form hints: “Generate in Ironscales partner portal”).
   • Company ID (required) — from Step 2 (the form hints: “Ironscales tenant/company identifier”).
4. Click Connect. Expected: Conduit validates immediately by reading the incident list for that company with your key, then shows a green Connected status. A bad key or a company ID the key can’t access 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 Ironscales 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 Ironscales tool. You should get real data back, and the call appears in your audit log with the correct user, vendor (ironscales), and a successful status.

Troubleshooting

Symptom	Likely cause
Connect fails with “Invalid Ironscales API key or company ID.”	Either value can be at fault: the key is wrong/revoked, or the key is valid but doesn’t have access to the Company ID you entered. Verify both, and confirm the key was generated for the right tenant.
Connect fails with “Ironscales returned HTTP …”	Ironscales answered with an unexpected status — a malformed Company ID or a transient service issue. Double-check the Company ID value and retry.
Tool calls return 403 “no credentials for vendor”	Ironscales 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 show the wrong tenant’s data	The stored Company ID points at a different company than intended. Update the credential at /org/catalog with the correct Company ID.
Need to rotate the key	Generate a new API key in the Ironscales partner 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.