Glossary

Documentation Index

Fetch the complete documentation index at: https://docs.cogniagent.ai/llms.txt

Use this file to discover all available pages before exploring further.

A reference guide to the terminology used throughout CogniAgent. If you’re new to workflow automation or AI agents, start here.

​

Core Concepts

​

Application

A container that holds one or more workflows. Think of it as a project folder. Applications let you organize related automations together and manage them as a unit. Example: An “Order Management” application might contain workflows for order confirmation, shipping updates, and returns processing.

​

Workflow

A sequence of connected nodes that automates a process. Workflows start with a trigger and include actions and logic nodes that execute in order. Example: A workflow that starts when a customer submits a form, uses AI to categorize the request, and routes it to the appropriate team.

​

Node

A single step in a workflow. Nodes are the building blocks you connect together. There are three types:

• Triggers — Start the workflow
• Actions — Perform tasks
• Logic — Control the flow

​

Execution

A single run of a workflow. When a trigger fires, it creates an execution that moves through each node in sequence. You can view execution history to see what happened.

---

​

Trigger Types

​

Start Trigger

The simplest trigger. Runs the workflow when you click the Run button manually. Good for testing or workflows you want to run on-demand.

​

Scheduled Trigger

Runs the workflow on a time-based schedule. Can be set to hourly, daily, weekly, or custom intervals using cron expressions. Example: Run a report every Monday at 9 AM.

​

App Trigger

Starts the workflow when something happens in a connected application. Requires an integration to be set up first. Example: When a new row is added to a Google Sheet, when an email arrives in Gmail.

​

Webhook

Starts the workflow when an external system sends an HTTP request to a unique URL. Useful for connecting with systems that support webhooks. Example: When Stripe sends a payment notification, when a form service submits data.

​

AI Trigger

Uses AI to monitor a condition and triggers when that condition is met. More flexible than rule-based triggers. Example: Trigger when an email appears urgent based on its content, not just keywords.

---

​

Action Types

​

Ask AI

Sends a prompt to an AI model and returns the response. Use this for text generation, summarization, classification, or any task where you need AI intelligence.

​

App Action

Performs an action in a connected application. Requires an integration to be set up. Example: Send an email via Gmail, create a row in Google Sheets, post a message to Slack.

​

Call AI Agent

Invokes an autonomous AI agent that can perform multi-step tasks independently. Agents can use tools, make decisions, and complete complex objectives.

​

Execute Code

Runs custom JavaScript or Python code. For advanced users who need logic that isn’t available through standard nodes.

​

HTTP Request

Makes a web request to any URL. Use this to integrate with APIs that don’t have a dedicated CogniAgent integration.

​

Update Variable

Sets or updates a variable value that persists across the workflow execution or the entire application.

​

Read File

Extracts content from uploaded files. Supports PDFs, documents, spreadsheets, and images.

---

​

Logic Types

​

Condition

Branches the workflow based on a true/false condition. If the condition is true, one path executes. If false, another path executes. Example: If order total is greater than $100, apply free shipping. Otherwise, calculate shipping cost.

​

Multi-Condition

Branches the workflow based on multiple conditions. Like a condition node but with more than two paths. Example: Route support tickets to different teams based on category: billing, technical, or general.

​

Loop

Repeats a set of nodes for each item in a list. Useful for processing multiple records. Example: For each row in a spreadsheet, send a personalized email.

​

Pause

Stops the workflow for a specified duration before continuing. Example: Wait 24 hours before sending a follow-up email.

​

Wait and Combine

Waits for multiple parallel branches to complete before continuing. Used when you’ve split a workflow and need to merge the results.

---

​

Data Concepts

​

Variable

A named value that stores data during workflow execution. Variables can be set by nodes and referenced by other nodes. Types:

• Runtime variables — Exist only during a single execution
• Application variables — Persist across executions

​

Variable Reference

The syntax for accessing data from other nodes: {{node_name.field_name}} Example: {{ask_ai_1.response}} gets the response from an Ask AI node named “ask_ai_1”.

---

​

Integration Concepts

​

Integration

A connection to an external service (Gmail, Slack, Shopify, etc.). Integrations require authentication and enable App Triggers and App Actions. CogniAgent supports 2,700+ integrations through Pipedream and built-in connectors. Learn more →

​

Pipedream

CogniAgent’s primary integration platform, providing access to 2,700+ pre-built app connections. Handles authentication, rate limiting, and API updates automatically.

​

MCP (Model Context Protocol)

A standard protocol for connecting AI models to external tools and data sources. CogniAgent both uses MCP (agents can call MCP-exposed tools) and exposes an MCP server so AI assistants like Claude can build and operate flows on your behalf. See the MCP server guide.

---

​

AI Concepts

​

AI Agent

An autonomous AI system that can perform multi-step tasks, use tools, and make decisions. Unlike simple AI prompts, agents can take actions and adapt based on results.

​

Human-in-the-Loop

A workflow pattern where automation pauses to get human input or approval before continuing. Ensures humans stay in control of important decisions. Example: AI drafts a response, but a human reviews and approves before sending.

​

Prompt

The text instruction sent to an AI model. Good prompts are clear, specific, and include relevant context.

---

​

Conversation Flow Concepts

​

Conversation Flow

CogniAgent’s visual canvas for building multi-agent conversational AI. A flow contains one Start node, one or more actors (AI agents), and routing edges between them. Learn more →

​

Actor

An AI agent inside a conversation flow. Each actor has a name, an icon, a system prompt (context + instructions), a model, capabilities (knowledge bases, integrations, custom tools), and a focus mode. Learn more →

​

Start Node

The single entry point of a conversation flow. Owns the channel configuration (Widget, Gmail, Slack, Teams, Phone). Every flow has exactly one.

​

Routing Edge

A connection between two actors. Each edge carries an activation prompt — a plain-language description of when this route should fire. The platform reads it during routing decisions and auto-generates a short label. Learn more →

​

Global Context

Shared knowledge written once on the flow and inherited by every actor that opts in. Use it to write your company introduction or product blurb once, not on every agent. Learn more →

​

Focus Mode

How strictly an actor sticks to its job when users change topics mid-conversation. One of Auto, Flexible, Persistent, or Strict. Learn more →

​

Definition of Done

A short rule on an actor describing when its job is complete. Triggers a handoff to the next agent.

​

Execution Mode

Whether a flow waits for inbound messages (Responder) or starts conversations itself (Initiator). Learn more →

​

Channel

A communication surface where conversations happen — Widget, Gmail, Outlook, Slack, Teams, Phone, SMS, WhatsApp. Configured on the Start node. Learn more →

---

​

Architecture Concepts

​

EDAA

Event-Driven Agentic Architecture — CogniAgent’s workflow orchestration system. EDAA manages how workflows execute, coordinates between different services, and handles actions triggered by conversations.

---

​

Execution States