We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

laurentapia
Administrator

SERV_BannersforCommunitySite_BuildWith_Tapia_1100x224-B.png

 

Our annual #BuildWith Challenge is back for the 4th year, and we can’t wait to see what you create using ServiceNow Build Agent. Build Agent is Now Assist’s agentic AI tool designed to do all the heavy lifting of building  a fully featured ServiceNow application via natural language. #BuildWithBuildAgent is your chance to vibe code with ServiceNow and see just how fast you can build an amazing app! 

 

Join the challenge to get recognized and inspire the ServiceNow Community with what you can build using Build Agent. 

 

Complete the Challenge

 PSMDCM_SNUGSRelaunch_SocialCards_Option1_Event.png

 

 

What is Build Agent? 

 

ServiceNow Build Agent is a smart AI tool that helps you build, edit, and deploy full-stack applications via a conversational interface. It’s designed to support developers of all backgrounds, whether you're just starting out or a veteran of the platform. 

 

Build Agent is what we’ve been calling an accelerating tool; it accelerates your build process so you can bring ideas to life faster. It writes the code, organizes your files, fixes errors as it goes, and takes care of both the core logic and the user interface components. 

 

Just describe a task using natural language, and the agent manages the entire build process. 

 

Why Join the #BuildWithBuildAgent Challenge? 

 

  • Get hands-on with ServiceNow’s innovative agentic AI tool 
  • Inspire others by sharing what you built 
  • Earn recognition in the Community

 

2.png

 

 

How to Participate: 

 

  1. Get Started: Go into your ServiceNow IDE in your instance. Once you have activated the Build Agent skill (pre-installed on Personal Developer Instances), you can create a new application or edit an existing ServiceNow IDE app using natural language prompts. Include the initial prompt that kicked off your Build Agent journey, and any standout prompts that helped bring your app to life. 
  2. Document: Share your experience with others by submitting a description (300 words or more), a quick video, or an infographic about your app on social media with the hashtag #BuildWithBuildAgent. 
  3. Share: Comment on this blog post and be sure to attach a link to your social post. Include a brief description of your experience using Build Agent!

 

For more information on how to get started, feel free to check out the FAQs at the bottom of this post or watch the video walkthrough below. 

 

3.png

 

 

Getting Started with Build Agent 

 

Need help getting started? Check out the video below to learn how to get started with ServiceNow Build Agent and how to enter the #BuildWithBuildAgent Challenge. 

 

 

https://devlink.sn/EarlBuildWithBlog 

 

We’ve also compiled a helpful list of resources in our FAQs to help you get started. Explore how to participate, content creation tips, and more below. You can also access our #BuildWithBuildAgent toolkit for comprehensive guidance and best practices here. 

 

Still have questions? Our Community is here to support you every step of the way. Feel free to ask a question on this blog or our Now Assist forum. You can also reach out to us at buildwith@servicenow.com. Please note that response times may vary! 

 

Get started today and show us what you can build with Build Agent! 

 

 

4.png

 

 

General FAQs

 

Where Do I Enter?  

 

To enter, please follow all official guidelines and submit your entry by replying to this Community blog post. Your response should include a description of what you created using Build Agent, along with a direct link to your social media post where you shared your creation! Make sure to include #BuildWithBuildAgent in your social media post to enter the challenge. 

 

How can I get started? 

 

Access Build Agent in Personal Development Instance on developer.servicenow.com and sign in or create a free account. Click "Request Instance," choose the latest release, and submit your request. You'll get a URL and admin credentials within minutes to start building. 

 

How many natural language prompts can I use? 

 

For this challenge, users with Now Assist for Creator licenses have no limit! For everyone else, your ServiceNow Instance will be limited to 25 prompts. PDIs on developer.servicenow.com have a limit of 10 prompts per instance. Want to keep building with Build Agent? Just back up your work, release your Personal Developer Instance, request a new one, and continue creating your application. 

 

Where and What Do I Post on Community?  

 

Post it right here! At the bottom of this blog, leave a comment with a link to your social post, along with a description of what you’ve built using Build Agent. 

 

Do You Have Any Tips for Content Creation? 

 

We have compiled resources to help guide you through the #BuildWithBuildAgent content creation process here! 

 

Where and What Do I Post on Social Media?  

 

