erstan. They need no external connector setup, though write-capable tools still follow the runtime’s approval and policy checks.
Use Erstan tools when an agent needs to work with Erstan-native objects: tasks, projects, teams, documents, files, workbooks, skills, agent runs, or Agent Builder definitions.
Agent Builder action presets
The Erstan action picker is generated from the available tool catalog, grouped by resource. Search includes common names and older labels. Runtime-only and retired tools are excluded from new actions. An Erstan action runs one operation with the inputs you configure and returns its structured result. Use an AI step when the model should choose inputs or combine tools. Existing saved AI action steps keep their behavior.
The picker also includes available file and document reads, task and project operations, native Sheets, Excel files, Skills, and Agent Builder operations. Code actions are available when the workspace enables Code.
Extract File Data reuses cached parsing. You can extract fields directly from a file; add a separate Parse step when you also need the readable content. Its validation result identifies missing fields, invalid types, and other schema failures. Document confidence and OCR confidence describe different evidence. Automated visual review does not replace a human review step.
The Builder sets
contractVersion: "file-tools/v2" for new Inspect, Parse, and Extract actions. Set it explicitly when calling these tools directly, including calls using the fileId shortcut. V2 reads do not persist extracted text to the source; saved unversioned calls retain their earlier behavior.
Extract accepts a bounded draft-07 JSON Schema for an object, with nested arrays, required fields, enums, standard formats, and acyclic local references. External or recursive references, custom regular-expression patterns, and asynchronous schemas are rejected before parsing or model work. Schemas are limited to 32 levels and 4,096 nodes. Validation preserves returned types and does not fill defaults or insert missing null values.
Check schemaValidation.status, schemaValidation.errors, and review.required before using extracted fields. Invalid data remains available for review; schema conformance does not establish factual accuracy. documentConfidence is separate from ocrConfidence. Field evidence is explicitly marked not_assessed when references and independent confidence are unavailable. review.humanReview.status remains not_performed after automated visual review.
Tasks and projects
Task tools let agents create work, update its status, add comments, assign participants, attach references, and group the work under projects.
For project behavior and scope, see Projects.
Documents, files, and workbooks
These tools create and manage the artifacts agents produce.Agents, runs, and Agent Builder
Agents can inspect other agents and their runs, and approved builder tools can create or update Agent Builder drafts.
For user-facing builder guidance, see Choosing AI steps.
Skills, teams, members, and communication
Data, AI, and NetSuite helpers
These are Erstan-hosted helper tools, even when they support NetSuite work.Next steps
Tools by connector
See tools that come from connected systems and providers.
Tools overview
Understand tool sources, behavior, and policies.
Projects
Learn how
er_project_list fits task assignment.Choosing AI steps
Decide when an AI step should think, respond, call tools, branch, loop, or pause.