Skip to content
Nappai Documentation

Stored Skill

This component allows you to use a skill that you have previously created and saved in your personal skill library. Instead of building a workflow from scratch every time, you can simply select an existing skill to perform specific tasks. Think of this component as a container that holds a ready-to-use logic, which can be plugged into your automated workflows to save time and ensure consistency.

How it Works

When you place this component in your dashboard, it acts as a bridge to your personal library of skills. It does not contain its own internal logic; instead, it retrieves the logic of the skill you choose from your stored collection.

Here is the simple process of how it operates:

  1. Selection: You choose a specific skill from a dropdown menu. This skill has already been defined and saved by you or someone else in your library.
  2. Execution: Once the skill is selected, the system takes the data you provide (the input) and passes it to the stored skill’s logic.
  3. Output: The skill processes the input and returns the result, which can then be used by subsequent steps in your workflow.

This component is designed to be “passive” in terms of configuration—it simply connects your data to the pre-built logic of the selected skill. You do not need to edit the code of the skill itself within this node; you only need to ensure the correct skill is selected and that the input data matches what the skill expects.

Connection & Credentials

This component does not require any external API keys or specific credential configurations for standard operation, as it interacts with your local or personal skill library which is managed via the Nappai dashboard.

Operations

This component does not offer multiple distinct operations. It functions as a single node that executes the chosen stored skill.

Inputs

The following fields are available to configure this component.

  • Skill: Select a skill from your library.
    • Visible in: All operations

You must select a skill from your library to use this component. If you have not created any skills yet, you can go to the Mis Skills section in your dashboard to create or edit them. Once a skill is selected, its internal requirements will determine what other data (inputs) might be passed to it from previous nodes in your workflow.

Outputs

This component produces the result generated by the executed skill.

Output Data Example (JSON)

The output depends entirely on the skill you selected. Below is a generic example of what the output might look like if the skill returns a structured result: json { “status”: “success”, “result”: “Here is the processed data or text returned by your stored skill.” }

If the skill returns a complex object, you may see nested fields in the output. These values can be mapped to other components in your workflow for further processing, such as sending an email or saving to a database.

Connectivity

This component is typically connected in the middle or end of a workflow chain.

  • Incoming Connections: You should connect previous components (such as “Input” nodes, “Data Fetcher” nodes, or other “Skills”) to this component. The outputs of these preceding nodes will serve as the input_text or parameters for the stored skill.
  • Outgoing Connections: Connect the output of this component to nodes that need to use the result, such as “Email Sender,” “Database Writer,” “Conditional Logic,” or “Display/Visualization” nodes.

Usage Example

Imagine you have created a skill named “Format Customer Review” in your library. This skill takes raw text and formats it into a professional summary.

  1. You drag the Stored Skill component into your workflow.
  2. In the Skill dropdown, you select “Format Customer Review”.
  3. You connect a “Get Email” component (which extracts the text of a customer email) to this Stored Skill node.
  4. The workflow passes the raw email text into the skill.
  5. The skill processes the text and outputs the formatted summary.
  6. You then connect this Stored Skill output to an “Send Notification” component to alert the support team.

Important Notes

  • Skill Availability: Ensure that the skill you select actually exists in your library. If a skill is deleted from your library, this node may fail to execute.
  • Input Compatibility: The data connected to this node must match the expected input type of the selected skill. If the skill expects a string but receives a number, the execution may fail.

Tips and Best Practices

  • Organize Your Library: Keep your personal skill library well-organized. Naming skills clearly helps you find the right one quickly in the dropdown menu.
  • Test Skills Individually: Before connecting a stored skill to a complex workflow, test it individually to ensure it behaves as expected with sample data.
  • Reusability: This component is designed for reuse. Once you define a logic in a skill, you can use this component multiple times in different workflows to apply that same logic.

Security Considerations

Since this component accesses your personal skill library, ensure that you only select skills from trusted sources or those you have created yourself. If you are working in a shared team environment, be aware that skills selected from a shared library may have access permissions or restrictions defined by the creator. Always verify that the selected skill handles data in compliance with your organization’s security policies.