You can post on any social media platform, whether it’s LinkedIn, YouTube, X, Instagram, or public forums such as Reddit or Stack Overflow. You’re also welcome to share what you built using Build Agent on a personal or company blog or website. Just make sure your post is publicly accessible and includes #BuildWithBuildAgent ! 

 

Here’s an example of a social post: 

 
 

image (4).png

 

 

What if I Don’t Have Social Media or Don't Want to Post Publicly?  

 

Not to worry! Please send an email to BuildWith@servicenow.com, and we will contact you to redeem your swag.  

 

When Will I Receive My Swag?  

 

To receive swag, you must have completed the challenge by November 23, 9:00 AM PST, and placed your swag order no later than November 24th, 9:00 AM PST. Swag was available only while supplies lasted.

You can expect your swag to arrive in late January or early February. If you’re located outside the United States, please allow additional time for shipping. 

 

Do I Need to Fill Out a Submission Form?  

 

No submission form is required! Just follow the guidelines above and you’re good to go!  

 

How do I get featured in the App Gallery? 

 

Include the initial prompt that kicked off your Build Agent journey, and any standout prompts that helped bring your app to life. 

 

These prompts give us insight into your creative process and will help the team behind Build Agent choose which apps to showcase in the App Gallery. 

 

When Does the Challenge End?  

 

While the challenge officially concluded on November 24th, we welcome you to continue sharing your apps past this date. 

 

Who is Eligible to Enter the Challenge?  

 

We invite everyone aged 18 and above to join us! Whether you're an absolute beginner or an experienced developer, your contribution is valued! 

 

I Have a Problem Who Do I Reach Out to? 

 

Please comment directly on this blog or email buildwith@servicenow.com with #BuildWithBuildAgent Challenge in the subject line. Please refrain from emailing your entries to this address! We are monitoring the comments for your submissions.  

 

Do you have an example of what I should share on this Community blog?  

 

Yes! Here is an example for you. Be sure to include a link to your social media post! 

 

image (4) copy 2.png

 

5.png

 

 

Technical FAQs

 

What are the usage limits? 

 

For Personal Developer Instances (PDI), there is a limit of 10 prompts per instance per month. For customer instances that acquire Build Agent from the ServiceNow Store, there is a limit of 25 prompts per instance per month. For instances that are licensed for Now Assist for Creator, limits are based on your license. 

 

When are usage limits reset? 

 

PDI usage limits for Build Agent prompts reset every 30 days starting from the day on which the limit is set. 

 

What if I run out of usage or used all my prompts before this challenge? 

 

The limit is per instance, so you can elect to release your current PDI and request a new one, which will reset the usage count. Remember to back up any important work on your instance before you release it. 

 

How long can each prompt be? 

 

Very long. Feel free to be as simple or verbose as you want in each prompt. You can copy and paste large console logs, lengthy Product Requirement Documentation, or even huge error messages.  

 

What else does Build Agent handle besides writing the code? 

 

  • Compiling and validating source files 
  • Testing of its own files 
  • Pushing builds into the instance 

 

How does Build Agent differ from AI Agents or Agentic AI? 

 

While both names share “Agent,” Build Agent focuses on dev automation, whereas AI Agent (Agentic AI) focuses on task automation within workflows. Build Agent is an AI Agent. 

 

What are the limitations of Build Agent? 

 

Generally speaking, Build Agent is currently limited to the following abilities: 

 

  • ServiceNow Fluent via the ServiceNow SDK  
  • React based web components for user interfaces 

 

To see what ServiceNow metadata that Build Agent is able to create and edit on your behalf (like business rules, client scripts, tables, etc.), check out the documentation for Fluent here:

 

https://www.servicenow.com/docs/bundle/zurich-application-development/page/build/servicenow-sdk/conc... 

 

That means Build Agent’s scope is currently explicit. If it is not part of the Fluent SDK, then it cannot build it. But that also means that the capabilities of Build Agent are constantly growing as more and more metadata types are being added to the Fluent framework. 

 

What that will look like as you build your applications: Build Agent will elect to write scripted code instead of building a Flow Designer action or flow. Or another example: telling Build Agent to build something that it doesn’t have access to and forcing it to move forward despite this might cause it to build it a different way or simulate that it built it. 

 

Always remember that Build Agent is utilizing generative AI and can hallucinate. 

 

 

Where can I learn more about Build Agent and how to acquire it for my company? 

 

Read more about the product of Build Agent and Enterprise Vibe Coding at https://www.servicenow.com/products/vibe-coding.html#faq, including questions regarding governance and how Build Agent relates to App Engine. 

 

 

