TextCortex

TextCortex connects company knowledge with configurable AI agents and visual workflows. Teams can ask questions across selected documents, create an agent for a recurring role and turn a useful process into a Flow. Its current product combines knowledge retrieval, tool use and scheduled work, with controls that need to be configured around the underlying sources.

Ask questions across company knowledge

The company-knowledge product connects documents, wikis and supported tools so agents can answer with source context. Knowledge bases group material for a task or department. The User Handbook explains that retrieval selects relevant sections for a question rather than reading every stored document into each answer.

Supported material includes PDFs, Word documents, presentations and spreadsheets, with integrations such as Google Drive and OneDrive. This suits questions that depend on internal policies, procedures or project records. Open the cited source before treating a response as an agreed decision, especially when several documents describe different versions of the same process.

Configure agents for a defined role

The official website describes a visual agent builder with selected knowledge and tools such as web search and data analysis. Agent instructions define the role, required behavior and output. Agents can also be invoked through supported work surfaces such as Slack and Teams, or scheduled for recurring tasks.

A support-operations agent, for example, could use approved troubleshooting guides to prepare an internal answer brief. Specify which knowledge it should consult, what counts as insufficient evidence and which reviewer owns the result. Connecting documents supplies context; it does not make every generated interpretation correct.

Build a repeatable process with Flows

Flows uses a visual, node-based editor for multi-step work. Nodes can fetch information, retrieve knowledge, reshape records, run an agent and display, send or store results. Mapping converts structured records into text, while conditions and table operations help control what reaches the AI step.

The component reference documents typed connections: text, structured objects, tables, files and images must connect to compatible inputs. This makes data preparation part of the workflow rather than leaving an agent to interpret an arbitrary raw response.

Who it suits and an internal-policy workflow

TextCortex suits operations, support and knowledge-management teams that can maintain approved sources and define repeatable review steps. For an internal policy question, create a knowledge base containing the current policy and related procedures. Build a Flow from Text Input through Retrieve from Knowledge Base, then combine the question and retrieved context in a Prompt and pass it to an Agent.

Send the first results to Text Output for inspection. Follow the first-Flow guide to inspect node outputs and required fields. Test a clear question, a missing policy and conflicting versions. Add recurring delivery only after confirming the recipients, source references and behavior when evidence is absent.

Product-specific limitations

Imported webpage content is not automatically a live view of the original page. Keep source updates under review. The file-format guide also notes that dense text or large tables can exceed processing limits even below the file-size cap.

Flow knowledge indexing is not instant, so a retrieval step may not see material added earlier in the same run. A Flow cannot combine scheduled and webhook triggers. Inspect scheduling status and failed nodes instead of assuming a completed run produced a usable answer. The limitations guide explains how ambiguous instructions and incomplete references can produce misleading results.

Pricing and access

The pricing page lists Free, Premium and custom Enterprise access. Storage and model usage differ, and enterprise deployment has separate organizational controls. The usage documentation describes included compute, optional administrator-controlled Extra Usage and fallback to standard models and settings when allowances are exhausted. Confirm Flow access, connectors, storage and expected recurring usage for the proposed workspace before choosing a plan.