---
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


---

# Workflow for custom activity creation

# Steps to create a custom activity in 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) 1 min. de leitura

There are multiple steps to add custom activities for use in Creator Studio automations.

## Adding a completely new activity {#creator-studio-custom-activity-workflow__section_imk_xr4_xcc}

The steps to create a custom activity for a playbook are as follows:

1. Create the flow, subflow, or action: An admin or someone with the correct role must first create the flow, subflow, or action in Workflow Studio. For more information, see [General guidelines for Workflow Studio flows, subflows, and actions](https://www.servicenow.com/docs/access?context=design-considerations-consolidated&version=australia&pubname=australia-build-workflows&ft:locale=en-US).
2. Define the activity: An admin then defines the activity by adding it to the Activity Definition table and assigning the flow/subflow/action to a playbook activity. This step is also when the admin specifies which inputs can be made available as fields in the activity settings in Creator Studio playbooks. For more information, see [Activity definitions](https://www.servicenow.com/docs/access?context=activity-definitions&version=australia&pubname=australia-build-workflows&ft:locale=en-US) and [Create an activity definition](https://www.servicenow.com/docs/access?context=create-activity-definition&version=australia&pubname=australia-build-workflows&ft:locale=en-US).  
   Nota:  
   If an activity definition already exists for the activity you want, you can skip this step.
3. Make the activity available in Creator Studio: An App Engine admin adds the activity to the Creator Studio Activities table. For more information, see [Make a custom activity available for playbooks in Creator Studio](https://servicenow-prod.fluidtopics.net/qwRBYFZk~zFMCs8I1~opIQ "You must add custom activities to the Creator Studio Activities table [sn_creatorstudio_activity] before users can add them to playbooks when building apps.").
{#creator-studio-custom-activity-workflow__ol_fw3_ll4_xcc}

## Making existing activities and playbooks available in Creator Studio {#creator-studio-custom-activity-workflow__section_irn_yr4_xcc}

Admins can make existing flows, subflows, and actions available in Creator Studio by defining the activity and then adding it to the Creator Studio Activities table (the preceding steps 2 and 3).

Admins can also make existing playbook activities available in Creator Studio by adding them to the Creator Studio Activities table (the preceding step 3).  
Nota:  
Creator Studio admins can see the Activity Definitions \[sn_pd_activity_definition\] table by default, which also enables them to administer processes in Workflow Studio.