Terms and Conditions  

No purchase is necessary. #BuildWithBuildAgent Challenge is open only to individuals at least eighteen (18) years old at the time of entry. The Challenge begins November 12, 2025, at 10:00 a.m. Pacific Daylight Time ("PDT") and ends on November 24, 2025, at 11:59 p.m. PDT.  

Entrants must respond to the official forum with a 1) Screenshot, graphic, or video showing their app built using Build Agent or 2) a 300 minimum word description of the app they built with a screenshot using Build Agent AND entrants must post their video or blog into the ServiceNow Community Developer forum here AND share it on LinkedIn or Twitter with #BuildWithBuildAgent Challenge on their post AND the social media post will be linked to their forum post.   

The Submission must be your own, original work; The Submission must contain a relevant reason/response to the prompt of Build Agent; The Submission must meet the format and size requirements of the social platform used to enter; The Submission must conform with any applicable social media platform terms.  

The prize includes the official 2025 #BuildWithBuildAgent tote bag, while supplies last. The brand of tote bag may vary. Tote bag may take up to 4 weeks or longer to arrive once ordered. Approximate Retail Value (“ARV”): $10 USD.  

The ServiceNow Community reserves the right to access email data provided by the entrant in order to reach out to individuals who have completed the challenge. Entrants who have met the guidelines and have successfully completed the challenge will receive an email from ServiceNow with instructions on how to redeem the prize. International country restrictions will apply.  

Except where prohibited, participation in the Challenge constitutes each entrant's consent to use submission’s name, and photograph (including, without limitation, entrant’s Twitter and LinkedIn profile photo), voice, opinions and/or hometown and state for promotional purposes in any media, worldwide, without further payment or consideration. 

 
614 Comments
VaranAwesomenow
Mega Sage

Internal developer portal using ServiceNow

1. The Architectural Diagram (Mermaid.js)

Copy this block to visualize the "Fact → Rule → Score" engine:

VaranAwesomenow_0-1777194752799.png

 

 

Building a Port.io-Style IDP on ServiceNow: Beyond the Catalog

Context

I’ve been exploring how far we can push App Engine Studio and Now Assist for Creator to build a modern Internal Developer Portal (IDP) that rivals standalone tools like Port.io. The goal: a platform that doesn't just list services, but provides engineering intelligence through automated ingestion and declarative scoring.

The Philosophy: Facts → Rules → Scores

The secret sauce of an IDP isn't the UI; it’s the separation of concerns. You shouldn't update a "Service" record every time a build fails. Instead:

  1. Fact Layer: Ingest external signals (GitHub, SonarQube, Jira).

  2. Rule Layer: Use Decision Tables to evaluate those signals.

  3. Score Layer: Aggregate values into a weighted health score.

Architecture Overview

  • Core Model: x_idp_service (Extending cmdb_ci). We aligned this with CSDM 4.0 (Technical Service Offerings) to ensure the IDP talks the same language as the rest of the business.

  • The Fact Table: x_idp_fact. This acts as a buffer. Integrations write here, keeping the CMDB clean and auditable.

  • Scoring Engine: We moved away from heavy Business Rules and opted for Flow Designer + Decision Tables. This makes the "Logic" transparent to engineering leads who want to know why their score dropped.

DORA Metrics Implementation

We implemented the standard four (Deployment Frequency, Lead Time, Change Failure Rate, MTTR). The calculation is handled via a weighted model:

$$Score = 0.25 \cdot DF + 0.25 \cdot LT + 0.30 \cdot CFR + 0.20 \cdot MTTR$$

Why this works: It balances speed against stability. A team moving fast but breaking things will see their score dip, triggering a "Production Readiness" review.

The "Developer Experience" (UI Builder)

Using UI Builder, we created a workspace that gives devs a "Single Pane of Glass":

  • My Services: Filtered by ownership (managed_by).

  • Scaffolding: Record Producers that trigger GitHub Actions to bootstrap new repos.

  • Scorecard Transparency: A drill-down view showing exactly which DORA metric is hurting their grade.

Lessons Learned

  1. CSDM is your Friend: If you don't map your microservices to Application Services, your MTTR data will be garbage.

  2. Declarative > Scripted: Decision Tables allow you to change the "Passing Grade" for a service in seconds without a deployment.

  3. Data > UI: A beautiful dashboard with bad data is just a "pretty lie." Focus on the ingestion pipelines first.

