Windsor.ai “Account Is Not Available” Error: Troubleshooting Guide

Seeing “Account [ID] is not available” even though the source shows up fine in your Data tab? In most cases, this is an access or API key mismatch, not a connector outage: your request may be using an API key that doesn’t have that account in its list, even if another key in your organization does.

Windsor checks accounts against the API key making the request, not against every key your organization owns. Use the wrong key, and you get no access: this exact error, plus a list of the accounts that key can see.

One confirmed case: a Meta account was authorized and visible under the customer’s main Windsor login. But the request, made through an AI assistant via MCP, used an API key from a different, abandoned account. That key never had the source connected. Same error.

This shows up across Facebook, LinkedIn Organic, RTB House, and more, and it isn’t limited to MCP requests: the same key mismatch can happen through a Google Sheets add-on, Excel, Power BI, a script, or a direct API call. It’s not a connector bug, it’s a key mismatch. Stop guessing which key is stale: check the Data tab under the Windsor login that key belongs to. That’s the only place that matters.

Note that a key mismatch isn’t the only thing that can produce this message. A disconnected source, an expired token, missing permissions, or a plan/account limit can look similar. The causes and fix below cover the API key mismatch specifically, since it’s the case we see most often.

• Wrong or stale API key. If you have more than one Windsor API key (an old key saved in a script, a second account created by accident, a key copied before rotating it), the account you’re targeting may simply not exist under the key you’re currently using.
• Account connected under a different Windsor login. Windsor accounts and their connected data sources belong to whichever Windsor login (and its API key) added them. If a teammate connected the source under their own Windsor login, or through a separate authorization flow, your key won’t see it unless that account is shared with or added to yours.
• Account removed and reconnected. If a source was disconnected and reconnected, its underlying account ID may have changed even though the account name looks the same. Check the current account ID in Windsor and update any saved request that still references the old one.

Before changing anything, check:

• The exact API key your request is using.
• The Windsor login/email that key belongs to.
• Whether the target source appears in the Data tab for that same login.
• Whether the account ID in your request matches the current account ID shown in Windsor.

This is usually enough to spot the mismatch without touching any connections yet.

1. Open Windsor’s web dashboard and check the Data tab under the same login whose API key you’re using in the request, not just any login on your team. Confirm the target account is listed there.
2. If it isn’t listed under that login, either reconnect the account under that login, or switch your request to use the API key that belongs to the login where the account is actually configured.
3. Check the API key wherever it’s configured: an MCP connector (Claude, ChatGPT, or similar), a Google Sheets add-on, Excel, Power BI, a script, or a direct API call. A common cause is an old API key saved in one of these places that never got updated after a key rotation.
4. If the account was recently reconnected, re-run the request. The “configured accounts” list in the error message reflects what the key currently sees. A fresh reconnect usually resolves the mismatch immediately.

Confirmed the account is under the right login and still stuck? Message support with the account ID and your API key’s account name. Don’t send the full API key over chat or email; the account ID and account name are enough, and you can add the last 4 to 6 characters of the key if you want extra reference. We’ll find the mismatch. No back-and-forth needed.