--- 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 --- # Create your first app # Creating your first app 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) 3 min. de leitura Creator Studio helps you create your app by dividing it into smaller parts. Each does something special, and you work on them sequentially. Summary: After reading this section, you'll understand: * The general workflow for building an app * What goes into the idea for an app * Who to ask for help {#creator-studio-creating-your-first-app__ul_bcg_2bn_51c} Let's give you a very high-level overview of what you will do in each part. 1. **Let's get you started.** Create your app in a few simple steps before you can start building it out. Find out more in [Create an app in Creator Studio](https://servicenow-prod.fluidtopics.net/ksYFGEC9vz4VuTeuZpj2wQ "Get started creating an app by specifying basic info for the app that you're building in Creator Studio.").Start by selecting a catalog template that closely matches the app you want to create. For instance, if you're creating an app for IT issues, there could be a catalog template with pre-designed fields for specifying IT-related problems. While the template might not cover everything you need, it gives you a solid starting point. Check out how you select a catalog template to create your app's first form using Now Assist or on your own in [Create an app in Creator Studio](https://servicenow-prod.fluidtopics.net/ksYFGEC9vz4VuTeuZpj2wQ "Get started creating an app by specifying basic info for the app that you're building in Creator Studio."). 2. **Or ask to work on someone else's app!** If you see an app that you want to work on but don't have access to, you can request to get access to it. Or, you can ask your admin to create an app for you that you can then work on. Find out how in [Ask to work on an app in Creator Studio](https://servicenow-prod.fluidtopics.net/a4v5mK0Oin9f62Wv89OBaA "Want to work on an app but don't have access to it? No problem. We'll show you how to ask for access.") or [Ask an admin to create an app for you in Creator Studio](https://servicenow-prod.fluidtopics.net/zeColU0SBKnqK6jlen6j3A "Don't have permission to build an app? Ask your admin to get you started by creating a basic app for you. Just give them a name and tell them what you want the app to do. Once they start it, you’ll take over and modify it."). 3. **Add a form to collect information.** A form is where you gather information by asking questions, but first you have to add the form to the app. See [Add a form to an app in Creator Studio](https://servicenow-prod.fluidtopics.net/Nn~~o_uHlAxbSMoWJczG4g "Add a form to the app you just created. Forms contain questions that people respond to when submitting a service desk request.") for more information. 4. **Ask for the info you need.** Customize the default catalog template to ask for the specific information your fulfiller needs. How do you know what customizations to make? Ask yourself what info the fulfiller needs to fulfill a request. We'll show you how to add, subtract, and modify the form fields in [Customize your form for an app in Creator Studio](https://servicenow-prod.fluidtopics.net/GdrfClVqs5FrT5pxHD0_hg "Forms help people ask for things they need, such as a new keyboard or permission to take time off. The default form that's added when you create an app in Creator Studio needs some changes to fit your needs. For example, you must add question labels to gather information about the request."). 5. **Make your forms available.** Once your form is ready, publish it to make it accessible to requesters. The process is straightforward, and we'll walk you through it in [Publish a form for your app in Creator Studio](https://servicenow-prod.fluidtopics.net/TD6WNSD2YbrN5e6wMrSHPQ "Publishing forms once they're ready makes them available as catalog items in the production instance for published apps."). 6. **Specify the automatic actions that your forms trigger.** You'll want your app to take some action when a requester submits or revises a form. For instance, a new request might trigger approval from a manager. Another action could be emailing the requester to confirm their request submission and provide them with a tracking number. Discover more automation possibilities in [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."). 7. **Customize the workspace fulfillers use.** Creator Studio automatically creates a workspace category where fulfillers work on requests.Creator Studio automatically creates a form submission workspace category where fulfillers work on requests that is ready to use, out of the box. The workspace is ready to use as-is, but you can tweak it to suit your needs. Find out how in [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."). 8. **Test your app to see if it's ready.** Think your app is ready? Test it out to see your answers to form questions and automation results in the record your app generates. Get details in [Test one of your forms for an app](https://servicenow-prod.fluidtopics.net/dzc1Ee~C5V3bUG~VqHNcjg "Use the Try it button on the Request forms tab to submit a request, which triggers any associated playbooks and creates a record that you can work with in Creator Studio."). 9. **Get your app deployed to production.** Once your app is spiffed up, tested, and ready to go, ask an admin to move it to a production environment for you so real users can begin using it to make requests. Find out how in [Request deployment for your app from Creator Studio to production](https://servicenow-prod.fluidtopics.net/vzR_aQB9u80iFdgH6OY7qw "After you've tested your app's forms, playbooks, and workspace category on a non-production instance, for example a development instance, deploy it to a production instance so users can access it."). {#creator-studio-creating-your-first-app__ol_up2_yhg_s1c} Use case: Sam's job at the Example Company is to answer employee requests for office equipment. They've done this for years by receiving emails and keeping spreadsheets of requests, requesters, equipment, prices, dates, and fulfillments. Their company is growing, and the number of requests is now overwhelming. "I'm spending all my time reviewing requests instead of doing all the other parts of my job." They'd like to create an app that enables people to request office equipment, automatically sends an email confirmation of the request, stores the request, and enables them to fulfill or reject the request with the click of a button. They've never written a line of code in their life, but with Creator Studio, they can create the exact application they want.