Skip to main content
The Neo API tool gives a Neo Agent access to Neo’s own public API (/public-api/*). Use it for “meta” automations — agents that report on other agents, reconcile configuration, kick off other workflows, manage technician-in-the-loop requests, or escalate to the Neo team.
Automatically enabled when you set Neo API permissions in your agent’s Integrations tab — there is no separate toggle in the tool list, the same way the PSA, RMM, and documentation API tools work. Access is scoped by permission groups. Want to call the API from your own code rather than from an agent? See the public API documentation. The full OpenAPI spec is also served at /public-api/openapi.json.

​
What It Does

  • Read and configure agents (workflows) — list, inspect, enable/disable, update settings
  • Browse Neo’s curated templates library — starting points for new agents
  • Query executions and event history — what ran, when, and what it did
  • Fetch artifacts produced by an execution — markdown notes inline, sandbox-file downloads via short-lived URLs
  • Inspect callbacks / triggers — see why a workflow did or didn’t match an event
  • Manage technician-in-the-loop requests — list pending approvals, see decisions
  • Look up RMM script runs the agent has launched
  • Read settings, end companies, and integrations configuration
  • Pull observability, performance rollups, and billing/credits data — including end-user (white-label) Teams bot active-user (MAU) usage and its monthly charge
  • Trigger and read Insights ROI analyses
  • View Phone Agent numbers and call history
  • Read chat sessions
  • Escalate an issue to the Neo team

​
Permission Groups

Like the other API-backed tools, Neo API access is split into permission groups, each set to Disabled, Read Only, or Read / Write — so you can give an agent read access to executions and analytics without letting it reconfigure other agents, for example.

​
Safety Controls

​
How to Configure

1

Open the agent's Integrations tab

Find Neo API. It needs no connection step — it’s Neo’s own API, so it’s available on every tenant.
2

Set permission groups

Choose an access profile, or set each permission group individually to decide which parts of the API the agent can read or write. Setting any group above Disabled gives the agent the Neo API tool.
3

Set approval requirements

Decide whether configuration writes require technician approval.
Start with Read Only — most “meta” agents (status digests, drift checks, “did workflow X run today?”) never need to write anything.