--- 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 --- # Quick start # Creator Studio quick start {#ariaid-title1} * Versão de lançamento: Australia * * Atualizado 12 de mar. de 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 16 min. de leitura This quick start guides you through the process of building your first app in Creator Studio and requesting its deployment. At a minimum, you need to create the app, and then add and customize a form, which is where users submit their fulfillment requests. Building your first app is a good way to understand how Creator Studio enables easy app creation. For a more thorough tutorial where you build a gift card request app, see [Creator Studio tutorial](https://servicenow-prod.fluidtopics.net/jzbqQLoxemTW~he1mgwGYw#creator-studio-tutorial-landing "Use this tutorial to create a Gift Card Request app to streamline the processes of providing recognition to a team."). Your system administrator must add you to the Creator Studio Users group. ## Quick start part 1: Create an app {#ariaid-title2} Create your app first. Later, we'll continue building it out. ### Antes de Iniciar Your system administrator must add you to the Creator Studio Users group. Nota: If you don't have permission to create apps yourself, you can ask your admin to create one for you. See [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.") to find out how. ### Por Que e Quando Desempenhar Esta Tarefa You can also watch a short video on how to create an app. ### Procedimento 1. Head over to the Creator Studio home page by going to AllApp EngineCreator Studio. Figura 1. Start Creator Studio The Creator Studio home page appears. To learn more about working in the home page, check out [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."). 2. Select the Create app button to start the process of creating an app. Figura 2. Create app button * If you're a system administrator, you can read more about this topic in [Application collaboration](https://servicenow-prod.fluidtopics.net/NFI_m30krkjNdKpYnrRlvg "People with admin privileges can manage the permissions of developers collaborating on an application."). * If you want to know how to request an admin to create the app for you, check out [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."). {#crs-quick-create-app__ul_h25_5bs_dcc} 3. Select the type of app you want to build, such as Service Desk. Service Desk apps enable users to submit requests, report issues, and access support related to services within your company. Nota: Your admin may have hidden this page. Figura 3. Select the app type 4. Select the Continue button. 5. On the page that appears, enter a Name and brief Description of the app's purpose. Figura 4. Create an app 6. Select Create app. 7. Select a catalog template from the list, which your admin can customize, and then select Apply template and continue to finish building the foundation of the app. You may not see a catalog template that is exactly what you want. So, choose one that's the closest. If none look close, select the Creator Studio Default Template option, if your admin hasn't removed it. It's your best bet. Dica: Feel free to click through the list of catalog templates. Previews will help you pick the one you want. Don't worry if you don't see other catalog templates to choose from! Your admins may not have created any custom catalog templates for you yet. 8. Choose how you want to build the form: * To use Now Assist, stay on the Build with Now Assist tab and enter directions for the form you want. 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."). Nota: You can select Try an example to see some examples of the available directions. To see a quick mock up of what the form will look like, select the generate form preview button. If you want a different form, change the provided direction and select Regenerate preview for a quick look. * To manually build the form, select the Build on your own tab and enter the information for the form:{#crs-quick-create-app__table_mhx_mqd_zdc__entry__2} | Field | Description | |-|-| | Form name | A descriptive name for the form. | | Short description | Some information on what the form is used for. | | Long description | Additional details for the form. You can include content like images and links to other sources of information (for example, a knowledge base article). | [Tabela 1. Form details] {#crs-quick-create-app__table_mhx_mqd_zdc} {#crs-quick-create-app__choices_lhx_mqd_zdc} If you don't see the option to Build with Now Assist tab, you need to check with your admin. To install Now Assist for Form generation, see [Configuring form generation in Creator Studio](https://servicenow-prod.fluidtopics.net/P6dYjp7Zw9Le26DbjVmVEg "Install and configure Now Assist for Creator in Creator Studio."). 9. Select Save and edit form. ### Resultado Okay, you've created the beginning of your very own application! You've named and described it. Now, let's add a form. ## Quick start part 2: Customize your form's info {#ariaid-title3} Enter some basic information for the form to tell users what it does. ### Antes de Iniciar Your system administrator must add you to the Creator Studio Users group. ### Procedimento 1. **Opcional:** Enter a Short description that appears to users when they see its tile. 2. **Opcional:** Provide more info in the Long description box. You can use rich text, for example to include links and tables. 3. Select Save and edit form. ### Resultado Get more details on customizing your form 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."). Next, we'll build and publish a form. ## Quick start part 2: Add a form {#ariaid-title4} Let's add a form so people can make a request. Forms contain questions that people respond to when submitting a service desk request. ### Antes de Iniciar Your system administrator must add you to the Creator Studio Users group. ### Procedimento 1. Select + Add form to get started. Figura 5. Select to add a form 2. Select a catalog template from the list, which your admin can customize, and then select Apply template and continue. You may not see a catalog template that is exactly what you want. So, choose one that's the closest. If none look close, select the Creator Studio Default Template option, if your admin hasn't removed it. It's your best bet. Dica: Feel free to click through the list of catalog templates. Previews will help you pick the one you want. Don't worry if you don't see other catalog templates to choose from! Your admins may not have created any custom catalog templates for you yet. 3. Choose how you want to build the form: * To use Now Assist, stay on the Build with Now Assist tab and enter directions for the form you want. 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."). Nota: You can select Try an example to see some examples of the available directions. To see a quick mock up of what the form will look like, select the generate form preview button. If you want a different form, change the provided direction and select Regenerate preview for a quick look. * To manually build the form, select the Build on your own tab and enter the information for the form:{#creator-studio-quick-add-form__table_mhx_mqd_zdc__entry__2} | Field | Description | |-|-| | Form name | A descriptive name for the form. | | Short description | Some information on what the form is used for. | | Long description | Additional details for the form. You can include content like images and links to other sources of information (for example, a knowledge base article). | [Tabela 2. Form details] {#creator-studio-quick-add-form__table_mhx_mqd_zdc} {#creator-studio-quick-add-form__choices_lhx_mqd_zdc} If you don't see the option to Build with Now Assist tab, you need to check with your admin. To install Now Assist for Form generation, see [Configuring form generation in Creator Studio](https://servicenow-prod.fluidtopics.net/P6dYjp7Zw9Le26DbjVmVEg "Install and configure Now Assist for Creator in Creator Studio."). 4. Select Save and edit form. ### O que Fazer Depois Now that you've added a form to your app, it's time to customize it! Remember: You can add multiple forms to your app for if you need to. ## Quick start part 3: Add questions to and publish a form {#ariaid-title5} Add questions to the form and define what they are asking to gather the information that your fulfiller needs to evaluate the request. You can then publish it to make its catalog items available. ### Antes de Iniciar Your system administrator must add you to the Creator Studio Users group. ### Procedimento 1. Select the question that you want to customize. When you select a question, it's highlighted on the form so you know what you're working on.Figura 6. Select a question to work on it 2. In the Configurations tab of the Question details panel, specify information about the question you added, such as a label for what the question is asking and whether it must be answered for the requester to submit the form. The details vary by question type. For example, if you add a Dropdown question, you must supply the options to choose from. Figura 7. Form question details 3. **Opcional:** Make the form's appearance change based on how users answer questions by adding [dynamic behavior](https://servicenow-prod.fluidtopics.net/ACNUyxL3haCoieGCkodBsQ#gloss-dynamic-behavior "A form for a catalog item can use dynamic behavior to automatically update based on how users answer a question. For example, if a user says they don't want lunch for an event they're attending, you can make a Meal preference field disappear.") to it on the Behaviors tab. For example, if a user says they want a T-shirt for an event they're attending, you can make a T-shirt size field required. Get the details on adding dynamic in [Make a form change based on responses in Creator Studio](https://servicenow-prod.fluidtopics.net/CgSO01EVPZhWO2ra0aYBwg "Make a form update based on how users answer a question using dynamic behavior. For example, if a user says they want a T-shirt for an event they're attending, you can make a T-shirt size field required."). 4. Automatically populate a question's answer based on the answer to another question on the form (record choices questions only) by selecting the Add auto-fill option. For example, a form can enable someone to select a user for the Choose the gift box recipient field, which retrieves its values from the User table. An additional Preferred name field can be automatically populated from the First name field of the User table selection, but then edited if someone prefers a nickname. The Add auto-fill option is available only if the form has a record choices question on it. You must also complete the following fields:{#crs-quick-add-questions-form__table_hfg_tk4_sdc__entry__2} | Field | Description | |-|-| | Select the dependent question | Question whose answer makes the current question automatically populate. | | Select the value field | Field in the source table for the record choices question that contains the value you want to use as the answer to the current question. You must select the edit icon (![]()), navigate to the field in the source table that contains the auto-populated answer, and select to Apply it. For more info on selecting fields in a table, see [Dot-walking to data in related tables](https://www.servicenow.com/docs/access?context=c_DotWalking&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US). | [Tabela 3. Details for auto-populating a question based on a record choices answer] {#crs-quick-add-questions-form__table_hfg_tk4_sdc} 5. Select Save and close when you finish modifying the question. 6. **Opcional:** Add another question by dragging the type of question you want from the Form elements panel onto the form, dropping it on the canvas where you'd like it. You can also add questions by selecting the add icon (+) that appears when you click on an existing question on the form. If you're adding a pre-configured Question set, you must select the question set from the modal that appears when you drag it onto the form. For a description of question types and how they're used, see [Available question types in Creator Studio](https://servicenow-prod.fluidtopics.net/1pwosmNt_x2z3X1aSYSklQ "Build apps using different types of questions on a form in Creator Studio."). 7. **Opcional:** Change a question type by selecting the question and then choosing the new question type in the Content type field of the Question details panel. Selecting a new type may introduce new values you must supply. Keep these specifications in mind as you create your questions: * You can't change an existing question into a question set. To include a question set on a form, you must newly add it to the form. * If you put two checkbox questions side-by-side on a form, they make a section. You can't add other types of questions to that section. {#crs-quick-add-questions-form__ul_w13_1d4_s2c} {#crs-quick-add-questions-form__crs-qs-add-qs-6-cmd} 8. Now, let's arrange the questions and images that you've added to the form. 1. From the Form elements panel, drag the layout option you like onto the form and drop it where you want it to appear, for example, a Divider line. Don't worry if you don't like the layout, just try another one by dragging it onto the form's canvas. 2. Revise the form layout you chose using the Section details or Question details panel (depending on the layout you're working on). You can do things like make text bold, add links, and so forth. Nota: To edit or delete a section, you must hover over the section name and then select Section to see the section details in the properties panel, as well as the delete icon.Figura 8. Selecting a section For more information, see [Layout options for forms in Creator Studio](https://servicenow-prod.fluidtopics.net/H9agZQwJ8FgobtfIdin83Q "Adjust how your form, which creates a catalog item, appears in Creator Studio using layout options."). 3. Select Save in the Section details/Question details panel when you're done revising the form's layout. {#crs-quick-add-questions-form__substeps_ljm_x4d_w1c} 9. **Opcional:** See how your form will look in various experiences by selecting the Preview button. You can see a preview of the how the current version of the form will appear in various experiences by selecting Portal (such as Employee Portal), Now Mobile, or Virtual Agent. You can fill in the form when previewing, but selecting the Submit button doesn't generate a task record. Figura 9. Preview a form 10. Publish the form when it's ready by selecting the Mark as ready button. Publishing forms makes them available as catalog items in the production instance after the associated app has been deployed. Figura 10. Mark as ready button ### Resultado Now that the form is available as a catalog item, we can use it to create an automated playbook. ## Quick start part 4: Add a playbook {#ariaid-title6} Add a playbook to create automation for your app, for example, to automatically assign a record to a manager for approval. ### Antes de Iniciar The form that you want to add automation to must already be published. Your system administrator must add you to the Creator Studio Users group. ### Procedimento 1. Select the Automations tab in the application header. 2. Select + Add automation in the navigation panel for the form you want to add a playbook to. Nota: If the form isn't yet published, you must first mark it as ready. For more information, see [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."). Figura 11. Add automation 3. Select the Create a playbook button. 4. Specify the playbook's General attributes in the Create playbook modal. {#crs-quick-add-playbook__table_eld_vcg_l1c__entry__2} | Field | Description | |-|-| | Playbook name | Descriptive name for the playbook you're creating. | | Description | Brief explanation of what the playbook does, for example, the end goal for the record type. | [Tabela 4. General playbook definition fields] {#crs-quick-add-playbook__table_eld_vcg_l1c} Figura 12. Create a playbook 5. Specify the Schedule for the playbook. 1. Select the type of Trigger that initiates the playbook. {#crs-quick-add-playbook__table_hp1_52g_l1c__entry__2} | Trigger | Description | |-|-| | Form submitted | Start running the playbook when a user submits the form you chose. | | Form updated | Start running the playbook when a user updates the form you chose. | | Form submitted or updated | Start running the playbook when a user submits or updates the form you chose. | [Tabela 5. Playbook trigger options] {#crs-quick-add-playbook__table_hp1_52g_l1c} Nota: You can't change an playbook's trigger type after you finish creating the playbook. Instead, create a new playbook with a different trigger. However, you can edit the trigger condition, such as making the playbook run conditionally based on a specific answer to a question. For more information, see [Edit the trigger for a playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/QesBXhvmAunqfAIn1mYLyA "Define the trigger for a playbook in Creator Studio to specify what makes the playbook start running."). 2. If you chose a trigger that includes a form being updated, specify how often that app should Run your playbook. The options are: * Once * For each unique change * Only if not currently running * For every update {#crs-quick-add-playbook__ul_e1b_4fg_l1c} 3. Specify the conditions that must be met for the playbook to begin running by selecting Add conditions. * If you want to trigger the playbook based on the value of a column in a table, select the [Field](https://servicenow-prod.fluidtopics.net/ACNUyxL3haCoieGCkodBsQ#gloss-field-creator-studio "A field in Creator Studio is a column on the app's underlying table. If you're using condition builder, a field is either a column on the table or a question from the form.") that you want to be the trigger, as well as its condition Operator and the specific trigger Value. For example, when a Start date is after the Date needed.{#crs-quick-add-playbook__crs-trigger-question-ph-1} * If you want to trigger the playbook based on the response from a form, select Questions as the trigger Field. Then select the question you want in the Question field, the condition Operator and the answer's Value. Figura 13. Question answer as trigger for an automation {#crs-quick-add-playbook__crs-trigger-question-ph-2} {#crs-quick-add-playbook__ul_fk1_r44_sbc} Add as many conditions as you need. For more information, see [Create a condition statement using the condition builder](https://www.servicenow.com/docs/access?context=create-cond-state-using-cond-build&version=australia&pubname=australia-platform-user-interface&ft:locale=en-US).{#crs-quick-add-playbook__crs-trigger-conditions-many} 4. Select Create. {#crs-quick-add-playbook__substeps_ldr_42g_l1c} ### Resultado Next, we'll add an activity to the playbook to define what the automation does. ## Quick start part 5: Add an activity and activate a playbook {#ariaid-title7} Add an activity to your playbook to define what the automation does. ### Antes de Iniciar Your system administrator must add you to the Creator Studio Users group. ### Por Que e Quando Desempenhar Esta Tarefa If you want to include an if/then statement to define circumstances for the [activity](https://servicenow-prod.fluidtopics.net/ACNUyxL3haCoieGCkodBsQ#gloss-activity-creator-workflow "Activities in a playbook complete automated tasks, such as obtaining approvals, assigning records, and sending emails."), add a decision. See [Add a decision to an app's playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/j3e5ni_HHcNsSXBj97Fbow "Add decisions, which are if/then conditions, to define branches, or different paths of an automation's playbook in Creator Studio.") for details. ### Procedimento 1. Ensure that you're viewing the playbook that you just created. 2. Select the add icon ![]() on the connector where you want to add an activity and choose the square Add an activity icon (![]()) in the menu that pops up. 3. Choose the type of activity that you want from the Activity library pop-up. Nota: In addition to the following standard activities, you may see some custom activities that your admin created. {#crs-quick-add-activity__table_gj1_3cg_n1c__entry__2} | Activity type | Description | |-|-| | Request approval | Ask someone for permission to accomplish a task. | | Assign to | Choose a person who should fulfill the task. | | Create task | Specify a process that must be done as part of the playbook. | | Send an email | Send an email to one or more people. You can specify images and enrich text for the email that gets sent automatically. | | Placeholder | Set an undefined activity to be specified later, or a more advanced activity such as an email notification, when an activity is completed. Placeholder activities don't have any logic assigned to them yet, and must be edited in Workflow Studio. Or, you can swap them out later for another type of activity in Creator Studio. | | Update submission | Update the value of the specified fields on the record that the form generates when a user submits it. | [Tabela 6. Types of activities] {#crs-quick-add-activity__table_gj1_3cg_n1c} Figura 14. Activity library for a playbook 4. Enter the basic details for the activity. {#crs-quick-add-activity__table_hb3_mfm_n1c__entry__2} | Field | Description | |-|-| | Label | Unique, user-facing name for your activity, which appears to agents and fulfillers while the playbook is running. | | Description | Optional details about what the activity accomplishes. | [Tabela 7. General activity details] {#crs-quick-add-activity__table_hb3_mfm_n1c} Figura 15. Activity details panel 5. Complete the details for the activity, using [Add activities to an app's playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/rlFOV7MsExaLAD22OxzL0g "Add activities to an app's playbook to specify what the automation does to the designated record type. An activity defines what actually happens when a playbook executes.") for information on how to finish creating the activity. 6. Select the Save and close button to finish setting up your activity. 7. Once the automation is done, activate it by selecting the Activate button. Activating a playbook makes it available to run when its related form is created or updated on your non-production, development instance. Figura 16. Activate the playbook ### Resultado The app is now ready to be deployed to production! Let's request deployment in the final step of this quick start guide. ## Quick Start part 6: Submit your app for deployment {#ariaid-title8} Now that you've made an app, it's time to submit it for review so admins can approve and deploy it. ### Antes de Iniciar Your system administrator must add you to the Creator Studio Users group. ### Procedimento 1. **Opcional:** Test the form by selecting the Try it button. You can then enter test values in the fields and select Submit to view the record your form submission created. 2. In the navigation panel, select Submit for review. Figura 17. Submit for review 3. Select Continue on the Submit app for review modal. 4. Now you need to choose which published forms are visible to users in the catalog. In the Ready for review section of the Review request forms modal, select which of the app's published forms that you want to be available after the app is deployed by selecting the Visible to others option. Figura 18. Review request forms for deployment 5. Select Continue when you're happy with the forms being deployed to production. 6. Next, you must decide which of the app's activated playbooks will run on production after the app is deployed. In the Review playbooks modal, select the Run on production option for each playbook that you want to run on records that the app generates. Nota: If you can't select a playbook, you need to go back to the Automations section of Creator Studio and activate it. If you need a refresher on that, check out [Activate a playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/SKdgWzxszZpuiR3It_BUcQ "Activating a playbook means that it will run when its related form is created or updated on your non-production, development instance. However, the app must still be deployed to production."). 7. Select Continue when you're happy with the playbooks being deployed to run on production. 8. Finally, make sure that all the release details for the published app are correct. {#crs-quick-submit-app__table_a5n_phs_m1c__entry__2}{#crs-quick-submit-app__cs-version-guidelines-ph} | Field | Description | |-|-| | New version | [Version number](https://servicenow-prod.fluidtopics.net/ACNUyxL3haCoieGCkodBsQ#gloss-version-number "A number assigned to the app that increases with each subsequent time it's deployed.") of the app you're requesting for deployment. Creator Studio automatically generates an updated version number, but you can change it. Follow your organization's versioning guidelines, or use the x.y.z format, where x = major update, y = minor update, and z = patch. | | [Release notes](https://servicenow-prod.fluidtopics.net/ACNUyxL3haCoieGCkodBsQ#gloss-release-notes "The information about what's included in each new version of the deployed app. Release notes help administrators to track what the changes are between app versions.") | Details on what's changed in this new version of the app, or a general description of what the app does if this is its first version. | [Tabela 8. Versioning options for deployment] {#crs-quick-submit-app__table_a5n_phs_m1c} Read more about this step of requesting deployment in [App versioning and release notes for Creator Studio apps](https://servicenow-prod.fluidtopics.net/98F0eC6a9z6nvt5YYdjR3A "Each deployed version of an app must have a version number and release notes, which helps administrators track app usage and changes."). Figura 19. App versioning info 9. Select Submit for review when everything is correct and ready for your admin to review and deploy. ### Resultado Congrats: Hooray! You've created your app, customized the form, added automation, and submitted it for review. After your admin reviews and deploys it, people will use your brand-new app to make requests.