Unleash the Power of Build Agents in the #BuildWithBuildAgent Challenge

[laurentapia]

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

 

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

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. 

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! 

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: 

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! 

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. 

[MadhyushaP]

I’m excited to share my experience building an AI-powered Employee Self-Service Agent using ServiceNow’s Build Agent – Unleash the Power of Agents. Below are the key highlights of my project and learning journey:

• I explored how AI-driven agents can completely transform the way employees interact with their organization. The Build Agent platform allowed me to design an employee assistant that provides instant support, answers questions, and helps users complete their tasks quickly. The simplicity of designing prompts, automating flows, and connecting data made the development process smooth and intuitive, even for someone still learning the platform.

• The Employee Self-Service Agent I created focuses on improving employee experience by giving quick access to essential information and guiding users through common processes. It can handle queries, create and track requests, and provide step-by-step assistance without the need for manual intervention. This demonstrates how AI can reduce dependency on support teams while ensuring consistency and accuracy.

• Working with ServiceNow Build Agent helped me understand how generative AI, automation, and workflows come together to build a smart, interactive, and reliable solution. I was able to experiment with different prompts, refine responses, and customize behavior to meet the needs of employees. This hands-on experience gave me a deeper understanding of how organizations can adopt AI to increase efficiency and accelerate digital transformation.

• I have also created a short video demonstrating how the agent works, how it responds to employee queries, and how the entire interaction flow looks. I would love to receive feedback, suggestions, or improvement ideas from the ServiceNow community. Learning from experts and fellow builders is something I truly value.

🔗 LinkedIn Video Link: https://www.linkedin.com/posts/madhyusha-pilli-a8a963325_servicenow-buildagent-ai-activity-739572896...

[KasiRamanathan]

Hello All, 

As part of the #BuildWithBuildAgent challenge, I used ServiceNow’s Build Agent to create a full healthcare application called Health-e PHR (Personal & Family Health Records) — built entirely using natural language prompts.

My goal was to solve a real pain point for middle-class families: organizing health records, tracking vitals, and managing medical reminders for the entire household. Here’s how I built it in minutes on my Personal Developer Instance (PDI).

🩺 Step 1: Define the Concept
I wanted the app to support:

• Family member profiles (spouse, parents, children)

• Upload & manage health documents (prescriptions, lab reports, scans)

• Track vitals like BP, sugar, weight, heart rate

• Reminders for checkups, vaccination & medication

• Emergency view with bl*od group, allergies, medications

• Simple, clean, card-based UI for everyday users

💬Step 2: Prompt Build Agent
Here’s the exact prompt I used:

Build a ServiceNow application called Health-e PHR that lets users upload and manage family health records, track vitals like BP & sugar, set reminders for checkups, and view emergency info for each family member. Use custom tables, UI Builder, and Flow Designer. The UI should be clean, modern, user-friendly, and use a simple dashboard with card-based design. Add sample dummy data for a family (parents + children) with example records, vitals, and reminders.

⚡Build Agent generated:
✅Custom scoped app
✅Family members, records, vitals & reminder tables
✅Sample dummy data
✅UI Builder workspace with card-style dashboard
✅Vitals chart view & emergency health card
✅Security so users only see their own data
✅All with zero manual coding — just prompts!

Screenshots:

📌You can find my social post here on LinkedIn.

[sb001062267]

I recently participated in the #BuildWithBuildAgent challenge, and it was a great learning experience. I built a Vehicle Servicing Management Application using the ServiceNow Build Agent, and I was impressed by how efficiently the tool translated natural language prompts into working components.

The Build Agent helped generate data models, flows, dashboards, and automation with minimal manual effort. This not only accelerated development but also demonstrated how AI can reduce lead time for solution delivery, improve consistency, and streamline complex processes.

From a business perspective, the application can help service centers track vehicle service requests, manage appointments, assign technicians, monitor progress, and improve turnaround time — ultimately enhancing customer satisfaction and operational efficiency.

Overall, the challenge highlighted the real potential of AI-assisted development on the Now Platform, and I’m excited to continue exploring more use cases.

Link to Social Post : https://www.linkedin.com/posts/sushant-baviskar_buildwithbuildagent-servicenow-buildwithbuildagent-u... 

[sb001062267]

I recently participated in the #BuildWithBuildAgent challenge, and it was a great learning experience. I built a Vehicle Servicing Management Application using the ServiceNow Build Agent, and I was impressed by how efficiently the tool translated natural language prompts into working components.

The Build Agent helped generate data models, flows, dashboards, and automation with minimal manual effort. This not only accelerated development but also demonstrated how AI can reduce lead time for solution delivery, improve consistency, and streamline complex processes.

