Before connecting
Windsor connects Work Mode to supported advertising and analytics data through its official MCP service. In TradeVulcan, this path requires Lead Forge access and your normal Work and app permissions. Managing the connection also needs the appropriate settings permission.
Have your own Windsor account ready and ensure the desired source accounts are connected there. A Google Ads or Meta login elsewhere does not establish that Windsor can access the same account. Do not put an API key, OAuth code or provider password into the conversation.
1. Authorize Windsor
- Open Work Mode → Connections → Windsor.ai in the correct workspace.
- Choose Connect Windsor or the reconnect control for the intended installation.
- Complete the provider authorization in the opened window. If it did not open, use Open Windsor authorization.
- Return to TradeVulcan and reload the connection state. Authorization alone is not the final account-selection step.
2. Save a precise account selection
Under Accounts available to this workspace, inspect the connector, account label and provider account identifier. Select only the accounts relevant to this workspace. Two similarly named accounts can belong to different businesses or sources.
If no accounts are returned, add or repair the source connection in Windsor, then use Refresh tools. Do not type an arbitrary account ID into a prompt to bypass the returned selection.
Choose Save accounts and permissions. TradeVulcan verifies the selected scope before marking it connected. If another tab changed the selection, reload the saved settings and reconcile your edits instead of overwriting them blindly.
3. Keep external actions off for an initial report
For reporting, leave Allow approved external actions off. Reading campaign data does not require authority to change advertising. Every eventual provider write needs a separate exact action approval even when the connection permits approved actions.
Additional named Windsor connections currently support reads where their card says external changes are unavailable. Do not assume that enabling writes on one installation enables them on another. Use distinct labels such as Main Google Ads and Regional reporting so the account boundary stays visible.
4. Verify with a small read
Using my Windsor connection named Main advertising, list the selected source accounts. Then read campaign names and spend for the Google Ads account I select, for the previous seven complete days. Do not change anything.
Check the returned account, currency and dates. If Work asks you to choose among accounts, select explicitly. A successful tool refresh verifies metadata and scope; it is not yet evidence that every metric or external action is available.
After reconnecting or refreshing
Refreshing can move the installation back to scope review and turn writes off. Reconfirm accounts and permissions before continuing. A changed provider tool definition also requires review rather than automatic acceptance.
If authorization succeeds but reporting fails, use the Windsor troubleshooting guide with the connection label, source connector, date range and non-sensitive error. Do not repeatedly create replacement connections or publish credentials in support chat.