Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt

Use this file to discover all available pages before exploring further.

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, IT Glue, and Hudu API tools all work this way. You pick which permission groups the agent can use; the matching tool appears without a separate toggle.

​
Tool Categories

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 IT Glue and Hudu documentation, configurations, and assets

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 is assigned a credit tier based on its complexity. Your workflow’s credit cost is determined by the highest-tier tool enabled.
TierCostDescription
Basic1 creditSimple operations — retrieving data, generating passwords
Standard2 creditsDocumentation search, ticket search, sandbox shell
Advanced3 creditsPSA API writes, RMM script execution, Microsoft 365 operations, external API calls
For the API-backed integration tools (PSA, RMM, IT Glue, Hudu), the effective tier reflects the access you grant — Standard when every enabled permission group is Read Only, Advanced when any group allows writes.

​
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.