From a business perspective, the application can help service centers track vehicle service requests, manage appointments, assign technicians, monitor progress, and improve turnaround time — ultimately enhancing customer satisfaction and operational efficiency.

Overall, the challenge highlighted the real potential of AI-assisted development on the Now Platform, and I’m excited to continue exploring more use cases.

Social Post : URL 

[Ravindra H V]

🚀Excited to share my latest #BuildWithBuildAgent Project!

I built a Shared Pool / Floating Asset Management app on ServiceNow to help organizations manage shared assets efficiently and streamline assignments for both employees and contractors.

🧭 Application Summary

The app is built entirely on the alm_asset table using a simple u_shared_pool flag.

Shared assets can be assigned and reassigned automatically, while availability is tracked in real time.

Admins can monitor usage at a glance, ensuring assets are efficiently managed without manual updates.

In emergencies, assets can be removed from a user if rules are violated, giving admins full control.

This solution is especially effective for contractors, offering a simple, controlled way to manage non-employee access.

🎯Goals

• Simplify shared/floating asset management

• Automate check-out/check-in tracking

• Give admins full visibility via a centralized dashboard

• Restrict access for non-admin users

• Allow emergency removal of assets in case of rule violations

⭐Key Features

• Identify shared assets using Model Category + u_shared_pool

• Automatic check-in/check-out triggered by assigned_to

• Admin-only dashboard displaying availability, assignments, and quick actions

• Add or remove assets from the shared pool easily

• Minimal configuration, no new tables required

• Emergency asset removal for policy enforcement

💼Customer Impact

• Faster access to assets → employees and contractors get what they need immediately

• Reduced manual tracking → saves hours of admin work weekly

• Clear visibility → know exactly what’s available and who is using it

• Streamlined operations → ensures shared assets are managed efficiently with minimal effort

• Cost-effective → reduces costs by leasing and sharing the same assets instead of buying new ones, minimizes losses from untracked or idle assets, and lowers administrative overhead through automation

• Better control for contractors → ensures non-employee access is secure and trackable

💡I’ve added a glimpse of the dashboard features in the attached video — check it out for a real-time view of the app in action!

📚Lessons Learned

• Small automation + flags deliver big efficiency gains

• Admin-only dashboards simplify governance without complexity

• Minimal changes to out-of-the-box tables can produce high-impact results

• Rule-based emergency removal ensures asset security
  
  Note: - Iam not able to add video please view my LinkedIn post where I’ve added a glimpse of the dashboard features as a video — check it out for a real-time view of the app in action!
  
  

   

   

LinkedIn Post : Link

 #servicenow #ServiceNowCommunity #BuildWithBuildAgent


Thank You
Ravindra H V

[shriramjosh]

Hi @laurentapia ,

As part of the #BuildWithBuildAgent challenge, I am presenting  CTMS- Application Summary

🎯 Overview

A comprehensive end-to-end CTMS built on the ServiceNow platform using Fluent API for managing medicines, trials, participants, and adverse events across all trial phases (Phase 1-4).

🎛️ Primary Dashboard

This comprehensive React-based dashboard includes:

• Real-time statistics with success rates, completion rates, and AE tracking
• Interactive charts showing trial outcomes, phase distribution, and adverse event severity
• Filterable trials list with sorting capabilities
• Responsive design that works on all devices

Please find my LinkedIn

https://www.linkedin.com/posts/shriram-joshi-b9223a3b_ctms-activity-7396047169352273920-8yGf?utm_sou...

I enjoyed working on this. Thanks for sharing this opportunity.

Prompt used to build: 

I want to build a custom application designed specifically for end-to-end clean trial management of new medicines. The system should store complete trial data, including pros and cons, side effects, patient responses, trial outcomes, and overall performance metrics. It must also maintain detailed background information about each medicine, such as its place of development, the research team involved, the number of years of research invested, formulation details, and supporting scientific documents. The application should support all clean trial phases (Phase 1–4) with clear status tracking, milestones, and results. It should also capture participant profiles, demographics, consent forms, and medical history relevant to the trial. A dedicated module for adverse events reporting must log severity, frequency, doctor notes, and follow-up actions.

[Gaurav Rathaur]

From an 11th-Standard Dream to a Real Application — How the BuildWithBuildAgent Challenge Helped Me Bring D-Labour to Life

When I was in the 11th standard, I carried a dream that felt far bigger than me.

I wanted to solve a real problem in India — the struggle of daily-wage labourers to find consistent work, and the equal struggle of contractors to find the right manpower at the right time. I imagined something that could transform this gap: an application called D-Labour.

