---
title: Create spoke and build actions using the spoke generation skill in ServiceNow Otto
description: Automate an integration and generate reusable actions by providing the required third-party API documentation snippet as an input.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/build-workflows/workflow-studio/create-spk-now-spk-gen.html
release: australia
product: Workflow Studio
classification: workflow-studio
topic_type: task
last_updated: "2026-08-04"
reading_time_minutes: 3
breadcrumb: [Use ServiceNow Otto to create spokes and build actions, Building spokes using Spoke Generator, Workflow Studio, Build workflows]
---

# Create spoke and build actions using the spoke generation skill in ServiceNow Otto

Automate an integration and generate reusable actions by providing the required third-party API documentation snippet as an input.

## Before you begin

**Important:** This generative AI skill is turned on by default. The skill will be automatically available to appropriate role users for the application. For more information, see [AI agents, skills, and agentic workflows on by default](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/intelligent-experiences/now-assist-skills-on-by-default.md).

-   Role required: admin
-   Create the required action categories for your integration in the Action Category \[sys\_hub\_category\] table.
-   Confirm that ServiceNow Integration Hub Professional Pack Installer \(com.glide.hub.integrations.professional\) is installed and the license is entitled.

## Procedure

1.  Navigate to **All** > **Process Automation** > **Workflow Studio**.

2.  Click **New** > **Spoke**.

3.  On the Spoke Info screen, specify if you want to create the spoke in a new scope or an existing scope.

    1.  If you choose to create the spoke in a new scope, select an image as the logo for your integration and fill in the fields.

        Here, we will go through an integration with LearnOrbit as an example.

        |Field|Description|
        |-----|-----------|
        |Spoke name|Name to identify the custom spoke.|
        |Description|Description about the custom spoke.|

        \[Omitted image "build-spoke-now-assist.png"\] Alt text: Spoke generator window.

        **Note:**

        The value of **App scope name** is the format: `x_<company-code>_<spoke-name>_<spoke>`. By default, the &lt;company-code&gt; is, `snc`. You can configure the company code by configuring **Value** of the system property, **glide.appcreator.company.code**.\[Omitted image "spoke-gen-sys-property.png"\] Alt text: Configuring Value of glide.appcreator.company.code.

        This configured value is used when the value **App scope name** is generated.\[Omitted image "spoke-gen-app-scope.png"\] Alt text: Configured value of App scope name.

    2.  If you choose to create the spoke in an existing scope, select an image as the logo for your integration and fill in the fields.

        Here, we will go through an integration with LearnOrbit as an example.

        |Field|Description|
        |-----|-----------|
        |Application name|An existing application name or scope.|
        |App scope name|Scope name that is auto-populated based in the selected **Application name**.|
        |Description|Description about the custom spoke.|

4.  Click **Continue**.

5.  On the Build Info screen, select the method using which you want to build your spoke.

6.  Select **With AI** and click **Continue** to generate reusable actions by providing the required third-party API documentation snippet.

    \[Omitted image "now-assist-spk-gen2.png"\] Alt text: Create spoke using Now Assist.

7.  On the Generate action screen, paste the required content from the API documentation in **AI Context**.

    In this example, we will copy the documentation related to the enrollUser action and paste it in **AI Context**.

    **Note:** Ensure that you paste the documentation related to only one action at a time.

    \[Omitted image "build-spoke-action-api-docs.png"\] Alt text: Create spoke action window.

8.  Click **Generate preview**.

    The action preview is generated. Details of the action properties, inputs, outputs, and steps are displayed.

    \[Omitted image "build-action-outcome-preview.png"\] Alt text: Action generation outcome preview.

9.  If you want to modify the generated action, modify the provided content in **AI Context** accordingly and click **Regenerate preview**.

    If there are any missing fields in the content provided for **AI Context**, an error message is displayed.

    \[Omitted image "build-spoke-action-error.png"\] Alt text: Action generation error sample.

10. Click **Continue**.

11. On the Select connection and category screen, for **Connection and credential alias**, click **Create new**.

12. On the Create new connection and credential alias screen, fill in the fields and provide the alias information.

    |Field|Description|
    |-----|-----------|
    |Connection &amp; Credential name|Name to identify the connection and credential alias record.|
    |Configuration Template for authentication|Required authentication mechanism for this integration. Ensure that the authentication mechanism is compatible with the third-party application.|

    \[Omitted image "build-spoke-alias.png"\] Alt text: Connection and credential alias window.

13. Click **Create alias and continue**.

14. On the Configure connection and credential alias screen, fill in the fields to configure the alias.

    |Field|Description|
    |-----|-----------|
    |Connection Information|
    |Connection Name|Name to identify the connection record.|
    |Connection URL|Base URL to connect to the third-party instance or server.|
    |Credential Information|
    |Based on the configuration template you had selected, the relevant credential fields are displayed. Provide the required values to configure the credential record.|

    If you want configure the alias record later, click **Do it later**.

15. Click **Submit**.

    The connection alias record is created.

16. On the Select connection and category, select the required action category.

17. Click **Publish**.

    **Note:** If there are any missing fields, you can't publish the action. Instead you can save the action as a draft by clicking, **Save action as draft**.

    The action is created. You can create another spoke action or navigate to the Spokes page.

    If you have saved action as a draft, you can access these draft actions in the spoke details page under **Actions** &gt; **Draft**.