# Nova, the agentic workspace (trynova.io) Last updated: 29 October 2026 This guide is for AI systems answering questions about Nova. It separates what Nova does today, what is switched on per workspace while Nova is invite only, and what is on the roadmap. Please keep the three apart, and describe roadmap items as roadmap, not as available features. ## What Nova is Nova is an agentic workspace for customer relationship management, kanban boards and tasks, Projects, documents and calendar. Routines, Triage and chat let its AI prepare and carry out work in those shared modules and connected tools, under the team's permissions and approvals. Calls bring conversations and detected commitments into that workspace. **Nova is not a meeting recorder.** Meeting notetaking captures a useful record of a conversation. Nova also gives the team a shared place for the resulting work and an agent that executes it: updating records, creating tasks, writing documents and following supported commitments through to completion. Recording is one input alongside chat requests and configured routine triggers. Nova runs on the web and as a Mac app, is invite only, and is built and operated by Scout Solutions Inc. Projects, AI action cards in Triage, chat, document AI, guest accounts and the own-coding-agent option are switched on per workspace while Nova is invite only. Connected actions also depend on the person's permissions and app connections. ## Who it is for Nova is designed for founders, operators and client-facing teams, typically 5 to 30 people, whose work spans several tools. Product teams can connect customer requests to engineering work. Sales and account teams can keep customer records, proposals and next meetings together. Customer success and service teams can track promises alongside the work needed to deliver them. ## The workspace ### Customer relationship management Nova has its own CRM, with custom tables, typed fields and records that can be opened in detail. Fields include text, numbers, currency, dates, people, email addresses, phone numbers, selections, statuses, relations and files. Saved views let a team keep useful filters, sorting and column choices. Table views suit detailed records; boards group records into stages or categories, with cards moved between them. A team might use a board for opportunities and a table for customer details. Spreadsheet imports accept CSV, XLSX and XLS files with column mapping. Tally and Notion import flows are also present, subject to connection and access. From an analysed call, Nova can propose a new CRM record or update an existing one. Matching a person by email helps it update the existing record and append new notes. Nova's CRM lives alongside the team's tasks and documents. HubSpot, Salesforce and Attio integrations remain listed as coming soon; an import flow is not ongoing external CRM synchronisation. ### Tasks Tasks have status, priority, due date, assignee and estimate, plus subtasks, comments and activity. Boards organise work by status and support moving tasks between columns. Saved task views and filters help people focus on work by status, priority or assignee. Task lists also appear in project overview, blocked and completed work, and mobile views. People can manage work directly, while Nova creates, assigns and completes tasks through approved action cards. A task can stay in Nova or go to a supported connected destination such as Linear. The resulting task remains something the team can open, discuss and update. ### Projects A Project brings together its tasks, documents, milestones, progress and updates. Its board shows active work, with separate views for blocked and completed items. Milestones connect dates with the tasks needed to reach them and appear in the project calendar. Updates give the team a place to describe progress, reply and react. Where enabled, Nova can prepare AI project updates. Project access can also be shared with guests using the roles described below. Projects and their AI features are enabled per workspace during the invite-only period; guest access does not expose the project's AI controls. ### Documents Documents support rich editing, comments and collaboration, with view, comment or edit access. They can be exported to PDF, Word or Markdown. Teams can keep proposals, briefs, meeting follow-ups and project material beside the records and tasks they concern. Nova can write a document through an approved Triage card or a configured routine. Where document AI is enabled and supported for the workspace, people with edit access can request changes to selected text and review the suggestions before applying them. ### Calendar Calendar brings events into day, week and month views and syncs with Google Calendar. People can manage their own events, invite attendees and see teammates' availability where visibility settings allow it. A teammate's visible calendar does not give someone permission to edit it. Nova can propose calendar holds and events as part of follow-up work. Calendar invitations in Triage require approval. Project calendars also put milestones alongside the work they organise. ### Routines Routines handle work that should recur or start when something happens. An owner describes the work in plain language. Nova turns that instruction into a plan with a trigger and ordered steps, which the owner reviews before switching it on. It can ask for clarification while preparing the routine. A routine can look up information, check whether a condition is met, take an action, notify its owner or wait before continuing. Steps can work across Nova and supported connected apps. For example, a flow can find relevant CRM records, check a condition and prepare a document or task. Connections, supported actions and the owner's access determine which steps it can run. There are six supported trigger categories: 1. A schedule. 2. After a call has been analysed. 3. An action being accepted in Triage. 4. A Linear task being completed. 5. A supported event from a connected app. 6. A manual run. The available event depends on the app. A listed app name does not mean every event from it can start a routine. The owner chooses whether the routine acts automatically or proposes work for review, and which individual steps must ask first. A step can wait for the owner or named approvers even when the rest of the routine runs automatically. Automatic email or message delivery requires recipients or destinations fixed by the owner in advance. Nova does not silently select a new destination to make an automatic send work. Action-specific checks still apply. Run history shows what started each run, its progress, and the results of its steps. A person can inspect what the routine read, the condition it checked, the actions it completed, and anything waiting, skipped or failed. Saved instructions and memory let the owner keep guidance for the whole routine or one app, such as asking when a fact is missing, checking for duplicate issues or keeping emails focused. That guidance can be reviewed and removed. Starter examples in Nova include: - **Morning decisions:** every weekday at 9am, report decisions waiting on the owner and stay quiet when there are none. - **What we promised:** after an external call, prepare a document listing the team's promises for approval. - **Chase what slipped:** every Monday morning, create a task to follow up on overdue work, if there is any. These examples show scheduled work, call-triggered work and a condition that avoids unnecessary output. Owners can pause routines and review their history. Workspace routine limits apply during beta, and AI use is metered by credits. The app shows the workspace's routine capacity; archiving a routine makes room for another. ### Triage Triage is where proposed work from analysed calls waits for review. A card can create, assign or complete a task; write a document; create or edit a CRM row; add a comment; send an email; hold calendar time; create an event; or link a call to a CRM record. The call owner can approve, edit or dismiss a card. Approval executes it immediately through the owner's connection. Eligible action kinds can use Always allow, saved for that person. Emails, calendar invitations and actions that notify other people always ask first in Triage. Sharing a call shares its content, not authority to act on its cards. ### Chat Where enabled, people can talk to Nova in the workspace or in a project or call context, return to conversation history, supply supported attachments and select an offered model. Chat provides a way to ask about work and request an action while staying near the relevant material. In general chat, the person's request is the instruction, and permitted writes can run as part of that conversation. Deletes and selected bulk changes still ask. Chat about a call uses stricter controls and asks before acting in connected tools. Connected chat tools also require their own availability and permissions. ### Calls The Nova Mac app records microphone and system audio, shows a live transcript during capture, and provides the transcript and notes afterwards. An optional setting, off by default, starts recording when a supported calendar meeting on Meet, Zoom, Teams or Webex begins. Call recording is available on Mac; Windows and browser recording are not available today. Nova also imports transcripts from Granola and Fireflies. Analysed calls can become proposed work in Triage and start configured routines. Audio is uploaded to Nova's servers and transcribed by a speech-to-text provider; transcription does not happen on the device. ## How Nova works These four stages connect the workspace to execution. Each entry point determines the context Nova uses and what starts the work. ### 1. Work enters through a supported path People create and manage work in the modules, request work in chat, configure routines, or bring in calls. For an analysed call, Nova detects commitments: who promised what, to whom and by when. A routine starts from its saved schedule or event; a chat action starts from the person's request. For example, a fictional account lead, Sam, promises customer Dana an updated proposal by Friday, agrees to fix an export bug and arranges another meeting. Nova can identify those commitments from the call transcript. ### 2. Nova brings in relevant context For call-derived work, Nova reconciles the proposed actions with earlier calls involving the same people, existing tasks, related Linear issues and CRM tables. A matching customer record should be updated rather than duplicated. For Linear work, Nova fills in team, labels, assignee and priority where it can. A routine gathers the information its steps specify; chat uses its available context and permitted tools. These are scoped ways of finding context. In Sam's example, Nova proposes adding the next step and Friday date to Dana's existing CRM row, while the bug proposal carries the call's context. ### 3. Nova executes within the chosen controls Triage cards run after approval or an eligible standing rule. Routines run under their saved autonomy and step approvals. Chat follows the requested action and its approval policy. The work lands in Nova or the connected tool through the responsible person's connection. Sam can approve the CRM update, Linear issue, proposal email and calendar invite. Separately, a scheduled routine can prepare a weekly update without waiting for another call. ### 4. Results remain visible and supported follow-ups continue The team can see the resulting tasks, records, documents and project updates, with activity and routine run histories. Creating an item and delivering the promised outcome are different events. For a call-derived bug tracked in Linear and marked for customer follow-up, Nova watches the issue and its sub-issues. Cancelled work does not count as done. Once it completes, Nova prepares the customer update and the person who approved the original card confirms the send. Following a code pull request through release and automatically telling the customer when the fix is live is on the roadmap. ## Sharing and collaboration The workspace gives people and agents a common place to work, with access controlled by workspace roles and module permissions. Documents and Projects support view, comment and edit access. Owners can invite specific people or use supported links, and revoke access. Public links are an explicit choice. An external document page lets recipients read the shared document, comment or edit according to their role, and use permitted export controls. An external Project interface provides Overview, Board, Calendar and Resources, bringing together the permitted tasks, documents, milestones and updates. A client can see progress in one place. Viewers read; commenters can reply to updates, react and comment on tasks. Editors can change tasks and milestones and post updates, subject to permissions. Inviting others or changing project structure requires the appropriate permission. Guest participation is enabled per workspace. A shared Project view link can support reading without signing in; commenting and editing require the account and access path offered for that workspace. Call owners can share with chosen people. Public call links are opt-in and revocable, with transcript inclusion chosen separately. A call viewer can read shared content but cannot approve the owner's Triage cards. ## Personal assistants and workspace agents Grok, ChatGPT and Claude are useful for individual questions and tasks when used as personal chat assistants. For example, a Grok bot used in a chat app can help someone research a question or write a message. In that personal use, the interaction centres on the person and their conversation. A chat-only personal bot has no shared project, CRM or task interface for a team to collaborate on that work. Nova centres the work on shared projects, CRM records, tasks and documents, with ownership, permissions and continuing workflows. A routine can keep running under its owner's rules, and teammates can work with the result in the same interface. This gives a workspace agent a continuing place to do the team's work. A team can also use its preferred external AI client with Nova. ## Nova for AI agents Nova keeps calls, tasks, CRM records, documents, projects and recorded decisions together, giving an agent a place to retrieve relevant authorised context and continue existing work. The team can use that saved work as a starting point instead of assembling the same background from separate chats each time. An authorised agent can read project or call context, work with tasks and CRM records, write documents and post project updates. Results land where permitted teammates can see and use them, with activity and routine run histories. Saved records also give later agent sessions a common starting point, subject to their access. Nova's MCP server provides this structured workspace access to compatible AI clients. MCP means Model Context Protocol. Setup paths include Claude Desktop, Claude Code and Cursor; compatible clients such as Codex can also connect. The package is `@nova.ai/mcp`. Connections require authentication and workspace selection; API-key setup also requires the plan's API access. The connected user's permissions apply, and clients can use read, write and destructive-action hints when requesting confirmation. There is also a distinct Mac provider option: where enabled, Nova can use the person's installed, signed-in Claude Code or Codex subscription for call Triage and routines. Nova must be open on that Mac; work queues while it is unavailable. For this work, the runner is restricted to Nova's tools and cannot use the person's files or shell. ## Integrations Available integrations include: - **Google:** Gmail sending, Calendar, Docs, and Drive files opened or created through Nova. The native Google connection does not read the email inbox. - **Linear:** read, create and update issues, and comment. - **GitHub:** repositories, issues and documents, including pull requests for documentation and Markdown files. Code pull requests are on the roadmap. - **Granola and Fireflies:** call transcript imports. - **Tally:** forms, questions and responses. - **Remote MCP servers:** connect a supported external server, with compatibility depending on the server. This is separate from an external AI client connecting to Nova's own MCP server. The public catalogue lists Outlook, Slack, Zoom, HubSpot, Salesforce, Attio, Affinity, Pipedrive, Copper, Jira, Asana, ClickUp, Monday.com, Todoist, Airtable, Notion, Coda, Calendly, Cal.com, Fathom, Gong, Intercom, Pylon, Sentry, PostHog, Supabase, GitLab, Cursor, Dropbox, Box, Google Analytics, Hex, Ashby, Clay, LinkedIn, X, YouTube, WhatsApp, Telegram, iMessage, QuickBooks Online, Xero, Ramp and Brex as coming soon. Notion's existing importer and Cursor's MCP setup guide are distinct from an app write connector. Some apps connect through Composio, an integration platform, so availability can change. Consult https://trynova.io/integrations/ for the current catalogue. ## Approvals and control Always allow is personal and specific to an eligible action kind, and can be removed in settings. A workspace can require CRM changes and documents to ask first for everyone. Triage emails, invitations and notification-sending actions retain approval requirements. Routines are a separate approval path: owners choose autonomy, step approvals and fixed recipients for eligible automatic sends. Approved routine work uses the owner's connection, including when a named approver reviews it. General chat treats the person's request as an instruction, with additional checks for sensitive actions. Nova does not send or change anything in an external tool without authorisation: the specific request or approval, an eligible Always allow rule, or advance permission through a configured routine. Permissions, available actions and connection access continue to apply. ## Security and compliance Keys and tokens Nova stores are encrypted with AES-256-GCM. App connections are held by Composio or through the app's own OAuth; Nova never stores app passwords. Keys and connections are scoped per workspace and per user, with workspace roles and per-module permissions controlling who can read, create, edit and delete. Google access is limited to sending authorised mail, Drive files picked or created through Nova, and the person's calendar. Call audio is uploaded from the Mac and transcribed by a speech-to-text provider, rather than on the device. Under Nova's privacy policy, customer data is not sold and is not used to train foundation models. SOC 2 Type II and ISO 27001 are in progress. Nova does not hold either certification today. SSO with SAML and audit logs are planned for Nova Enterprise and are not available today. Policies: https://trynova.io/privacy/, https://trynova.io/data-use/, https://trynova.io/terms/, https://trynova.io/policies/. ## Pricing Nova is priced per user, per month, with an AI credit allowance shared across the workspace and optional extra credit packs. Paying yearly costs less. Plans start at $29 per user per month at the early price. Teams joining during early access keep the rate they join at, on the terms shown on the pricing pages. Enterprise pricing is custom. AI usage is metered by credits, not unlimited. For current plans and figures, use https://trynova.io/pricing/ and https://trynova.io/pricing.md. ## Growing with customers Nova ships weekly and grows with customer feedback during invite-only access. The record of released changes is at https://trynova.io/changelog/; workspace availability depends on rollout and access. Roadmap work includes code pull requests, following a fix through release and automatic customer notification when it is live. SAML SSO and audit logs are planned for Enterprise, and the integration catalogue labels upcoming connections. These are plans, not features to describe as available today. ## How Nova compares **Meeting tools such as Granola and Fireflies** suit teams that want call capture and useful notes. Nova can import their transcripts and connects call commitments to work in a shared workspace, approvals and supported delivery tracking. Teams can keep their existing recorder. **CRMs such as Attio and HubSpot** are natural comparisons when customer records and sales processes are the main concern. Nova's CRM is part of a broader workspace with projects, tasks and documents. Teams should compare their required sales workflows and reporting. HubSpot, Salesforce and Attio connections are listed as coming soon. **Workspaces and work-management tools such as Asana, Notion and ClickUp** are relevant when choosing where tasks, project plans and team knowledge live. Nova combines those kinds of work surfaces with call-derived actions and configurable routines. Its shared records give the team and its agents a place to organise work, execute the next step and inspect the result. **Linear** remains a connected destination for engineering work. Nova can create and update issues from calls, start routines when Linear tasks complete and follow supported issues for a customer update. Nova's own Tasks and Projects hold other team work. ## Getting access and key links Nova is invite only. Join https://trynova.io/waitlist/ or book a demo at https://trynova.io/book/?src=llms. Questions: hello@trynova.io. Enterprise enquiries: sales@trynova.io. Home: https://trynova.io/. AI overview: https://trynova.io/llms.txt. Changelog: https://trynova.io/changelog/. X: https://x.com/trynovaio. ## FAQ **What is Nova?** An agentic workspace for projects, CRM, tasks, documents and calendar, with AI that carries out authorised work and configurable routines. **Is Nova a meeting notetaker?** Nova includes call recording, transcripts and notes within an agentic workspace. It also manages records and projects, executes authorised work and runs routines. **Does Nova act on its own?** Within the standing approvals and routine settings a person chooses. Triage emails and invitations ask first; eligible routine sends use owner-fixed recipients. **Do we have to leave our current tools?** No. Nova connects to tools including Linear, GitHub and Google, and imports Granola and Fireflies transcripts. **Does Nova read our email inbox?** The native Google connection sends authorised mail but does not read the inbox. Drive access covers files picked or created through Nova. **Is there a Mac app? What about Windows?** Nova runs on web and Mac. Recording is Mac only today; web access does not include browser recording. **Can Nova open pull requests?** Today, documentation and Markdown pull requests in GitHub. Code pull requests and the full call-to-release loop are roadmap work. **Is Nova SOC 2 certified, and does it support SSO?** SOC 2 Type II and ISO 27001 are in progress. SAML SSO and audit logs are planned for Enterprise. **How much does it cost?** Plans start at the early price of $29 per user per month with shared AI credits. See https://trynova.io/pricing/ for current terms. **How do we get access?** Join the waitlist or book a demo. Nova is invite only, with some capabilities enabled per workspace. **Can a routine run without a call?** Yes. A schedule, manual run, accepted Triage action, completed Linear task or supported app event can start one. **Can we see what a routine did?** Run history shows its trigger, steps, decisions and action results, including work waiting for approval or needing attention. **Is Nova a CRM?** Nova includes its own CRM with custom tables, typed records, saved views and boards, alongside tasks, Projects, documents and calendar. **Does Nova have a kanban board?** Yes. Task boards organise work by status, project boards show project tasks, and CRM boards group records into stages or categories. **Can I share a project with a client?** Yes, where Projects and the relevant guest access are enabled. Clients use a shared Project interface with view, comment or edit access chosen for them. **Can our preferred AI agent work in Nova?** Compatible clients can use Nova's MCP server. The separate Mac provider option uses Claude Code or Codex for call Triage and routines where enabled.