A single platform where labourers could receive work requests, contractors could request the exact number of workers needed at any location, and even architects and raw materials could be sourced instantly.
A digital ecosystem to streamline construction-related services across India.

But at that time, that dream felt impossible.

I had no money to invest.
No technical knowledge or mentors.
No guidance, no community, no direction — just a young student with an idea and a heart full of aspirations.

So I kept that dream safe inside me, waiting for a time when I could finally bring it to life.

---

Fast-forward to Today — I Finally Lived My Dream

Today, years later, I finally saw that dream turn into reality — at least to a meaningful extent.

Thanks to the ServiceNow BuildWithBuildAgent Challenge, I transformed my childhood idea into a fully functional ServiceNow application.
End-to-end. Designed, developed, automated, and delivered.

The same features I once imagined on paper — job requests, labour allocation, location-based service delivery, workforce distribution, even extending it to architects and materials — I built them all using ServiceNow and the power of BuildAgent.

For the first time, my dream didn’t feel far away.
It felt real.
Achievable.
Built by me.

My Linkedlin Post and Video - https://www.linkedin.com/posts/gaurav-rathaur_buildwithbuildagent-servicenow-buildwithbuildagent-act...

---

Why the BuildWithBuildAgent Challenge Matters

This challenge is more than just a competition.
It is a bridge for people like me who always had ideas but lacked guidance, skills, or resources.

BuildAgent isn’t just a tool — it’s a partner.
It guides you, supports you, removes your barriers, and helps you bring your vision to life with speed and clarity.

You don’t need a big team, years of coding experience, or huge funding.
All you need is your idea — and the courage to start.

---

If You Have a Dream, This Challenge Is Your Starting Point

I often think:
What if I had something like BuildAgent back in 11th standard?
Maybe I would have started earlier.
Maybe my application would have been live years ago.

But I’m grateful I got this chance today — a chance to honour that young version of me who dared to dream.

And now, I want others to experience the same feeling.

If you have an idea — even a small spark — join the ServiceNow BuildWithBuildAgent Challenge.
Let it be your turning point.
Let it be the moment where your dream stops being “someday” and becomes “today.”

---

Your idea deserves a chance.

Your dream deserves to be built.
And this challenge gives you exactly that opportunity.**

I lived my dream through this challenge.
It’s your turn now.

[Suneesh]

Thank you so much @laurentapia , for giving instructions and  the opportunity to take on my first challenge! I truly appreciate your trust and support as I get started. I learned a great deal from this experience and enjoyed tackling something new. Looking forward to many more opportunities to contribute and grow with the team!

My LinkedIn post: Post | LinkedIn

[ClaudioG4376288]

As part of the #BuildWithBuildAgent challenge, I used ServiceNow’s Build Agent to create a scoped application called Team Pulse & Load Board, built end-to-end from natural language prompts.

The goal: give managers a live, visual view of team mood and workload, with heatmaps and simple flows to flag people at risk.

Here’s a step-by-step walkthrough of how I built and demoed the app on my Personal Developer Instance (PDI).
(I’ll share my LinkedIn post link in the comments 👇)

---

🧠 Step 1: Define the App Concept

I started from a very clear (but intentionally simple) concept: daily check-ins for teams, with a strong focus on visuals rather than complex processes. I wanted:

• A Team Member registry (name, team, role, at-risk flag…).

• A Daily Pulse check-in where each person records:

  • Mood: Very Happy / Happy / Neutral / Stressed / Burned out

  • Workload: 0–10 scale

  • Optional notes + location (office/remote/hybrid/other)

• A Workspace-style dashboard with:

  • Key metrics cards (check-ins today, average mood, average workload, at-risk count)

  • Two heatmaps:

    • Mood by person vs day

    • Workload by person vs day

  • Charts and lists (mood distribution, recent pulses, “at risk” list)

• A simple flow:

  • When someone submits “Stressed” or “Burned out”, mark them at risk and notify the manager.

Non-goals on purpose:

• No HR performance processes.

• No complex scheduling or calendar logic.

• No external integrations beyond basic email notifications and standard Now Experience components.

---

💬 Step 2: Prompt Build Agent

I then wrote a single, detailed prompt for Build Agent.
Here’s the core of it:

“Create an internal scoped application called ‘Team Pulse & Load Board’.
The app tracks daily mood and workload of team members and shows this in a modern, card-based Workspace.

Data model

• Table Team Member: name, user (sys_user), email, team, role, manager, at_risk (boolean), active.

• Table Daily Pulse: reference to Team Member, date (default today), mood (Very Happy / Happy / Neutral / Stressed / Burned out), workload (0–10), location, notes.

