Skip to main content
The current Nexor workspace starts with chat at app.getnexor.ai. Use Nexor AI to ask about your account, investigate a record, or request a configuration change. Open an agent and its task when the request concerns a specific job.
Some guides and screenshots describe the classic interface, which remains under /v1. Its Summary/Chat switch and floating chat launcher are not the navigation for this workspace. If the controls in a guide do not match your screen, use this guide first.

​
Choose the right agent and task

An agent can contain several Tasks. Each task describes a job the agent does with your leads. The agent’s shared channels, schedule, and instructions provide defaults; a task may keep those defaults or use its own settings where an override is available. Open the agent, then choose the task before requesting a task-specific change. In your request, state whether it should affect just that task or the shared configuration. Do not assume a task change applies to every task. Some older guides call a task an Agent and its shared container a Group. API field names and identifiers also retain those older names; this does not change which scope you should select in the workspace.

​
Find records and workspace areas

Use Search, or press Command + K on macOS or Control + K on Windows and Linux. For authorized workspace users, search includes agents, leads, knowledge, channels, tools, functions, and pages. Results depend on your role and selected account. The workspace also provides access to Leads, Inbox, Meetings, Knowledge Base, and Integrations. Some items depend on your permissions or enabled features. Open the account menu for Settings and Docs. A link to a lead opens that record. A task or group link selects its context in the chat workspace. Settings may open as a panel or dialog, so not every control has its own page URL.

​
Configure a CRM through chat

Start with the CRM chat and MCP guide, which describes the available operations and provider limits. In the agent workspace, Data sources is the place to review connected sources. A useful request identifies the provider, the receiving task, and the direction of the data:
  • “Show the HubSpot connection and incoming routing for this task. Do not change anything.”
  • “Explain which CRM fields fill this task’s Variables and which values are inherited.”
  • “Propose mapping the CRM budget field to this task’s budget Variable. Show the affected scope before applying it.”
  • “Check the latest import and explain why this lead did not synchronize.”
Keep these checks separate:
  • Connection: Nexor can authenticate to the external account.
  • Configuration: routing, field mappings, Variables, and outputs are configured for the intended task or group.
  • Execution: a particular import or synchronization actually ran and produced the expected result.
A connected account is not proof of successful synchronization. A queued job or preview is not a completed import. Ask for the specific execution result when troubleshooting.
Complete authorization through the connection screen. Do not paste API keys, passwords, or private receiving URLs into a support conversation.

​
Request changes and verify the result

Describe the desired outcome and its scope. If you want a proposal first, explicitly ask Nexor AI to inspect and explain before changing anything. Review any confirmation requested by the flow, then check the saved configuration and test with an appropriate test record before relying on it for live leads. Nexor AI in your workspace can perform supported configuration operations. The support conversation is for guidance and diagnosis; do not assume a support reply has applied a change to your account. For scheduling in HubSpot or GoHighLevel, follow CRM booking through chat. Provider availability and prerequisites still apply.

​
If a guide shows the classic interface

Use the current workspace for chat, agent and task context, leads, and knowledge. Use a classic screen only when your team is working there or the documented function requires it. When asking for help, include the area and task you were using and the control you expected to find. Support can distinguish a navigation change from a missing permission or configuration.
Last modified on September 21, 2026