SaaS connectors
These connectors cover the assistants, agent builders, automation tools and code repositories where teams build agents outside the big clouds. Most connect with a read-only API key in about two minutes.
Every connector follows the same pattern:
- Create a read-only credential in the vendor's admin console (details below).
- In Waxell, open Agent Discovery → Connections → Add connection and choose the platform.
- Paste the credential, fill in any settings shown, and select Connect & sync.
Credentials are encrypted at rest and never shown again. Waxell only reads — it never creates, edits or runs anything on these platforms during discovery. For the cloud platforms see Microsoft, Google Cloud and AWS; for MSP platforms see Hatz AI. The connector catalog compares every connector in one table.
AI assistants & workspaces
Glean
Discovers: your Glean agents and their configuration.
| Field | Value |
|---|---|
| Glean API token | A token with the agents read scope, created in Glean's admin console under API tokens. |
| Instance name | Your Glean instance — the part before -be.glean.com. |
Atlassian Rovo
Discovers: Rovo agents, derived from your organization's audit events. Rovo has no agent-inventory API, so Waxell builds the inventory from agent lifecycle events (created, updated, deleted) as they appear in the audit trail. Agent activity, including MCP tool calls, flows into the Activity tab.
| Field | Value |
|---|---|
| Atlassian org-admin API key (unscoped) | In admin.atlassian.com, open Settings → API keys as an organization admin and create a key without scopes — the events API rejects scoped keys. |
| Atlassian organization ID | The ID in your admin URL: admin.atlassian.com/o/<org-id>. |
User-level AI activity additionally requires Atlassian Guard Premium.
Salesforce Agentforce
Discovers: Agentforce agents through the Waxell Agentforce connector rather than a key here. Select Agentforce in the picker and follow Open Connect to set up the connector; discovered agents appear in Agent Discovery automatically.
ServiceNow AI Agents
Discovers: Now Assist and AI Agent Studio agents.
| Field | Value |
|---|---|
| OAuth bearer token | A token for an integration user with read access to the sn_aia_* tables. |
| Instance subdomain | The part before .service-now.com — for example acme. |
Box AI
Discovers: Box AI Studio agent configurations.
Select Connect with Box to authorize with your Box account. If your organization prefers, choose Use an API token instead and paste a Box OAuth bearer token with read access.
Dust
Discovers: the assistants in your Dust workspace.
| Field | Value |
|---|---|
| Dust API key | A workspace API key from Dust's admin settings. |
| Workspace ID | Your Dust workspace ID. |
| Region host (optional) | https://eu.dust.tt for EU workspaces; leave blank for the default. |
Agent builders
Devin
Discovers: Devin sessions. With an Enterprise service user, Waxell also pulls the enterprise audit log — session lifecycle, secret access, MCP server changes and guardrail events — into the Activity tab.
| Field | Value |
|---|---|
| Devin API key | An API key from Devin's settings. For the audit log, use an Enterprise service-user key with permission to manage enterprise settings. |
Mistral Agents
Discovers: the agents defined in your Mistral La Plateforme organization.
| Field | Value |
|---|---|
| Mistral API key | An API key from the Mistral console. |
LangGraph Platform
Discovers: the assistants (deployed graphs) on a LangGraph Platform deployment.
| Field | Value |
|---|---|
| LangSmith API key | A LangSmith API key with access to the deployment. |
| Deployment URL | The URL of your LangGraph deployment. |
Botpress
Discovers: the bots in your Botpress Cloud workspace.
| Field | Value |
|---|---|
| Personal access token | Created in Botpress Cloud under your profile settings. |
| Workspace ID | Your Botpress workspace ID. |
Workflow, iPaaS & RPA
n8n
Discovers: n8n workflows that contain AI agent nodes, on n8n Cloud or self-hosted.
| Field | Value |
|---|---|
| n8n API key | Created in n8n under Settings → n8n API. |
| Instance URL | Your n8n URL, for example https://acme.app.n8n.cloud. |
UiPath
Discovers: deployed processes and agentic automations in UiPath Orchestrator.
| Field | Value |
|---|---|
| Orchestrator access token | An access token for an external application with read access to Orchestrator. |
| Orchestrator URL | Your Orchestrator URL, including your organization and tenant for Automation Cloud. |
| Folder ID (optional) | Limit discovery to one folder. |
Workato
Discovers: Workato recipes — the building blocks of Workato agents and skills.
| Field | Value |
|---|---|
| Workato API token | An API client token with read access to recipes. |
| Data-center host (optional) | For example https://app.eu.workato.com; leave blank for the US data center. |
Code and repositories
The repo-scan connectors find custom-built agents in your source code. Waxell reads only dependency manifests (such as requirements.txt, pyproject.toml, package.json, go.mod and pom.xml), matches known agent frameworks, and records a finding per repository. Source code is never stored. Findings show the frameworks detected and link to the repository.
GitHub
Choose one:
- Waxell GitHub App (recommended, least privilege) — install the app on your organization and paste its GitHub App installation ID; leave the token blank.
- Personal access token — a read-only token with contents: read.
Organization (optional) limits the scan to one organization.
GitLab
Select Connect with GitLab to authorize, or paste a read-only access token with read_api and read_repository. For self-managed GitLab, enter your GitLab URL.
Datadog LLM Observability
Discovers: the agents actually running, derived from your Datadog LLM Observability spans (grouped by ML app). Use it alongside the repo-scan connectors to confirm which agents found in code are live.
| Field | Value |
|---|---|
| API key : Application key | Your Datadog API key and an application key with read access to LLM Observability, joined with a colon. |
| Datadog site | For example datadoghq.com, datadoghq.eu or us5.datadoghq.com. |
| Lookback window (optional) | How far back to look, for example now-30d. |
After connecting
Each connected platform gets its own page in Agent Discovery with its agents, activity, controls and connection health — see Platform pages. Inventory and activity refresh automatically every 10 minutes.
If a sync fails, the connection shows the reason in plain language — for example that the credentials were rejected or lack a permission — with the technical detail under Details. Fix the credential in Settings and select Sync now.