Skip to main content
Connect the agent client you already use through Settings → AI & Agents → External agents. Its credentials act with your AutoAdy access, so review the connection’s scope before using management tools.

​
Choose a recipe

  1. Sign in to the AutoAdy identity that can access the intended workspace. Connect Meta before expecting Meta account data.
  2. Open External agents and select your client. Follow its current prerequisites and setup steps.
  3. Prefer OAuth account sign-in where the recipe supports it. If a key is required, create a named key in Settings → AI & Agents → AutoAdy API keys and copy it when shown.
  4. Store the key in the client’s private credential settings. Use the AutoAdy server URL supplied by the setup panel rather than a Meta access token.
  5. Follow Verify your first connection. Ask the client to list the Meta ad accounts reachable through AutoAdy and inspect the actual tool result.

​
Example: Claude on the web

You need access to Claude custom connectors. In a team or enterprise organization, an owner may need to add the connector before members sign in.
  1. In Claude, open Customize → Connectors, then Add custom connector. Older layouts may put Connectors under Settings. Name the connector AutoAdy if a name field is shown.
  2. Enter this server URL:
  3. Choose Add and complete the AutoAdy OAuth sign-in with the intended workspace identity. If the dialog asks how to authenticate, use account sign-in. If it asks for an OAuth client, choose Register automatically.
  4. In your Claude conversation, enable AutoAdy under the chat’s + → Connectors menu.
  5. Ask: “Use AutoAdy to list my connected Meta ad accounts. Return their names, IDs and currencies from the tool result. Do not change accounts, campaigns, budgets or settings.”
  6. Inspect the actual account-listing result and check its names, IDs, and currencies. A saved connector alone is not proof of a successful authenticated read.
You can also start from AutoAdy’s Claude setup, which prefills the connector dialog for your review. If authentication expires, reconnect through Claude’s connector controls and repeat the first read. If the custom option is unavailable, check your organization’s connector policy. These instructions follow Claude’s current custom-connector guide. The third-party sign-in flow was not live-tested as part of this help-center update.

​
Understand access

AutoAdy currently has no per-agent account scope and no read-only scope for paid API keys. A credential acts as you across the accounts you can access. The client owns tool allowlists and its approval controls; AutoAdy still checks workspace permissions, plan requirements, and write safeguards. Before expanding beyond reads, set the client’s supported allowlist or confirmation policy and review a specific proposed campaign or budget change. Creating a key does not unlock paid tools, remove credit requirements, or enable a source unavailable in your workspace.

​
Verify and recover

A successful sign-in and an empty account list mean different things: the agent may be authenticated while no Meta account is reachable. Check your Meta connection and workspace account grants. A client saying it is connected is not enough. Verify that its tool result lists the intended accounts. If authentication fails, check the recipe, key or OAuth state, and identity. A revoked or expired credential needs replacement or reconnection. When you stop using a client, revoke its key or connection in AutoAdy API keys. Never send credentials to support. Third-party client availability and sign-in policy can change; the setup panel records its recipe limitations. For custom technical setups, use the developer reference.