Entelligence leverages artificial intelligence to provide insights, recommendations, and predictive analytics for businesses seeking data-driven decision-making capabilities
Entelligence leverages artificial intelligence to provide insights, recommendations, and predictive analytics for businesses seeking data-driven decision-making capabilities On Nagent, Entelligence is exposed as a fully-configurable artificial intelligence integration that any agent can call — 2 actions, and no authentication authentication. No code is required to wire Entelligence into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Entelligence to automate the kinds of tasks artificial intelligence teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Entelligence into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Entelligence, with input parameters and output schema. Drop these into any step of an agent built in Helix.
ENTELLIGENCE_ADD_A_NEW_REPOSITORYAdd a GitHub repository to Entelligence for code analysis and AI-powered insights. The repository will be analyzed asynchronously. After adding, you can use the 'interact_with_the_repository_agent' action to ask questions about the codebase. Returns a repo_uuid that can be used to track the repository.
Input parameters
The full GitHub repository URL (e.g., 'https://github.com/owner/repo'). Must be a valid, accessible GitHub repository URL.
A display name for the repository (e.g., 'my-react-app'). This can be different from the actual repository name.
The branch to analyze (e.g., 'main', 'master', 'develop'). If not specified, the default branch will be used.
Set to true for public repositories, false for private repositories. For private repos, you must also provide an AccessToken.
UUID of the user adding the repository. If not provided, the system will generate one.
Set to true to ingest and analyze pull requests from the repository. Defaults to false.
Set to true to ingest and analyze documentation files from the repository. Defaults to false.
GitHub personal access token for private repositories. Required when IsPublic is false.
URL of an existing vector database to use for this repository. If not provided, a new vector DB will be created.
Set to true to ingest and analyze issues from the repository. Defaults to false.
Set to true if this repository is a merged/combined repository from multiple sources. Defaults to false.
URL to external documentation for this repository (e.g., 'https://docs.example.com'). Useful for linking to official docs.
UUID of the organization this repository belongs to. Used for grouping repositories under an organization.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ENTELLIGENCE_INTERACT_WITH_THE_REPOSITORY_AGENTAsk questions about a codebase using Entelligence's AI-powered Repository Agent. Requires a repository to be added first using the add_a_new_repository action. The agent can answer questions about code architecture, functionality, dependencies, and help with understanding the repository structure.
Input parameters
Conversation history as a list of message objects with 'role' ('user' or 'assistant') and 'content' keys. Use an empty list \[\] for the first question in a conversation
The question to ask the Repository Agent about the codebase, e.g., 'What is the main purpose of this repository?' or 'Explain the authentication flow'
Display name or identifier of the user. Optional, used for personalization
The repository UUID (repo_uuid) returned by the add_a_new_repository action. This identifies which repository to query
Enable advanced agent features for more sophisticated code analysis. Defaults to True. Set to False for faster, simpler responses
GitHub username of the person asking the question. Optional, used for personalization and access control
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 47 agents privately built on Nagent that already use Entelligence.
Build on Nagent
Connect Entelligence to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Entelligence, and click "Connect Now." You'll authenticate with no authentication (it’s public) — Nagent handles credential storage and refresh automatically. Once connected, Entelligence is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Entelligence is connected, you configure its 2 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Entelligence steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Entelligence event fires, the agent kicks off automatically.
Every Entelligence action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Entelligence ships with 2 pre-built artificial intelligence actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Entelligence together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Entelligence-based workflows tailored to your business.