--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/pt-BR/application-development Release : - australia ft:locale : - pt-BR ft:publication_title : - Australia Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Build apps # Building apps with Creator Studio {#ariaid-title1} * Versão de lançamento: Australia * * Atualizado 12 de mar. de 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura By now, your admin has set up Creator Studio, given you permission to build an app, and you've got a great idea for a request-fulfillment app! How should you think about using Creator Studio to create your app? ## What apps are in ServiceNow {#building-apps-with-creator-studio__section_p1m_5zp_22c} 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. A Creator Studio app uses forms and automation to enable users to request something and move the request through the approval process. Creator Studio also enables you to the see the fulfiller's view of the Request App Workspace for the app. ## Create forms to gather request information {#building-apps-with-creator-studio__section_yrr_3cl_d1c} When finished, your app will look like a catalog of items that people can request. To create your app, you'll: 1. Select one of the available [catalog](https://servicenow-prod.fluidtopics.net/ACNUyxL3haCoieGCkodBsQ#gloss-catalog-creator-studio "A collection of items that represent all the items a requestor can ask for.") templates. 2. Customize a [form](https://servicenow-prod.fluidtopics.net/ACNUyxL3haCoieGCkodBsQ#gloss-form "A content page that displays fields and values for a single record from a database table.") to be included in the catalog using a WYSIWYG editor. A form describes one item in the catalog and provides space for questions that a requester will answer to specify details about what they want, such as the model number of a laptop. If your catalog needs multiple items, you can create multiple forms. Nota: You can create a form using Now Assist. To learn more, see [Generating forms with Now Assist](https://servicenow-prod.fluidtopics.net/qEyHZsCbQLPGp5_LtUHfZQ "Learn how the Now Assist in Creator application helps you to create forms for you in Creator Studio."). {#building-apps-with-creator-studio__ol_ndm_dv2_z1c} ## Automate workflows and simplify tasks with playbooks {#building-apps-with-creator-studio__section_mnh_brf_z1c} Streamlining your request-fulfillment process goes beyond just collecting information. Creator Studio empowers you to automate tasks with powerful [playbooks](https://servicenow-prod.fluidtopics.net/ACNUyxL3haCoieGCkodBsQ#gloss-playbook-creator-studio "A set of automated activities that occur based on a trigger. For example, sending an email when a request is approved. Think of playbooks as pre-programmed workflows that kick in after a form is submitted. They are like if/then statements: If this happens, then that will happen."). Think of them as pre-programmed workflows that kick in after a form is submitted. Here are some things that playbooks can do: * **Effortless approval routing:** Automatically route requests to the right person for approval, eliminating manual steps and bottlenecks. Imagine a laptop request automatically going to the IT manager for a thumbs-up. * **Intuitive playbook builder:** No coding required! Create custom playbooks using an easy-to-use editor. {#building-apps-with-creator-studio__ul_vgn_5qf_z1c} The playbooks you create use the information that people supply when they fill out your forms. So, the more details you ask for, the smoother the process runs. ## Workspaces give fulfillers a place to address requests {#building-apps-with-creator-studio__section_mw2_crf_z1c} Once deployed, your app will sit in its own workspace category, which makes it easy for fulfillers to answer requests. You can customize the workspace or use it as-is. For sys admin eyes only: Every app built in Creator Studio adds a record in the Request App Config table, which contains the table that the app uses. Your admin can change the table for an app, see [Administering an app's associated table](https://servicenow-prod.fluidtopics.net/1iO2ZEXDoyB8ByaDMQMpeg "Admins can change the default table that apps built in Creator Studio save their requests to.") for more information. The name of the table follows the format of scope_request, for example, x_snc_02_03_request. * **[Find existing apps in Creator Studio](https://servicenow-prod.fluidtopics.net/TJDWpATrSvOaTb4T1v5vyQ)** Perhaps you've been given permission to work on an app someone else created, or you want to add new items to the catalog in your app. The Creator Studio home page acts as your central hub, listing all the apps people in your company have built using Creator Studio. * **[Work with bookmarked apps in Creator Studio](https://servicenow-prod.fluidtopics.net/CAWQO8Qn~uLciS4eEYllIg)** Bookmark an app to quickly find it in Creator Studio, as well as ServiceNow Studio. * **[Change your development experience](https://servicenow-prod.fluidtopics.net/OKYYq_YAPmglLzL4cQb0aQ)** Choose a different development experience if you want a more robust environment using the experience switcher in Creator Studio. * **[App creation in Creator Studio](https://servicenow-prod.fluidtopics.net/9NHuHJL0uGen_0bo~p8jmA)** Have you ever dreamed of creating your own app? With Creator Studio, you might be closer than you think! The following links will send you to the sections in this guide that will walk you through the steps. * **[Collaborating with others to build apps in Creator Studio](https://servicenow-prod.fluidtopics.net/ZHCMnKoqNY9_r~2ka0rxiQ)** Sometimes you need help with building out your app, and that's OK! And sometimes other people need your help building their apps, which is great! This point is where collaboration comes into play. * **[Working with forms in Creator Studio](https://servicenow-prod.fluidtopics.net/SEjQV0vnta1LSqrAMkmd4g)** To add items or services to your catalog, you must create a different form for each thing being requested. * **[Working with automation in Creator Studio](https://servicenow-prod.fluidtopics.net/k1ZhzGExg2x1TgWkDZ12QQ)** How do you simplify and streamline tasks for fulfillers? Use automation! For example, you can have a task assigned automatically to someone based on what type of request it is. We'll use playbooks to accomplish adding this automation to your app. * **[Configuring workspace lists and records for form submissions](https://servicenow-prod.fluidtopics.net/5Q~2zMPn6iRO9O1ywF7CWA)** So, you've built your app, and people are submitting requests through it, that's great! However, you might be wondering where those requests go after they're submitted. They live in lists in a workspace where fulfillers can work on submitted forms, which you can customize in Creator Studio to suit your needs. * **[Testing and previewing Creator Studio apps and records](https://servicenow-prod.fluidtopics.net/xpZ7y54gqP7iAkJGlwoBWw)** Before you request deployment for your app, you can test out submitting a form and interact with any associated automation results on the record it creates. * **[Deploying your Creator Studio app](https://servicenow-prod.fluidtopics.net/XIrB3P1gP3uEycB0EEF2WA)** Congrats, you've built your app and are ready to share the first version of it with the world. That's great! Deployment is the next step in the process. * **[I've built my app in Creator Studio, now what?](https://servicenow-prod.fluidtopics.net/J8YfFkNwzJRERtt0tgsHQg)** You've added forms and automation to your app, and customized the workspace list configurations. Now what?