What a ServiceNow Project Produces
The output is configuration in your instance, not a repository. Tables, fields, forms, portal pages, workflows, business rules, and reports are created and updated in place. The agent can also read your current configuration first, which is what makes changes to an existing application practical rather than guesswork. It can inspect tables, widgets, reports, and roles before proposing anything.A ServiceNow project asks you to connect an instance before Build Mode becomes available. Configuration is normally applied to a development instance. See Integrations.
What the Agent Configures
Seven areas are in scope. Each is covered in detail in Component Reference.Working Across Areas Rather Than Within One
The most useful requests name a business outcome and let the agent coordinate the pieces, because a real ServiceNow feature almost never lives in one area. Locking down a portal, for example, touches page roles, table permissions, and possibly a UI policy. Adding an approval step touches the status model, transition permissions, a business rule, and a notification. Asking for the outcome gets those changed together and consistently; asking for one piece at a time tends to leave the others behind. Two request shapes that work well:- “Build a clinician-facing dashboard for overdue lab results.”
- “Restrict this portal to administrators and add an approval workflow.”
Beyond Building New Things
Two kinds of work matter as much as new configuration and are easy to overlook. Refactoring. Unused widgets, rows, and modules can be removed, duplicate reports and fields consolidated, and inconsistent naming and UX patterns brought into line. Instances accumulate this over years. Troubleshooting. Why a field is not visible, why a record will not move to a state, or why a portal widget returns no data are all answerable by inspecting the configuration rather than guessing at it, and the fix is applied to the cause rather than worked around.What Stays in Your Hands
The agent works through APIs, not the browser. It does not click through Studio. Anything that has no API surface has to be done in ServiceNow directly. Scope discipline is yours to set. Whether a change belongs in a scoped application or the global scope is a decision with long consequences for upgrades and delegation, and the agent will raise it rather than assume.Your Next Step
See every component in detail
Tables, UI, portal, workflow, automation, and reporting.
Enter Build Mode
What a ServiceNow project needs before it can build.
See what a Build request sends
What goes out, and what comes back.
Compare the low-code platforms
What each supported platform covers.