Roles & access

• team_pulse_admin: full access to all tables and configuration.

• team_pulse_manager: read all, manage Daily Pulse and Team Members.

• team_pulse_user: can create/edit Daily Pulse only for themselves.

Workspace & UX

• Create a Team Pulse Workspace with three tabs:

  1. General Overview: KPI cards, at-risk list, recent pulses, button to add a new pulse.

  2. Mood: mood distribution chart + mood heatmap (rows = people, columns = days, color by mood).

  3. Workload: workload stats + workload heatmap (color intensity by 0–10 scale).

• Add buttons to open the Team Member and Daily Pulse list views.

• From the dashboard, allow creating a new Daily Pulse and selecting the team member.

Logic

• Flow ‘Flag at risk team member’: on insert/update of Daily Pulse:

  • If mood = Stressed / Burned out → set Team Member.at_risk = true and email manager (or member email if manager missing).

  • If mood = Happy / Very Happy → optionally reset at_risk = false.

Seed the app with sample data for ~10–15 people across multiple teams and the last 30 days of pulses so that the heatmaps and charts look alive.
Focus on clean, modern visuals and a stunning dashboard.”

---

⚙️ Step 3: What Build Agent Generated

From that single prompt, Build Agent produced a fully-scoped app that I could refine:

• 📂 Scoped application Team Pulse & Load Board with:

  • Team Member table

  • Daily Pulse table (including the reference to Team Member)

• 👤 Roles & ACL setup:

  • team_pulse_admin, team_pulse_manager, team_pulse_user

  • Basic record-level protection so end-users only see their own pulses.

• 📊 Team Pulse Workspace with:

  • General tab

    • Metrics cards (check-ins today, average mood, average workload, at-risk count)

    • “Add Pulse” form where I can pick the team member, set mood/workload, notes, etc.

    • “At risk” card list with quick email action.

    • Recent pulses panel.

  • Mood tab

    • Mood distribution panel.

    • Mood heatmap (people vs date, green→red based on mood, emojis in the cells).

  • Workload tab

    • Workload stats (avg / min / max / distribution buckets).

    • Workload heatmap (people vs date, color intensity by load 0–10).

• 🔔 Flow / server logic:

  • A Flow / Business Rule that updates the at_risk flag and sends an alert email whenever someone reports “Stressed” or “Burned out”.

• 📈 Sample data:

  • Multiple teams (Platform, Operations, Customer Support, Engineering, QA).

  • About two weeks of realistic pulses, with a mix of positive and critical days so the dashboards and heatmaps look meaningful out of the box.

After a bit of tweaking (especially around the heatmap visuals and sample data), I had a demo-ready dashboard where managers can instantly see:

• Who is overloaded 🔥

• How mood and workload are trending over days 📆

• Which names keep appearing in the “at risk” area ⚠️

---

🎬 Step 4: Demo & Next Steps

I demoed Team Pulse & Load Board directly from my PDI:

• Logged in as a user, submitted a couple of Daily Pulses.

• Switched to a manager view to see the mood & workload heatmaps update in real time.

• Triggered the “at risk” flow with a “Burned out” entry and checked the email notification.

Next ideas I’m considering:

• Simple “My Pulse” page so each user can see their own history.

• Trend lines per person (e.g., rolling 7-day workload).

• Optional anonymized views for HR or leadership.

---

If you’re curious about the exact prompt or want to reuse this idea for your own team, I’m happy to share more details and screenshots in the comments.

Would love feedback from the community on what you’d add next to a Team Pulse-style app built with Build Agent 💚

[ClaudioG4376288]

As part of the #BuildWithBuildAgent challenge, I used ServiceNow’s Build Agent to create a scoped application called Team Pulse & Load Board, built end-to-end from natural language prompts.

The goal: give managers a live, visual view of team mood and workload, with heatmaps and simple flows to flag people at risk.

Here’s a step-by-step walkthrough of how I built and demoed the app on my Personal Developer Instance (PDI).
My Linkedin post is here : https://www.linkedin.com/posts/claudioguerini_buildwithbuildagent-buildwithbuildagent-servicenow-act...

---

🧠 Step 1: Define the App Concept

I started from a very clear (but intentionally simple) concept: daily check-ins for teams, with a strong focus on visuals rather than complex processes. I wanted:

• A Team Member registry (name, team, role, at-risk flag…).

• A Daily Pulse check-in where each person records:

  • Mood: Very Happy / Happy / Neutral / Stressed / Burned out

  • Workload: 0–10 scale

  • Optional notes + location (office/remote/hybrid/other)

