Make a custom activity available for playbooks in Creator Studio
You must add custom activities to the Creator Studio Activities table [sn_creatorstudio_activity] before users can add them to playbooks when building apps.
About this task
You may want to create custom activities for complex or company-specific workflows. For example:
- The standard Request approval activity has a Requester's manager option, but you may need a Department manager instead.
- You may need an approval or flow with more complex decision logic than is easily built in the Creator Studio automation. You could use Workflow Studio to build that flow, and then create a custom action that calls it.
- You may want more notification types than the standard Email notification activity. You could create a flow that sends a notification to a MS Teams integration, and create an activity that calls that flow.
Before you begin
The following steps must be completed before you can make a custom activity available in Creator Studio:
- 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.
- 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 and Create an activity definition.Note:If an activity definition already exists for the activity you want, you can skip this step.
Role required: admin or app_engine_admin
Procedure
Result
The new activity appears in the activity picker in Creator Studio.