--- sourceDocument: Australia Build workflows sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/build-workflows Release : - australia ft:locale : - en-US ft:publication_title : - Australia Build workflows ft:clusterId : - crworkflow bundleId : - crworkflow workflow : - Creator --- # Call Now Assist Skill step # Call Now Assist Skill step {#ariaid-title1} * Release version: Australia * * Updated March 12, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Call Now Assist Skill step The Call Now Assist Skill step enables ServiceNow users to run a published Otto for Creator skill within a custom action in Workflow Studio. It integrates with the Now Assist skill and the OneExtend Framework to process inputs and generate AI-powered outputs. This step is designed to streamline embedding AI capabilities into workflows by calling LLM-based skills directly from action steps. Show full answer Show less ## Key Features * **Availability and Roles:** Available as a Workflow Studio action step; requires the `actiondesigner` role and AI Skill Kit. * **Inputs:** * **Capability:** Reference to a OneExtend Capability record, allowing import of capability inputs into the action. * **Payload:** JSON-formatted string carrying data to send to the Now Assist skill. * **Skill Config:** Reference to a Now Assist Skill Config record controlling skill execution parameters. * **If Step Fails:** Option to either continue with the next step or trigger error evaluation. * **Outputs:** Multiple outputs are provided for integration in the workflow, including: * **Error:** Error messages if skill execution fails. * **Provider:** Name of the LLM provider used. * **Response:** Textual response generated by the skill (e.g., summaries or replies). * **Result:** JSON string representing the LLM-generated results. * **Status and Step Status:** Success or error indicators with detailed runtime information. ## Practical Example: Flow Summarization Skill This example demonstrates calling the Flow Summarize skill, which generates a text summary of a flow or subflow's function. Key action inputs correspond to the component's Sys ID and type (e.g., flow or subflow). The payload maps these inputs into a JSON object, and a matching Now Assist Skill Config is used. The output includes a descriptive summary of the specified flow, such as the "Change - Normal - Authorize" flow, detailing its approval process and conditions. Outputs like the Response and Result JSON can feed into subsequent workflow logic. The example shows no errors, successful status, and identifies the LLM provider used. ## Benefits for ServiceNow Customers * Facilitates integration of AI-driven skills into custom workflows and actions, enhancing automation. * Supports dynamic input mapping and flexible error handling to maintain workflow resilience. * Provides rich output data enabling downstream processing and actionable insights. * Empowers users with the `actiondesigner` role to extend Now Assist capabilities efficiently. Run a published ServiceNow Otto for Creator skill from an action. Configure the ServiceNow Otto for Creator skill inputs and skill outputs from the step inputs and step outputs. ## Roles and availability {#call-now-assist-skill-step__section_q5n_hhn_w2c} Available as an Workflow Studio action step. Users with the action_designer role can create a custom action with one or more action steps.{#call-now-assist-skill-step__available-action} AI Skill Kit requirements{#call-now-assist-skill-step__action-ih-subscription} : This step requires the AI Skill Kit. For more information, see [Exploring AI Skill Kit](https://www.servicenow.com/docs/access?context=exploring-now-assist-skill-kit&version=australia&pubname=australia-intelligent-experiences&ft:locale=en-US). Role requirements{#call-now-assist-skill-step__action-fd-roles} : This step requires roles granted by delegated development or assigned to the user. For more information, see [User access to Workflow Studio flows](https://servicenow-prod.fluidtopics.net/It9~lSDhYhBThAAusolhpg "Administrators can grant users access to Workflow Studio flows by assigning delegated development permissions or directly assigning a user role. Administrators can also specify which features and content a user can access based on user roles. Application developers can access Workflow Studio functionality through APIs for flows, subflows, and actions."). ## Inputs {#call-now-assist-skill-step__section-inputs} Provide a value for each input that your action needs. To add dynamic values, you can also drag and drop pills from the Data panel or select them from the pill picker.{#call-now-assist-skill-step__inputs-description} Capability : Data type: Reference Reference to a OneExtend Capability \[sys_one_extend_capability\] record. When you select a capability record, the system gives you the option to import the capability inputs and create matching action inputs for them. Note: Some capability inputs use reserved words such as sys_id that can't be used as action input names. Review any inputs that are created by the import process and verify that the action input names are valid. Payload : Data type: String JSON-formatted string containing the payload to send to the Now Assist skill and the OneExtend Framework for processing. Skill Config : Data type: Reference Reference to a Now Assist Skill Config \[sn_nowassist_skill_config\] record. If this step fails : Data type: Choice Option to continue running the next step or go to error evaluation. To use the step status code or message for a custom action error condition, see [Action error evaluation](https://servicenow-prod.fluidtopics.net/TJkLnvv_cE34AFa4p0LuVQ "Enable actions to catch step failures and continue running. Identify when specific error conditions occur and return your own action status code, status message, and error state."). ## Outputs {#call-now-assist-skill-step__section-outputs} These outputs appear in the Data panel. You can use them as inputs elsewhere in your action.{#call-now-assist-skill-step__outputs-description} Error : Data type: String Error message produced by the skill. This output is empty when the skill successfully runs the Now Assist skill request. Provider : Name of the LLM provider that fulfilled the Now Assist skill request. Response : Text response generated by the LLM such as a summary or a reply to a conversation. Result : JSON-formatted string containing the results generated by the LLM to the input payload. Status : Status of the call to the provider. Step Status : Data type: Object Object data pill containing runtime details about the step. Each step in an action returns a Step Status. Step Status Code : Data type: Integer Integer data pill indicating whether the step produced an error. A step returns a value of 1 when it produces an error for any reason. For example, a step can produce an error if it is missing mandatory input data or returns output in the wrong data type. A step returns a value of 0 when it runs successfully. You cannot customize these codes. * Success \[0\]: The step succeeded. * Error \[1\]: The step produced an error. {#call-now-assist-skill-step__ul_obs_2r1_j1c} Step Status Message : Data type: String String data pill containing the error message produced by the step or system operation. You cannot customize the step status message. ## Call the Flow Summarization skill {#call-now-assist-skill-step__example_hpq_5ln_w2c} This example action calls the Flow Summarize skill, which provides a text summary of what a flow or subflow does. The Flow Summarization skill has two skill inputs. * asset_sys_id. This input contains the Sys ID of the component to be summarized. * asset_type. This input contains the type of component to summarize. {#call-now-assist-skill-step__ul_rvm_q3m_y2c} To support the two skill inputs, this example action has two matching action inputs. * Flow to summarize. This input contains the Sys ID of the component to be summarized. * Type. This input contains the type of component to summarize such as flow, subflow, or action. {#call-now-assist-skill-step__ul_vsn_x3m_y2c} Note: An action can't have an input with the name sys_id, because that name is a reserved word. We can test this action by providing these example input values. Capability : This example uses the Flow Summarization OneExtend Capability record. Payload : This example uses a JSON object to map action input values to skill values. In this example, we provide the Sys ID of the Change - Normal - Authorize flow and the type of flow. Skill Config : This example uses the Flow Summarization Now Assist Skill Config record. Here are the example output values produced by the Flow summarization skill. Error output : This example doesn't produce an error output. Provider output : This example uses the Now LLM provider. Response output : This example uses the Flow Summarization skill to generate a summary for the Change - Normal - Authorize flow. Typically, you would use this Response output as an input for another action or flow logic. This flow, named "Change - Normal - Authorize", is designed to process a Change Request that uses the Normal Change Model and is in the state of Authorize, while ensuring it is not on hold. The flow begins by checking if the assignment group manager has already approved the change request. If not, it applies a Change Approval Policy, specifically for risk approvals. The flow then evaluates whether the approval process was skipped, rejected, or approved. If skipped, it does nothing. If rejected, it sends an email notification to relevant parties. If approved, it updates the change request record to mark it as approved. In parallel, the flow waits for the change request to be on hold or inactive, and then disregards any change request approvals. It also evaluates the change model again. The flow ends after completing these tasks. Result output : This example returns a JSON object containing the both the response and the flow elements used to generate the response. Status output : This example returns a success output value.