Recommended Free Tools
Build a ServiceNow AI agent by first confirming that your instance has the required release, plugins, roles, entitlements, model access, and geography support; then define a narrow business objective, create the agent and skills in AI Agent Studio or with Build Agent in ServiceNow Studio, test each skill and the complete workflow, activate triggers deliberately, and transport the approved application through your normal ServiceNow release process. Treat the agent like production application code: review generated instructions, tools, scripts, ACLs, metadata, and diffs before anything reaches users.
1. Confirm access, release, and scope before building
AI Agent Studio is ServiceNow’s central workspace for creating, managing, and testing agents and agentic workflows. Build Agent in ServiceNow Studio, or in the ServiceNow IDE where enabled, can create or update application artifacts through conversational instructions. Your first task is to establish what the target instance actually supports; menus and capabilities vary by release, licensing, model-provider entitlement, plugins, role assignments, and deployment geography.
As an Amazon Associate I earn from qualifying purchases.
Access checklist
- Open All > App Development > ServiceNow Studio, or launch the ServiceNow IDE, and verify that the AI development features appear.
- Install and configure the required ServiceNow Otto application and any AI Agent Studio or Gen AI components required by your release.
- Configure approved MCP server connections when the agent must call external tools or services. Confirm endpoint authentication, network reachability, and which application scope may use each connection.
- Verify the
adminorflow_designerrole required for the operation you intend to perform. Developers, testers, approvers, and production operators may need different roles. - Check model-provider and product entitlements in the instance. A visible menu does not prove that generation, evaluation, or a particular model is licensed for your users.
- Confirm that the target release includes the Build Agent and AI Agent Studio functions you plan to use.
Availability can differ for in-country offerings and restricted environments, including FedRAMP, NSC DOD IL5, Australia IRAP-Protected, and self-hosted deployments. Validate feature and data-residency eligibility with your ServiceNow administrator before designing around a capability that may not be available in the target environment.
Choose one outcome for the first release
Start with a single business result, such as classifying an incident and proposing the next action, rather than an open-ended assistant that can modify every record. Define the owning team, the records involved, the systems the agent may call, and the human decision that remains outside the agent. A narrow first scope makes authorization, testing, rollback, and success measurement tractable.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
2. Choose the build surface and execution model
The build surface determines how you create artifacts; the execution model determines whether a human must authorize work at run time. They are separate decisions.
| Decision | Option | Best fit | Important control |
|---|---|---|---|
| Build surface | AI Agent Studio | Create, manage, test, and evaluate agents and agentic workflows in a dedicated workspace. | Use its test and evaluation tools before activating triggers. |
| Build surface | Build Agent in ServiceNow Studio or the ServiceNow IDE | Conversationally generate or update application files, metadata, workflows, skills, instructions, tools, ACLs, and supporting scripts. | Review the proposed plan, generated files, diffs, and checkpoints before accepting changes. |
| Execution | Autonomous | Tasks that do not require a support user’s approval at each invocation. | Constrain records, tools, write operations, and escalation paths with ACLs and explicit instructions. |
| Execution | Supervised | Work that a designated support user must review and authorize. | Select a support user who satisfies the instance’s security controls and define what happens when approval is denied or times out. |
Build Agent is not a substitute for code review. ServiceNow documentation describes it as “an autonomous AI agent” that creates and updates applications through conversational interaction, but every generated change still needs a developer’s inspection and an approved transport path.
3. Write the agent contract before opening the builder
An agent contract is the short, testable specification that prevents prompt wording from becoming the only design document. Write it in ordinary language and keep it versioned with the application.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Define the objective and input context
- Objective: State one observable business outcome, including what the agent must not do.
- Inputs: Name the trigger, record type, fields, conversation context, attachments, and any required user attributes.
- Records: Identify tables and fields the agent may read, create, update, or delete. State whether related lists and historical records are in scope.
- Tools: List Flow Designer actions, skills, scripted APIs, integrations, and MCP tools the agent may invoke. For each tool, specify permitted parameters and side effects.
- Access boundary: Apply least privilege by application scope, role, ACL, domain, and data classification. Decide whether sensitive fields must be masked or excluded.
- Outputs: Define the object or fields downstream steps receive, such as a classification, recommendation, created record number, confidence explanation, and escalation reason.
- Escalation: List ambiguity, policy, authorization, confidence, timeout, and tool-failure conditions that require a human or a conventional flow.
- Success criteria: Specify the expected result for representative records, unacceptable behavior, and the evidence a tester must capture.
Example contract
Objective: Triage a newly created hardware incident and propose the correct assignment group.
Reads: incident fields, approved configuration-item attributes, and the assignment group's published routing rules.
Writes: no incident update until a support user approves the recommendation.
Tools: classification skill and knowledge-search action only.
Output: {classification, proposed_group, rationale, escalation_reason}.
Escalate: missing configuration item, conflicting routing rules, restricted data, or tool error.
When the agent is invoked from a flow, these contract choices map directly to the Flow Designer Gen AI spoke action: objective, execution mode, whether to wait for completion, expected outputs, and (for supervised execution) the support user who authorizes the work.
4. Create the agent, workflow, skills, and controls
Build in AI Agent Studio
- Open AI Agent Studio and create an agentic workflow for the business objective. Name the workflow and agent so that an operator can distinguish development, test, and production variants.
- Add the agent’s instructions, input context, skills, tools, and trigger conditions. Keep instructions specific about allowed records, output format, escalation, and prohibited actions.
- Associate each skill with the correct application scope. A skill that reads or writes another scope must have an intentional, reviewed access design rather than an accidental cross-scope privilege.
- Configure ACLs, tool credentials, and data filters before testing. Do not rely on a prompt to enforce authorization.
- Save the workflow and inspect its generated metadata. Record the agent version, instruction revision, skill versions, tool definitions, and connection references.
Use Build Agent for application changes
- From ServiceNow Studio or the ServiceNow IDE, describe the application outcome and the artifacts you want Build Agent to create or change.
- Let Build Agent propose a plan. The proposal may include files, metadata, an agent, skills, instructions, tools, ACLs, workflows, and supporting scripts.
- Review the plan before accepting it. Ask for narrower scope, explicit output schemas, or safer failure handling when the proposal is broader than the contract.
- Accept only the reviewed changes. Build Agent records checkpoints so you can compare later iterations and roll back a change that weakens behavior or introduces an unwanted dependency.
- Inspect the resulting files, metadata, scripts, ACLs, and application scope in the normal ServiceNow development views. Generated code is still code: check query filters, error handling, secret references, and update behavior line by line.
Design skills as independently testable capabilities
A skill should perform one coherent operation with a clear input and output, such as retrieving an approved policy or calculating a routing suggestion. Keep side effects separate from retrieval where possible. Publish a skill before another skill can use it as a tool; an unpublished skill will not be a dependable dependency for the rest of the workflow.
5. Review and iterate with checkpoints
Use short cycles: change one instruction, tool definition, ACL, or script; run the relevant test; inspect the result; then keep or revert the checkpoint. Review both conversational behavior and application artifacts.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
What to inspect
- Generated instructions: Are objectives, boundaries, escalation rules, and output schemas unambiguous?
- Tool definitions: Can the agent pass an unrestricted table name, query, URL, or record identifier?
- ACLs and scope: Does every read or write require the intended role and domain access?
- Scripts and flows: Are null values, timeouts, duplicate submissions, partial failures, and retries handled?
- Diffs and metadata: Did the change add an unexpected dependency, credential, trigger, or update to a production-facing table?
- Conversation change logs and checkpoints: Can another developer explain what changed and restore the previous behavior?
Do not merge a prompt fix that masks an authorization or data-model problem. Correct the control at the ACL, tool, flow, or script layer and then make the agent’s instructions consistent with that control.
6. Test skills and the complete agent separately
Test each skill first
Use ServiceNow Otto Skill Kit to run a skill against representative records and inputs. Include normal, incomplete, contradictory, unauthorized, and unusually large inputs. Verify the returned type and fields, not just the prose explanation. Confirm that a failed tool call produces the contract’s escalation result rather than a fabricated answer.
Run end-to-end tests in AI Agent Studio
- Run a manual single execution with a known record and capture the prompt context, tool calls, parameters, outputs, authorization decisions, and elapsed stages available in the instance.
- Run automated evaluations across multiple executions. Include records from each supported assignment group, priority, domain, language, and data classification that the agent will encounter.
- Assert the output object, side effects, and escalation behavior. A fluent response is not a passing result if it updates the wrong record or omits a required field.
- Repeat evaluations after every change to instructions, tools, model configuration, ACLs, or dependent skills.
Add ATF coverage
Generate and run Automated Test Framework tests where appropriate for application behavior and regression coverage. ATF should verify deterministic controls such as ACLs, flow outcomes, record updates, trigger conditions, and error branches. Pair those tests with agent evaluations for non-deterministic language and tool-selection behavior.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
AI Agent Studio testing does not provide live Now Assist panel assistance. If you need to test a live-agent interaction, use Now Assist in Virtual Agent and keep that scenario separate from the AI Agent Studio workflow evaluation.
Minimum test matrix
| Scenario | Expected evidence |
|---|---|
| Typical valid request | Correct skill and tool calls, schema-valid output, and only permitted side effects. |
| Missing or contradictory data | Clarifying question or escalation, with no guessed record update. |
| Unauthorized user or record | Denied access and a safe explanation; no data leakage through the response or logs. |
| Tool timeout or integration failure | Bounded retry or escalation, preserved correlation information, and no duplicate write. |
| Prompt injection or malicious field content | System instructions and tool boundaries remain in force; untrusted text is not treated as a command. |
| Supervised approval denied | No protected action occurs and the refusal is represented in the expected output. |
7. Activate triggers and integrate with flows deliberately
Generated triggers are not activated automatically. Enable them only after development review, testing, and approval.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Invoke an agent from Flow Designer
- Open the target flow in Flow Designer and add the Gen AI spoke action named Use an AI agent.
- Select the configured agent and provide the objective or invocation context required by your contract.
- Choose Autonomous when the operation needs no human authorization, or Supervised when a support user must review and authorize it.
- Choose whether the flow waits for completion. Waiting is appropriate when downstream steps require the agent’s output; asynchronous execution is appropriate when the flow can continue without it.
- Map the expected output fields to downstream actions. Use explicit data pills or object fields rather than parsing free-form text.
- For supervised execution, select a support user who meets the security controls and define approval, rejection, timeout, and reassignment behavior.
- Save, test, and activate the flow only after the agent trigger and the surrounding flow conditions have passed review.
Keep invocation context free of secrets and unnecessary personal data. Pass record identifiers and approved fields, then let ACL-protected tools retrieve what the agent is allowed to see.
Best Value
8. Deploy through governed application transport
Deploy the agent and its supporting application as one governed release. The exact transport depends on your instance process and the artifact types involved.
| Transport | Use when | Checks to perform |
|---|---|---|
| Update sets | Your organization promotes scoped configuration through ordered update sets. | Confirm all agent, skill, flow, ACL, script, and connection-reference records are captured and that no unrelated changes are included. |
| Deployment pipelines | Automated promotion gates are available between development, test, and production. | Require source review, automated tests, security checks, and an approval gate before production. |
| Application Repository | The application is packaged and distributed through the supported repository process. | Validate application version, dependencies, scope, install order, and post-install activation state. |
| Git or other source control | Your ServiceNow development model tracks supported application files in source control. | Review commits and diffs, protect branches, and verify that generated metadata and instance-only settings are handled correctly. |
Release sequence
- Have a developer who did not author the change review the generated files, instructions, tool permissions, ACLs, scripts, metadata, and test evidence.
- Obtain deployment approval from the application owner and security or risk approver required by your organization.
- Run readiness checks in the target environment: required plugins and entitlements, model and MCP connections, roles, credentials, ACLs, dependent skills, and application scope.
- Transport the approved application using the supported update set, pipeline, Application Repository, or Git process. Do not copy production credentials from a lower environment.
- Verify the installed metadata, agent and skill versions, trigger state, ACLs, connection references, and scheduled or flow dependencies.
- Execute a representative production-safe test with a controlled record. Confirm the expected output, approval behavior, logs, and absence of unintended writes.
- Record the release version, test evidence, owner, rollback checkpoint, and procedure for disabling the trigger if behavior degrades.
9. Security and operating controls
Prompt instructions explain behavior; they do not replace ServiceNow authorization. Enforce protection in ACLs, scoped APIs, flow conditions, tool parameters, and integration credentials.
- Use separate credentials and connection references for development, test, and production.
- Grant tools the smallest record and field access needed for the contract. Avoid generic query or update tools when a purpose-built action can enforce a fixed table and field set.
- Classify data before including it in prompts, model context, evaluation sets, or logs. Mask secrets, tokens, unnecessary personal data, and restricted fields.
- Log correlation IDs, tool calls, approvals, failures, and resulting record changes according to your retention policy. Avoid logging complete sensitive payloads.
- Define an owner for instructions, skills, model settings, ACLs, and integrations. A production agent without a named owner will drift as tables and policies change.
- Monitor trigger volume, tool failures, authorization denials, escalations, duplicate writes, and output-schema violations. A sudden change in any of these is a release signal, not merely a prompt-quality issue.
- Keep a tested rollback path: disable the trigger, route the flow to a conventional fallback, restore the prior checkpoint or application version, and preserve evidence for investigation.
10. Troubleshoot common failures
| Symptom | Likely cause | Resolution |
|---|---|---|
| AI Agent Studio, Build Agent, or a required action is missing | Unsupported release, missing plugin, role, entitlement, model access, or restricted geography. | Check release documentation and instance entitlements, install the required component, assign the least-privilege role, and confirm regional or regulated-environment availability. |
| A skill cannot be selected by another skill | The dependency is not published or is in an inaccessible application scope. | Publish the dependency, verify scope and ACLs, and retest its contract independently. |
| The agent returns an answer but does not complete the action | A tool is unavailable, parameters are invalid, authorization failed, or the flow did not wait for completion. | Inspect the execution trace and tool parameters, correct the permission or mapping, and choose synchronous waiting when downstream steps require the result. |
| The agent updates an unintended record | Broad tool input, weak query constraints, or an ACL that permits more than the contract. | Replace generic tools with constrained actions, validate record and domain filters server-side, tighten ACLs, and add a regression test for neighboring records. |
| A trigger never runs after deployment | Triggers require explicit activation and may have been transported inactive or blocked by conditions. | Check the deployed trigger state, flow conditions, roles, and event data; activate only after confirming approval and test evidence. |
| Development passes but production fails | Different model entitlement, connection, data shape, role, plugin, scope, or ACL. | Run the readiness checklist in production, compare metadata and connection references, and execute a controlled representative test before opening the feature to users. |
| Automated evaluations are inconsistent | Non-deterministic model behavior, ambiguous instructions, changing records, or an unstable dependency. | Freeze test fixtures where possible, assert structured outputs and side effects, tighten instructions and tool schemas, and repeat tests across multiple executions. |
11. A practical go-live gate
Do not enable a production trigger until every applicable item below has an owner and evidence:
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
- The objective, records, tools, outputs, escalation rules, and autonomous or supervised mode are documented.
- Required plugins, roles, entitlements, model access, MCP connections, and geographic restrictions are confirmed in the target instance.
- Generated instructions, files, scripts, ACLs, metadata, diffs, dependencies, and application scope have been reviewed by a developer.
- Each skill passes Otto Skill Kit tests, the complete workflow passes AI Agent Studio manual and automated evaluations, and deterministic behavior has ATF coverage where appropriate.
- Unauthorized access, prompt injection, malformed input, tool failure, timeout, duplicate submission, approval rejection, and rollback scenarios have been exercised.
- The transport package or pipeline includes every required artifact and excludes unrelated changes.
- Production verification covers metadata, trigger state, permissions, a representative execution, expected outputs, and post-execution record state.
- Owners know how to monitor failures and disable or roll back the agent without waiting for a new application release.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.