• A Workspace-style dashboard with:

  • Key metrics cards (check-ins today, average mood, average workload, at-risk count)

  • Two heatmaps:

    • Mood by person vs day

    • Workload by person vs day

  • Charts and lists (mood distribution, recent pulses, “at risk” list)

• A simple flow:

  • When someone submits “Stressed” or “Burned out”, mark them at risk and notify the manager.

Non-goals on purpose:

• No HR performance processes.

• No complex scheduling or calendar logic.

• No external integrations beyond basic email notifications and standard Now Experience components.

---

💬 Step 2: Prompt Build Agent

I then wrote a single, detailed prompt for Build Agent.
Here’s the core of it:

“Create an internal scoped application called ‘Team Pulse & Load Board’.
The app tracks daily mood and workload of team members and shows this in a modern, card-based Workspace.

Data model

• Table Team Member: name, user (sys_user), email, team, role, manager, at_risk (boolean), active.

• Table Daily Pulse: reference to Team Member, date (default today), mood (Very Happy / Happy / Neutral / Stressed / Burned out), workload (0–10), location, notes.

Roles & access

• team_pulse_admin: full access to all tables and configuration.

• team_pulse_manager: read all, manage Daily Pulse and Team Members.

• team_pulse_user: can create/edit Daily Pulse only for themselves.

Workspace & UX

• Create a Team Pulse Workspace with three tabs:

  1. General Overview: KPI cards, at-risk list, recent pulses, button to add a new pulse.

  2. Mood: mood distribution chart + mood heatmap (rows = people, columns = days, color by mood).

  3. Workload: workload stats + workload heatmap (color intensity by 0–10 scale).

• Add buttons to open the Team Member and Daily Pulse list views.

• From the dashboard, allow creating a new Daily Pulse and selecting the team member.

Logic

• Flow ‘Flag at risk team member’: on insert/update of Daily Pulse:

  • If mood = Stressed / Burned out → set Team Member.at_risk = true and email manager (or member email if manager missing).

  • If mood = Happy / Very Happy → optionally reset at_risk = false.

Seed the app with sample data for ~10–15 people across multiple teams and the last 30 days of pulses so that the heatmaps and charts look alive.
Focus on clean, modern visuals and a stunning dashboard.”

---

⚙️ Step 3: What Build Agent Generated

From that single prompt, Build Agent produced a fully-scoped app that I could refine:

• 📂 Scoped application Team Pulse & Load Board with:

  • Team Member table

  • Daily Pulse table (including the reference to Team Member)

• 👤 Roles & ACL setup:

  • team_pulse_admin, team_pulse_manager, team_pulse_user

  • Basic record-level protection so end-users only see their own pulses.

• 📊 Team Pulse Workspace with:

  • General tab

    • Metrics cards (check-ins today, average mood, average workload, at-risk count)

    • “Add Pulse” form where I can pick the team member, set mood/workload, notes, etc.

    • “At risk” card list with quick email action.

    • Recent pulses panel.

  • Mood tab

    • Mood distribution panel.

    • Mood heatmap (people vs date, green→red based on mood, emojis in the cells).

  • Workload tab

    • Workload stats (avg / min / max / distribution buckets).

    • Workload heatmap (people vs date, color intensity by load 0–10).

• 🔔 Flow / server logic:

  • A Flow / Business Rule that updates the at_risk flag and sends an alert email whenever someone reports “Stressed” or “Burned out”.

• 📈 Sample data:

  • Multiple teams (Platform, Operations, Customer Support, Engineering, QA).

  • About two weeks of realistic pulses, with a mix of positive and critical days so the dashboards and heatmaps look meaningful out of the box.

After a bit of tweaking (especially around the heatmap visuals and sample data), I had a demo-ready dashboard where managers can instantly see:

• Who is overloaded 🔥

• How mood and workload are trending over days 📆

• Which names keep appearing in the “at risk” area ⚠️

---

🎬 Step 4: Demo & Next Steps

I demoed Team Pulse & Load Board directly from my PDI:

• Logged in as a user, submitted a couple of Daily Pulses.

• Switched to a manager view to see the mood & workload heatmaps update in real time.

• Triggered the “at risk” flow with a “Burned out” entry and checked the email notification.

Next ideas I’m considering:

• Simple “My Pulse” page so each user can see their own history.

• Trend lines per person (e.g., rolling 7-day workload).

• Optional anonymized views for HR or leadership.

---

If you’re curious about the exact prompt or want to reuse this idea for your own team, I’m happy to share more details and screenshots in the comments.

Would love feedback from the community on what you’d add next to a Team Pulse-style app built with Build Agent 💚