Built something you're proud of? Tell the story. A quick G2 review of App Engine or Build Agent helps other developers see what's possible on ServiceNow. Share your experience.

rwpeerenboom
ServiceNow Employee

 

build_agent_banner.png

 

Three prompts. That's all it takes to go from "I don't know how to start" to a structured prompting guide for any metadata type Build Agent supports.

The blank chat box is the new blank page. You open Build Agent in Studio, the cursor blinks, and… what now? You know it can do a lot. You just don't know how to ask for it.

Here's the trick: Build Agent can teach you how to prompt Build Agent. No external guide. No memorizing templates. Just three turns, in context, on the artifact you're actually about to build.

With the 2026 March Store Release, Build Agent now runs in ServiceNow Studio, supports global scope, and covers 35+ metadata types across 11 domains. Business Rules on Incident, ACLs on Change, Client Scripts on Problem — the everyday stuff — are all in scope. The capability is there. The hard part is knowing how to ask for it.

So let's skip the hard part.

▸ THE THREE-PROMPT TRICK

1

Pick your action and your scope

Use the New Chat menu — pick Create a file or Update a file, then choose your scope.

2

Ask what it can do

Get the menu of metadata types it actually supports in your scope.

3

Ask it to coach you on the one you care about

Get a structured prompting guide with templates, pitfalls, and a gold-standard example.

Step 1 — Pick your action and your scope

Open Build Agent in Studio and head to the New Chat menu. You'll see two starting options:

📁 Create a file   |   ✎ Update a file

Pick Create a file for new metadata, or Update a file to modify what's already there. We'll use Create a file for this scenario.

Build Agent then asks which scope you want to work in — pick Global if you're extending an OOB table like Incident, Problem, or Change. (For a custom app, pick the app from the list instead.)

 

BuildAgent Global Selection_1.png

Step 2 — Ask what it can do

Once you're scoped, ask:

"What are the metadata types you can create and or edit?"

You'll get a clean table back: Tables & Columns, Business Rules, Client Scripts, Script Includes, UI Pages, Scripted REST APIs, Flows, ACLs, Roles, System Properties, Application Menus & Modules, Email Notifications, Scheduled Scripts, Service Catalog Items, Catalog UI Policies, and more.

This is your menu. Now you know what's actually available before you start typing wishes into the void.

BuildAgentMetaDataPrompt_2.png

Step 3 — Ask it to coach you on the metadata you care about

Pick the metadata type you need and ask for a prompting guide:

"For Business Rules, generate a comprehensive guide to crafting effective prompts."

Build Agent activates its skill, pulls the relevant knowledge, and gives you back something a lot more substantial than a list of tips. You get a full reference document.

BuildAgentPromptingGuideForBRs_3.png

 

▸ WHAT YOU ACTUALLY GET BACK

For Business Rules, the guide comes back with eight sections:

1.  Anatomy of a prompt (the 5 dimensions)

2.  Timing — the most critical decision

3.  Six prompt templates by use case

4.  Optional details you can include

5.  Common pitfalls (vague vs. better)

6.  Advanced prompt patterns

7.  Quick prompt checklist

8.  Gold-standard example


The five dimensions are Table, Timing, Action, Condition, Logic — with timing called out as the #1 factor in getting a correct rule on the first try.

That's it. Three turns. You now have a tailored reference document for the exact thing you're about to build — generated by the same agent that will execute it.

The "vague vs. better" payoff

The most useful section of the guide is the pitfall comparison. Here's a real example pulled straight from what Build Agent generated:

✕ VAGUE

"Add a script to the incident table"

✓ BETTER

"Create a before business rule on the incident table that sets assignment_group on insert when category is Network"

Same intent. Wildly different outcomes. The "better" version specifies all five dimensions — table, timing, action, condition, and logic — which is exactly what the guide tells you to do. That's the value: you stop guessing what Build Agent needs and start giving it what it asks for.

Why this works

Build Agent has the context. It knows what metadata types it supports, what fields each one needs, and what trips builders up.

When you ask it to write your prompt, you're getting guidance from the system that's about to read that prompt — which is a lot more accurate than a generic "prompting tips" article written six months ago.

Same trick. Every metadata type.

The guide for Business Rules has a sibling for every other metadata type Build Agent supports — and they all follow the same shape. Anatomy section, "most critical decision" callout, templates by use case, pitfalls, gold-standard example.

Ask the same Step 3 question for Tables & Columns and you get back a guide structured around column type selection (the most critical decision for tables), with seven prompt templates covering basic tables, extending OOB tables, adding columns, reference fields, choice fields, auto-numbering, and cross-scope columns.

Same shape. Different content. Once you know the pattern, every metadata type you encounter has a built-in coach available. 

 

▸ TRY THIS ON YOUR NEXT TASK

Got something on your plate this week?

A Business Rule to write on Incident
An ACL to add to a custom field on Change
A Client Script for a form behavior tweak
A new column on a custom table

Open Build Agent  →  pick Global  →  ask for a prompting guide before you ask it to build anything. You'll write a better first prompt and skip a couple of refinement loops.

 

▸ HEADING TO K26?

The Vibe Code Lounge Lab gets you started. This trick takes you further.

At the Lounge

The Vibe Code Lounge (CreatorCon show floor, sponsored by NVIDIA) runs a hands-on lab built around your problem from your org — not a canned demo. Quick video intro to Build Agent, guided prompting on something real, then AI Agents auto-generate screenshots and push your build to a live app gallery on the show floor. You leave with a working POC and a Code Brew mug.

🚀

After the Lounge

The Lab gets you to your first POC. The three-prompt trick gets you to every one after — on any of the 35+ metadata types Build Agent supports. Take what you learned in the Lounge and run the same three turns against a Business Rule on Incident, an ACL on Change, or whatever's sitting in your backlog.


🎟️ K26  ·  May 5–7, 2026  ·  Las Vegas (Venetian + Wynn)

📍 Vibe Code Lounge  ·  CreatorCon show floor  ·  Add it to your agenda

Example Build Agent Guide is attached to this post.

Review the guidance that Build Agent provides in the attached article.... ALL generated by Build Agent.


What metadata development type consumes most of your backlog?

Drop it in the comments — and if you've already used this "ask Build Agent how to prompt Build Agent" trick, share what worked.

Version history
Last update:
Tuesday
Updated by:
Contributors