Skip to main content
Tools define what actions Neo Agents can perform. When you configure a workflow, you select which tools are available and customize their settings to match your processes.
Some tools turn on automatically once you configure an integration’s permissions on the workflow’s Integrations tab — the PSA, RMM, Microsoft 365, and documentation API tools (IT Glue, Hudu, Lexful, Confluence, SharePoint) all work this way. You pick which permission groups the agent can use; the matching tool appears without a separate toggle.

​
Tool Categories

Tool credit costs

What each tool costs, and why a scheduled or chat agent is billed per call — not once per run

PSA

Read and write your PSA — tickets, notes, time entries, contacts, configurations, and more

RMM

Read device and monitoring data, and run scripts on target devices to fix problems

Microsoft 365

Manage Entra ID, Active Directory, Exchange, and Intune — users, groups, licenses, mailboxes

Communication

Send messages to end users and internal teams — ticket notes, email, Teams, SMS

Search

Find documentation, similar tickets, configurations, and web resources

Documentation

Read and write documentation in IT Glue, Hudu, Lexful, Confluence, and SharePoint

Management

Log time, generate passwords and secure links, trigger workflows, call external APIs and Neo’s own API

Built-in & Internal

Tools the agent always has or gets automatically — search helpers, the sandbox, plumbing

Approvals

Request human approval before sensitive actions

​
Credit Tiers

Each tool has a tier. What you pay depends on how the agent runs, not only on which tools are enabled.
For the API-backed integration tools (PSA, RMM, Microsoft 365, and the documentation platforms), the effective tier reflects the access you grant — Standard when every enabled permission group is Read Only, Advanced when any group allows writes.
Tools Neo adds for you never set a triggered agent’s per-run price. Searches, the sandbox, and similar always-on tools are listed under Built-in Capabilities with no price tag. On a scheduled or chat agent they still bill when called — Find Documentation is 2 credits per search, Sandbox Bash is 2 per call. Skills in that same list are free to load; the tools they use are not. The full table is on Tool credit costs.

​
Tool Dependencies

Some tools automatically enable other tools they depend on. For example:
  • Execute RMM Script automatically enables the device-lookup and script-search capabilities it needs
  • Update and create operations automatically enable the field-options lookups they need
Dependency tools are shown in each tool’s documentation. They’re automatically enabled when you select the parent tool.

​
Technician-in-the-Loop

Many tools support Technician-in-the-Loop approval, which requires human approval before the agent takes action. When enabled:
  1. The agent prepares the action and explains what it wants to do
  2. A Teams message is sent to configured technicians
  3. A technician approves or rejects the action
  4. The agent proceeds based on the decision
Start with approval enabled for sensitive operations. As you gain confidence in the agent’s decisions, you can disable approval for routine tasks.