# Overview Nected AI Copilot lets you go from a business requirement to fully built Rules and Workflows — without writing logic manually. Describe what you want to automate, upload a PRD, and Copilot handles the rest: it asks the right clarifying questions, shows you a plan before building, and creates the actual assets inside Nected that you can immediately test and use. This page covers what Copilot does and walks through the complete usage flow with UI steps. ### Overview Most automation tools make you configure logic from scratch. Nected AI Copilot inverts that. You start with intent — a plain-language description of a decision or process — and Copilot produces a working draft of the Rules and Workflows needed to implement it. Here is what Copilot does for you: **Understands business requirements directly.** You can describe a requirement the way your business team would write it, or upload a full PRD. Copilot extracts the logic from either format. **Asks the right clarifying questions.** When details are missing — thresholds, fallback behavior, field names, branching conditions — Copilot asks before it builds. This replaces the back-and-forth that usually happens during spec review. **Shows you the plan before creating anything.** Before any assets are created, Copilot presents a visual flow diagram and a list of everything it intends to build. You can approve the plan or revise it with feedback. **Builds the assets inside Nected.** Once approved, Copilot creates the actual Rules and Workflows in your workspace. You can click into each asset and test it immediately. {% embed url="" %} ### How to Use Copilot #### Step 1: Write Your Requirement or Upload a PRD From the **Home** page, open **Nected AI Copilot Beta**. In the Copilot input area, do one of the following: * **Type your requirement directly.** Be as specific as possible. Include what decision or process you are automating, what the inputs are, and what the expected outcomes should be.
* **Upload a PRD.** If your requirement covers multiple scenarios or is too large to describe in a prompt, upload the document and add a brief instruction in the prompt box telling Copilot what to generate from it.
**Example prompt:** ``` I need to automate merchant onboarding. Check KYC status and fraud score, then decide whether to approve, send for manual review, or reject. ``` **Example prompt with PRD:** ``` Use this PRD and generate decision logic for onboarding with clear approve/review/reject behavior. ``` {% hint style="info" %} Up to 5 chats are included. To use Copilot beyond this, connect your own Claude model. {% endhint %} *** #### Step 2: Answer Copilot's Clarifying Questions After reading your requirement, Copilot will ask targeted clarifying questions before generating anything. This is not a formality — Copilot uses your answers to define the actual logic it will build. Common clarification types: * What should happen when an input field is missing or null? * What are the exact threshold values for each condition? * Are there multiple branching paths? What determines each path? * What is the fallback or default behavior? **Answer each question explicitly.** Vague answers lead to generic output. For example, instead of saying "route to review," say "if fraud score is between 40 and 70 and KYC is verified, route to manual review." If you need to refine an answer, continue in the same thread — do not start a new conversation. #### Step 3: Review the Plan — "Here's What I'll Build" Once Copilot has enough clarity, it generates a plan before creating any assets. This appears as a **"Here's What I'll Build"** section in the chat. The plan includes: * **A visual flow diagram** showing the full decision or process logic, with branches and outcomes * **A list of assets** Copilot intends to create — each Rule and Workflow is listed, and you can preview them individually before approving At this point, you have two options: **Option A: Create Assets** If the logic looks correct, click **Create Assets** to proceed. Copilot will begin creating the assets in your Nected workspace.
**Option B: Modify the Plan** If something needs to change, like a missing branch, wrong outcome, or different structure- click the **Modify Proposal** button, which will add this prompt: "Modify the proposed solution:". Then type your feedback directly in the chat. For example: ``` Modify the proposed solution: Add a branch for when KYC is pending. Route those cases to manual review instead of reject. ``` Copilot will revise the plan and show you the updated version. You can continue refining before approving.
#### Step 4: Copilot Builds the Assets After you approve the plan, Copilot begins creating the assets. This may take a moment depending on the complexity of the requirement. Once complete, Copilot confirms the assets have been created and shows clickable links to each one directly in the chat.
#### Step 5: Review and Test the Assets Click any asset link from the Copilot chat to open it in the Nected editor. From there, you can: * Review the full logic of each Rule or Workflow * Test the asset using sample inputs * Identify any adjustments needed If something is incorrect, you can return to the Copilot thread and request specific changes, or edit the asset directly in the Nected editor. ### Limitations The following features are not yet supported in the current version of Copilot: **Integration support in PRDs is mocked.** If your PRD references external integrations (for example, calling a third-party API or connecting to a data source), Copilot will generate a mock placeholder for those integrations. The actual integration setup must be completed manually. Full integration support in Copilot is coming soon. **Editing existing Rules and Workflows via Copilot is not yet supported.** Copilot currently creates new assets. The ability to use Copilot to edit or update existing rules and workflows is coming in a future version. **Copilot is Claude-compatible only.** Nected's Rules and Workflows are optimized for Claude. If you plan to connect your own model, use a Claude-based model for the best results. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.nected.ai/nected-docs/ai-assistant-copilot/overview.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.