I’m curious—has anyone else tried building a 'developer-first' layer on top of the CMDB? How are you handling the ingestion of non-ITSM facts?

Let’s compare notes in the comments!

JayanthiHCL
Tera Contributor

https://www.linkedin.com/posts/jayanthi-jeyakumar-02a5a3a7_buildmorewithbuildagent-buildmorewithbuil...
 @laurentapia 
🚀 Excited to participate in the
#BuildMoreWithBuildAgent challenge from ServiceNow! 

I recently used an AI-assisted prompt-driven approach to design a Deployment Checklist Workspace App on ServiceNow.

🎯 The goal was to transform software deployments from spreadsheets, emails, and manual tracking into a structured, automated, and auditable workflow.

🔧 Key Features

Modern Workspace Dashboard
Deployment tracking & progress visibility
My Tasks accountability view
Automated checklist generation
Completion % tracking
Readiness gates before deployment
Gantt timeline for deployment phases
Standards / Runbooks in one place
Audit-ready history and governance controls

📈 Business Value

Faster deployments
Reduced missed steps
Better cross-team coordination
Improved release confidence
Real-time leadership visibility
Stronger governance and compliance readiness

 

🤖 Built Using Simple Prompts

This solution was progressively created using AI prompts.

Prompt 1

Create an app for deployment checklist

Result:
Tables
Forms
Numbering
Basic logic

Prompt 2

Create a workspace

Result:
Navigation menu
Deployments
My Tasks
Reports

Prompt 3

Create a modern dashboard workspace

Result:
KPI tiles
Quick actions
Dashboard pages
Clean UI experience

Prompt 4

Add automation

Result:
Auto-create checklist tasks
Update completion %
Block status changes if tasks incomplete

Prompt 5

Add deployment timeline

Result:
Gantt chart
Phase tracking
Status colors
Progress view

Emeka Chiazor
Tera Contributor

 

I spent 13 years in maritime before I ever touched ServiceNow. Seven at sea, six in port operations management.
So when Build Agent's challenge opened, I knew exactly what I wanted to build.
Port ops today still runs on spreadsheets and email. Berth approvals over the phone. Customs, immigration, and health pratique on three separate systems that don't communicate. For a Harbour Master coordinating forty active vessels, that is the daily reality. I have lived it.

This is HarbourIQ, an AI port Management System. 46 UK ports. 6,500 vessels. One Harbour Master's decision inbox, all built on Servicenow.
The honest part. I started this during last year's Build Agent challenge. Ran out of prompt budget before it was usable. So every month, when the quota reset, I picked it back up. Ten months of compound iteration on top of what Build Agent gave me on day one.

The skeletal first prompt is "Build me a port operations management platform on called "HarbourIQ".
It should be a multi-port command center for UK maritime operations, covering the end-to-end lifecycle of a port call — from expected arrival through pilotage, berthing, cargo handling, and departure.
Core entities: Ports, Terminals, Berths, Vessels, Port Calls, Pilots, Tugs, Incidents, Clearances (Customs, Immigration, Health pratique).
User experiences:
Command Center homepage — single-pane overview of all ports
Harbour Master Workspace — decision inbox (berth approvals, sanctions holds, dark ship triage, dangerous-goods discharge, overstays)
Port Directory — browsable per-port cards with live state
Live vessel map (AIS-style)"

 

 

https://www.linkedin.com/posts/emeka-chiazor_buildmorewithbuildagent-servicenow-nowplatform-ugcPost-...

Chetan1
Tera Expert

*Hello ServiceNow Enthusiasts,*

🚀 I’m thrilled to unveil my submission for the #BuildMoreWithBuildAgent challenge — a powerful solution built with Build Agent and refined into a production-ready agent!

 

🚀 Just built a Solar Performance Pro app on ServiceNow using Servicenow's  #BuildMoreWithBuildAgent Key Business Values -Solar Assets: Tracking PV modules, inverters, and transformers with serial numbers and warranty dates. Due Diligence Logs: To capture engineering design reviews and site audit results. RCA Cases: To track performance drops, using a '5 Whys' field structure and linking to specific Assets.

 

Here is my app linkedin post -

https://www.linkedin.com/posts/chetan-bhadane-%E2%98%81-05659528_buildmorewithbuildagent-buildmorewi...

 

#BuildMoreWithBuildAgent💪🔐

 

Regards,

Chetan