Skip to main content
Novaplan AI Agents

Create custom AI agents that can perform actions across your connected applications

BetaVisual Builder

​
What are Agents?

Agents are customizable AI assistants that can interact with your connected applications, search collections, and perform actions on your behalf. Unlike the standard chatbot assistant, agents are purpose-built for specific workflows and can be configured with:
  • AI models - Use the organization’s default model or connect models to the agent; if you connect models, at least one must support reasoning
  • Toolsets - Connect to external services like Slack, Jira, Confluence, and more
  • Knowledge sources - Access indexed documents and collections
  • Custom system prompts - Define the agent’s personality and behavior
When you want to use both Connector and Toolset: In the Agent Builder add nodes from Knowledge (Collections, API Apps) for document search and context retrieval, and add nodes from Tools for performing actions. Connect both to your Agent Core so the agent can search context and take action in the same conversation.

​
Key Concepts

​
Visual Flow Builder

Agents are built using a visual drag-and-drop flow builder powered by ReactFlow. You create agents by:
  1. Adding an Agent Core node that defines the agent’s basic configuration
  2. Optionally connecting LLM Model nodes; when models are connected, at least one must support reasoning
  3. Adding Toolset nodes to give the agent access to external applications
  4. Connecting Collection nodes for indexed document search
  5. Configuring edges to connect all components together

​
Agent Core

The Agent Core is the central configuration for your agent:

​
Toolsets

Toolsets are collections of tools that allow agents to interact with external applications. Each toolset provides specific actions:
  • Jira Toolset - Create issues, search tickets, add comments, etc.
  • Slack Toolset - Send messages, search channels, manage conversations, etc.
  • Confluence Toolset - Create/update pages, search content, etc.
  • Gmail Toolset - Send emails, read messages, search, etc.
  • Calendar Toolset - Create events, update events, check availability, etc.
  • Drive Toolset - List files, manage folders, search documents, etc.
Toolsets must be configured and authenticated before they can be used in agents. See Toolsets Overview for setup instructions.

​
Collections

Agents can access your indexed knowledge sources:
  • Connectors - Data synced and indexed from connected applications for querying and search (Google Drive, SharePoint, etc.)
  • Collections - Custom document collections you’ve uploaded

​
Agent Capabilities

​
What Agents Can Do

​
Getting Started

  1. Configure Toolsets - Set up the toolsets your agent will use (Toolsets Overview)
  2. Create an Agent - Use the visual builder to create your agent (Setup Guide)
  3. Test and Iterate - Chat with your agent and refine its configuration

​
Frequently Asked Questions

Example: Use a Gmail Connector to index and search your email history. Use a Gmail Toolset to send new emails through an agent.
Connector — Use when you need document context search: connectors sync and index your documents, emails, and pages so your assistant can find and use that context.Toolset — When you need actions: create or update content, send messages, or run analytical queries (e.g. JQL, CQL, reports).Quick takeaway: Search & context → Connector. Actions → Toolset.
Sometimes. Whether one OAuth app can serve both depends on the provider’s rules, supported redirect URLs, and the permissions required by each integration. Check the connector and toolset setup screens before registering the app.What you need to add in your OAuth app:
  1. Both redirect URLs: Copy the full callback URL displayed for the connector and the full callback URL displayed for the toolset. Register both exactly as shown if the provider allows multiple callbacks on one app.
  2. Required scopes: Review the permissions in both setup guides and the provider consent screen. Connector scopes are not always read-only, and toolsets do not all require write or delete access. Approve only the scopes needed for the intended integration.
If the provider supports this arrangement and your administrator approves the combined permissions, the two integrations can share a Client ID and Client Secret. Otherwise, create separate OAuth apps. Novaplan can help confirm the callback and consent requirements.
Follow this pattern:
  1. Agent Core (required) - The center of your agent
  2. LLM Model (optional) - With no model node, the agent uses the organization’s default model at chat time. If you connect model nodes, at least one must support reasoning.
  3. Toolset nodes (optional) - For actions like sending emails, creating tickets
  4. Collection nodes (optional) - For searching indexed data from Connectors
All nodes must connect to the Agent Core. The agent will have access to all connected toolsets and collections.
Yes! While chatting with an agent, you can select:
  • Specific Collections - Query data from particular Connectors (e.g., search only Confluence or only Drive)
  • Specific Toolsets - Use particular tools (e.g., send via Gmail or create Jira ticket)
  • Reasoning Model - Choose which AI model to use for the query
This gives you control at any time during the conversation to specify where the agent should search or which action to perform.
Yes. You can connect multiple model nodes to the Agent Core, provided at least one supports reasoning.When chatting with the agent, users can select which model to use for specific queries from the chat interface. This allows:
  • Using different models for different complexity levels
  • Flexibility to choose the best model for each task

​
Next Steps

​
Setup Guide

Step-by-step instructions for creating your first agent

​
Toolsets Overview

Learn about available toolsets and how to configure them