Glossary

Terms are in alphabetical order.

Agent: A component that uses an AI model to resolve a request: it decides what to do, uses the tools you have connected to it and writes the answer. See Agents.

AI Assistant: The dashboard assistant you ask in your own words to build, test or fix a flow. See The AI Assistant.

API key: A key that lets another application call your flows. See API keys.

Batch Mode: A component setting that makes it process each item of a list and return all the results together. See Process lists.

Component: Each step of a flow. It does one thing, such as receiving a message, asking a model or sending an email. Each one has its own page in the Components section of this documentation.

Connection: The line that joins one component’s output to another’s input. Information passes through it from one step to the next.

Conversation: The messages exchanged with a flow that holds conversations, such as a chat assistant. You read them in Conversation Reg. See Conversations and evaluations.

Credential: The saved access to an external service, such as a model provider’s key or your Gmail account. You save it once and choose it in each component that needs it. See Credentials.

Deploy: Putting a version of the flow into production. Only one version is deployed at a time. See Versions and publishing.

Draft: What you have on the editor’s canvas. It is saved automatically and is what the playground runs, but it doesn’t affect the published version.

Environment: A named set of values you link to a flow, to use some in testing and others in production. See Environments.

Evaluation: An automatic review of a flow’s conversations against the criteria you define. See Conversations and evaluations.

Execution: Each time a flow runs. NappAI records what each component did and shows it in Executions Logs. See Execution logs.

Execution profile: A set of limits applied to a flow’s runs, such as how many times it can run or which components it can use. See Execution profiles.

Field: Each piece of data in a record, such as name or email. A component’s settings are also called fields.

Flow: An automation: the components and connections that together receive information and produce a result. Each flow lives in a project.

Folder: Groups projects on the Projects screen. My projects is the main folder.

List: Several records together, such as the rows of a spreadsheet or the unread emails. See How information travels.

Memories: The playground tab with the flow’s saved conversations.

Model: The artificial intelligence that understands and writes text. Each provider has its own component, such as OpenAI, Gemini or Anthropic.

Playground: The editor panel where you test the flow and see the answer and the details of each step. See Test the flow in the playground.

Project: The container of a flow, with its name and description. In this documentation, project and flow mean the same thing. See Projects.

Publish: Deploying a version so that other applications, schedules and connected channels use it. See Versions and publishing.

Record: A named set of data, such as a customer card or an order. Each piece of data is a field.

Role: What a person can do within an account: Admin, Builder, Operator or Viewer. See Roles and permissions.

Scheduler: The screen where you schedule a flow to run on its own on the dates and times you choose. See Scheduler.

Skill: Instructions and supporting files you save once and connect to the agents that need them, such as the tone you use with customers. See My Skills.

Storage: The space where the files your flows create and read are kept. See Your storage.

System Prompt: An agent’s fixed instructions: who it is, what it must do, what information it has and what it must not do. See The agent’s instructions.

Template: A ready-made flow from which you can create a new project. See Templates.

Token: The unit AI models use to count the text they read and write. Model usage is measured in tokens. See LLMs Uptake.

Tool: A component connected to an agent so it can use it when needed, such as looking up a spreadsheet or sending an email. See Tools.

Unplug: A component option that freezes its last result so it isn’t run again while you test the rest of the flow. See Configure a component.

User Prompt: The request an agent receives at each moment. By default it is {input}, what arrives through its Input connection.

Version: A named copy of the flow at a given moment. You can save several, deploy one and restore an earlier one. See Versions and publishing.

Voice agent: A flow that holds spoken conversations, by phone or from a website. See Voice agents.

Webhook: An address another application sends data to in order to start a flow. The Webhook Input component receives it. See Webhook Input.