In recent weeks, ServiceNow has announced a new partnership with Figma, the cloud-based collaborative design tool. The result of this is a new integration that will enable ServiceNow users to easily build enterprise applications based on Figma designs.
These full-stack apps can be created without technical expertise, instead relying on AI to generate UI code, data models, business logic scaffolding, navigation, and starter logic – all based on Figma designs. Here’s everything you need to know about the integration.
ServiceNow and Figma: A Partnership in AI
“Enterprises today are looking to deliver AI-powered experiences faster than ever, yet they often struggle to translate early-stage designs or prototypes into solutions that can reliably perform at enterprise scale.”
Figma
The new integration uses the ServiceNow Build Agent, an AI product that enables ServiceNow users to create enterprise apps using natural language instructions. This practice, known as ‘vibe coding’, has become increasingly popular this year. The Build Agent is itself a relatively new tool, announced just a few months back as part of ServiceNow’s recent Zurich release.
The new integration adds a new dimension to this, by enabling designers, product managers, and developers to use Figma designs as part of the prompts these Build Agents are built on – alongside natural language commands. To do so, users can simply add a link to the Figma design into the AI prompt.
Together, the Build Agent and the Figma integration aim to bring vibe coding to the ServiceNow ecosystem. This practice of using AI to build applications has been one of the most widely discussed trends of 2025, with Collins Dictionary even selecting the term as its word of the year.
Despite its popularity, the results of vibe coding have been decidedly mixed. It certainly has its proponents, with many saying that the ability to quickly create apps without code is a game-changer. But at this stage, the technology remains in its infancy, and there’s a growing consensus that it’s best suited to simple, small-scale use cases, without complex infrastructure or security requirements.
For more complex cases, users will generally need a developer to edit, supervise, or finish the AI agent’s work. Nonetheless, this can still save time in comparison to building the application from scratch, meaning it could well be worth the investment for many.
How Does the Figma/ServiceNow Integration Work?
The integration principally relies on Figma’s Model Context Protocol (MCP) server – an open standard that enables Figma to send information and designs to third-party AI agents. The MCP server was first released in June this year, and was explicitly designed for use cases like the new ServiceNow integration.
Here’s how it works:
- First, users create designs in Figma. This could involve a designer creating a high-fidelity mockup or using Figma Make to create detailed mockups from low-fidelity designs or screenshots.
- Once the Figma user is satisfied with the designs, they add the Figma link to the ServiceNow Build Agent prompt. The integration uses OAuth 2.0 authentication and secure server-to-server communication to ensure the information is securely transferred to ServiceNow.
- From there, Figma will send a range of information to the Build Agent. This will include design tokens (color, typography, spacing, etc.), component properties (overall structure and design), and layout logic (including auto-layout rules, constraints, and the hierarchical structure of the page).
- This is where ServiceNow takes over. From here, all information and design tokens are stored within the customer’s ServiceNow instance. This means all the standard ServiceNow privacy and compliance standards now apply.
- Then, the Build Agent generates a full-stack ServiceNow application. This includes UI code, data models, and business logic scaffolding. All apps are built with ServiceNow’s built-in permissions, audit trails, and version control, ensuring effective governance and trust.
At this stage, the app operates just like any other application built in the ServiceNow ecosystem.
How to Get Started With the Build Agent Integration
If you’re a ServiceNow user looking to try out the new integration, there are a few prerequisites you’ll first need to be aware of:
- You’ll need a ServiceNow instance that’s up to date with either the Zurich Patch 2 or Yokohama Patch 8 releases.
- Users will also require a Now Assist for Creator subscription, and have the Build Agent installed with the version 1.2.1 plugin.
- On the Figma side, you’ll need a Figma account with either a Dev or Full seat on a Figma Pro, Org, or Enterprise plan.
- Then, you will have to whitelist the Figma MCP Server in ServiceNow, which will require admin privileges. To do so, follow the instructions in this ServiceNow developer article.
You can also find out more details about the integration and how to use it in the ServiceNow Community.
Why Have Figma and ServiceNow Partnered?
When the Build Agent was first launched in September, the goal of the exercise was clear: To jump onto the vibe coding trend that had already received so much attention. To some, this might seem like a reactive attempt to capitalize on the latest AI bandwagon – and to some extent, that’s probably true. But it’s not the whole story.
Whether you’re creating apps with code or commands, ServiceNow’s approach is to build in rigorous governance, compliance, and security controls by design. This makes it more effective at building complex enterprise applications, with strict governance requirements. Since these are the use cases that vibe coding most struggles with, ServiceNow seems to have something genuinely unique to offer here.
For ServiceNow, therefore, the partnership with Figma makes straightforward business sense: It opens up this product to a wider range of potential users and use cases. It means more people can use the Build Agent, and they can do more with it.
But from Figma’s perspective, the partnership announcement comes at an interesting time. The company’s recent financial performance has been decidedly mixed, particularly since first going public with its stock (known as ‘FIG’), in June this year. To date, the stock’s performance has been volatile. After an initial public offering (IPO) of $33, it shot to a closing value of $115 on its first day of trading, but has consistently dropped in the months since. As of December 4, 2025, its most recent closing value was $38.71.
At the same time, the company remains unprofitable and has faced recent concerns about insider stock selling in recent months.
Clearly, therefore, the ServiceNow partnership comes as part of a broader strategy from Figma, combining huge investment in AI products and partnerships with tech giants like ServiceNow, in order to chart a path to profitability. It’s this same strategy that has resulted in new products like the Figma Model Context Protocol and Figma Make both being announced this year. But just like with vibe coding more generally, the results of these products remain decidedly mixed.
“Figma Make still struggles to nail designs on the first try when using simple language. It performs well with simple prompts like ‘Design a user-friendly sign-up flow for a website that delivers an effortless onboarding experience for new users’.
“But for anything more complex, especially enterprise-level apps, designers, product teams, and developers will likely need a few iterations before things start to feel right.”
Klaud Koronkiewicz, Graphic Designer and Figma User
At this point, only time will tell if the partnership with ServiceNow will help improve the success of Figma’s AI products and lead to a more profitable and sustainable financial position for the company.