Overview of building apps in ServiceNow

  • Freigeben Version: Australia
  • Aktualisiert 12. März 2026
  • 3 Minuten Lesedauer
  • The ServiceNow AI Platform enables you to create global and custom applications. You can work in classic lists and forms, or you can build apps using App Engine products.

    What apps are in ServiceNow

    A ServiceNow app is a package that performs a specific task for a specified group of users. Think of an app as a container with a set of rules around who can access and edit it. For example, ServiceNow apps can include an API, a table, a workspace, a form, a flow, or any combination of those things.

    Some applications may only contain a few files, and others could contain thousands of files. In ServiceNow Studio, you can create and work on different sized apps with a variety of file types, depending on your permissions.

    Vibe coding and standard app development

    Vibe coding is an AI-driven approach to application development. Use vibe coding and ServiceNow AI-powered app building tools to describe your goals in natural language, and the ServiceNow AI Platform generates full-stack applications, workflows, and integrations. The ServiceNow AI Platform automatically incorporates governance into the app creation process.

    Vibe coding and using AI to build apps with the ServiceNow AI Platform collapses the traditional app development lifecycle—from ideation to deployment—into minutes instead of weeks. For more information, see Vibe coding and AI-assisted development on the ServiceNow AI Platform.

    Traditional app development on the ServiceNow AI Platform usually takes place in ServiceNow Studio. ServiceNow Studio provides a unified experience for all ServiceNow development activities, enabling admins and developers to extend base system solutions and create custom apps with ease.

    Use ServiceNow Studio to build apps and app files with integrated tools, access and edit app metadata in scoped and global apps, and package app changes for deployment, all in one powerful development tool. For more information, see ServiceNow Studio.

    Apps and plugins

    In ServiceNow, applications and plugins are related but distinct concepts.

    Applications are collections of ServiceNow components (tables, business rules, UI pages, etc.) that deliver specific functionality. They're essentially containers that bundle related features together. Applications can be:
    • Custom-built by your organization
    • Purchased from the ServiceNow Store
    • Core applications that come with ServiceNow (like Incident Management)
    Plugins are a specific type of application that adds functionality to your ServiceNow instance. The key differences between plugins and apps are as follows.
    • Plugins are typically installed via activation rather than traditional app installation.
    • Plugins are often foundational components that other apps depend on.
    • Once activated, plugins integrate deeply into the platform
    • Plugins are harder to remove - you can't easily deactivate a plugin once it's in use.
    Examples: ITIL, HR Service Delivery, Software Asset Management
    Hinweis:
    All plugins are applications, but not all applications are plugins. Plugins are the heavyweight, deeply-integrated applications that become part of your platform's foundation.

    Apps and workflows

    Applications are collections of components that deliver functionality - the building blocks of your ServiceNow instance.

    Workflows are automation tools within ServiceNow that define a sequence of activities to complete a process. Think of them as flowcharts that automate business processes. Workflows:
    • Automate approvals, notifications, and task assignments.
    • Define the step-by-step flow of work (if X happens, then do Y).
    • Are often part of an application.
    • Use a drag-and-drop workflow editor.
    Example: An approval workflow for purchase requests

    The relationship: A workflow is a component that lives inside an application.

    For instance, the Incident Management application might contain workflows that automatically assign tickets, send notifications, or escalate issues.

    Hinweis:
    Applications are the "what" (the functionality), workflows are the "how" (the automated processes that make things happen).