---
title: Add activities to an app's playbook in Creator Studio
description: 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.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/application-development/creator-studio/creator-studio-add-activities-automation.html
release: australia
product: Creator Studio
classification: creator-studio
topic_type: task
last_updated: "2026-03-12"
reading_time_minutes: 6
breadcrumb: [Automation in apps, Build apps, Creator Studio, Building no-code applications, Developing your application, Building applications]
---
# Add activities to an app's playbook in Creator Studio
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.
## Before you begin
To add [activities](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/creator-studio-glossary.md) to a playbook, you must be given permission to work on the app.
## About this task
The activities that you can add to a playbook are limited by your administrator to ensure you use the correct ones for your organization. Your admin may have created some custom activities for you to choose from, or hidden some standard activities.
## Procedure
1. Go to **All** > **App Engine** > **Creator Studio** to see all the apps on the Creator Studio home page.
2. Open the app that contains the playbook you want to add an activity to.
3. Select the form that contains the playbook that you want to add an activity to.
4. Select the automation that contains the playbook that you want to add an activity to.
**Note:** If your app has a lot of forms and automations, you can use the search box in the navigation panel to search for a specific automation.
\[Omitted image "crs-auto-copy-nav.png"\] Alt text: Select the automation in the navigation panel
5. Select the add icon \[Omitted image "cs-add-icon.png"\] Alt text: on the connector where you want to add an activity and choose the square **Add an activity** icon \(\[Omitted image "cs-add-activity-icon.png"\] Alt text:\) in the menu that pops up.
|
View
|
Steps
|
|---|
|
Diagram
|
1. Select the **+** icon in the stage.
2. In the mini-picker, select the square icon \[Omitted image "cs-add-activity-icon.png"\] Alt text: to add an activity.
|
|
Board
|
Select **+ Add activity**.
|
6. Choose the type of activity that you want from the Activity library pop-up.
**Note:** In addition to the following standard activities, you may see some custom activities that your admin created.
|
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.
|
\[Omitted image "crs-add-activity-more.png"\] Alt text: Select which type of activity to add
Your new activity and its Activity properties panel appear, where you define what the activity is.
7. Enter the basic details for the activity.
|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.|
\[Omitted image "cs-assign-to-properties.png"\] Alt text: Activity details panel
8. If needed, specify the approver or assignee in the **Select an approver** or **Select an assignee** fields.
Approvers and assignees are the person or people who must approve the task, or who the task gets assigned to. The options are:
- **Group**: Enter one or more user groups in the field that appears. For example, `App engine Admins`.
- **Specific person**: Enter the person's name as it appears on the ServiceNow AI Platform. If you entered a group, you can select only from users in the specified group.
- **Requester's manager**: \(Request approval activities only\) Automatically routes the approval to the manager of the person who's making the request.
9. Enter details for specific types of activities.
1. For Request approval activities only, specify the **Approval type**.
Approval type defines whether a single approver is needed or if everyone must approve the request. The options are:
- **Anyone approves**: Only one of the specified approvers must approve the request.
- **All approve**: Every one of the specified approvers must approve the request.
If you select this option and specified a group, all members of the group must approve the request.
2. For Create task activities, specify the **Priority**.
The options are:
- **Critical**
- **High**
- **Moderate**
- **Low**
- **Planning**
3. For Send an email activities, specify the recipients and contents of the email.
- Enter the name \(for ServiceNow AI Platform users\) or email address for people who should receive the email in the **To** and **Cc** fields.
Select the **Requester** option for the **To** or **Cc** fields to include the person who made the request in the email's recipients.
- Enter the email's subject in the **Subject** field.
- Enter the body of the email in the textbox. Select the additional toolbar buttons icon \[Omitted image "cs-more-actions-icon.png"\] to display more formatting options. For example, you can add images, tables, and links to the email.
4. For Update submission activities, select the fields that the activity should update on the submitted form's record.
Choose one or more of the following fields to be automatically updated and specify the field value:
- **Short description**: Then enter a value for the updated short description.
- **Description**: Then enter a value for the updated description.
- **State**: Then select the updated record state. For example, **Open**.
- **Priority**: Then select the updated value. For example, **4 - Low**.
For example, you can add an **Update submission** activity that automatically closes a record if a previous approval activity is declined.
10. Select at what point the activity should start running in the **When to start** field of the Conditions section.
The options are:
- **When playbook starts**: The approval request runs when the trigger occurs, which is the form's record being created or updated.
- **After specific activity**: The approval request runs after one or more activities run, which you must specify in the **Starts after** field. You can select only activities that occur sequentially before the activity you're working on.
**Note:** This option isn't available for the first activity in a playbook.
11. Define any extra conditions that must be met for the activity to happen by selecting **+ Add conditions**.
Use the condition builder that appears to specify any other things that must happen for the activity to run. For more information, see [Create a condition statement using the condition builder](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/create-cond-state-using-cond-build.md).
You can use the answer from the associated form to power the activity. For example, you can specify that if someone answers Yes to the question "Do you eat meat?" the Assign to activity is assigned to the Meat department to fulfill the gift box. To use the response from a form as a condition, do the following:
1. Choose **Questions** in the **Field** field.
2. Select the form's question to use as the condition from the **Question** field.
3. Specify the condition **Operator** and the answer's **Value**.
4. Select **Apply** when you're done defining the condition.
12. Select the **Save and close** button to finish setting up your activity.
## What to do next
Continue adding activities and decisions, as well as connectors and parallel processes if needed, to finish creating your playbook. For more information on decisions, see [Add a decision to an app's playbook in Creator Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/creator-studio-add-decision-automation.md).
**Parent Topic:**[Working with automation in Creator Studio](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/creator-studio-working-with-automations.md)