Skip to main content
Open the platform’s card in Workspace Settings → Integrations, click View, then + Add account and authorize the other login. Both accounts stay connected in the same workspace. See Connect multiple accounts.
The primary account. Click the star next to an account to make it the primary. To use a different one, just ask Claude — for example, “show my other Google Ads account” — and it will use that account for the request.
In the platform’s dialog, click the star next to an account. A filled star marks the primary; an empty star means it isn’t primary yet. Setting a new primary only changes Claude’s default — nothing gets disconnected.
Connect the accounts you need on each platform and set a primary. If you manage a large number and want help structuring workspaces, email support@get-ryze.ai.
Click Reconnect on the platform card in Workspace Settings → Integrations, then start a new chat in Claude.
Connect whichever platforms you want Claude to read. Nothing else is required — just start a new chat after connecting.
Go to Workspace Settings → Integrations → Shopify, enter your .myshopify.com domain (not your custom domain) and approve the Shopify prompt — no app creation or API keys. Use your own custom app only if you need extra scopes such as theme files or customer records. See Connect Shopify.
No. Connect the one Google login that has manager access and Ryze reaches the whole hierarchy. In a new chat ask “list all Google Ads accounts accessible to my login, including my MCC hierarchy”, then name any client by name or customer ID. Cancelled or never-enabled accounts in the hierarchy may show a CUSTOMER_NOT_ENABLED notice — that’s normal and doesn’t block the live ones.
Ryze sees exactly what the connected login can reach. If an account is missing, reconnect from the Integrations page and tick every permission checkbox on Google’s or Meta’s consent screen, signed in with the login that actually has access — or add that login as a second account. The card shows only the login email; the accounts themselves are discovered when the agent queries them, so ask in a new chat to list them.
Both are settings on Meta’s side. For blocked changes, give the connected user Manage ad account on that ad account (Business settings → Ad accounts → People), then reconnect. For “Verify your account” (error 31), complete the verification prompt in Meta Business Manager — creating any ad manually there usually triggers it; reconnecting in Ryze doesn’t clear it.
The account is connected, but a property hasn’t been chosen yet. Open the card under Workspace Settings → Integrations, pick the property for this workspace and save. The property you choose is only the default — the agent can still query every property on that Google login by name.
Yes — any tool that can add a remote MCP server. Add https://connector.get-ryze.ai/mcp as a custom MCP server in Cursor, or point the MCP/HTTP-MCP node in Make, n8n or Zapier at that URL, then authorize. There are no native one-click apps for these and no separate REST API key; the MCP endpoint is the supported path.