Dataverse goes where you build: Copilot Cowork, coding agents and n8n

Developers rarely pick one tool and stay in it. A single week might include coding agents in the IDE, a terminal agent for quick tasks, an automation platform for integrations, and an AI assistant for everything in between. However, business data should not get harder to reach as that list grows. That is why we keep bringing Dataverse to the coding agents and platforms where you already build.

In July, we expanded the Dataverse plugin for coding agents to Claude, Cursor and GitHub Copilot, and we committed to supporting more. Since then, Dataverse has arrived in Copilot Cowork, in more coding agents and in n8n. This post brings the full picture together in one place.

Where Dataverse runs today: Copilot Cowork, coding agents and n8n

Here is where Dataverse is available today, and how to add it on each platform. Each listing installs the same open-source Dataverse skills.

For any other agent that reads local skills, one command installs every Dataverse skill: npx skills add microsoft/Dataverse-skills -s "*". Full instructions for each platform are in the Dataverse skills repository on GitHub.

Copilot Cowork: governed apps from a single prompt

The Dataverse plugin in Copilot Cowork brings Dataverse skills to a conversational, approval-driven experience. You describe an app in plain language. Then Cowork designs the tables and relationships, reuses existing tables such as Contact, and seeds sample data. Finally, it builds and publishes a working app in Microsoft Copilot Managed Runtime (preview). Every change comes to you first as an approval card, and every action runs with your own permissions.

For a full walkthrough and demo, read the companion post, From one prompt to a governed Dataverse app: the Dataverse plugin lands in Copilot Cowork.

n8n: a native Dataverse node for your workflows

n8n is where many developers connect apps, APIs and AI agents into workflows. Dataverse is now a built-in node there, so there is no custom HTTP plumbing to write.

In the video, the n8n AI Assistant builds a multi-channel lead-capture workflow in seconds. Leads arrive from a web form, WhatsApp, Telegram or Facebook. Next, an AI step extracts the details. Then one Dataverse node checks for an existing lead, and a second Dataverse node creates the lead if it is not there yet. This is the pattern we see most often: read trusted context from Dataverse, act on it, and write the result back. All of it happens inside the automation platform the team already uses.

Beyond the demo, the Microsoft Dataverse node can create, update, upsert, get, get many and delete rows in standard and custom tables through the Dataverse Web API. For example, Get Many supports column selection, OData filters, sorting, expand and FetchXML. Table and column pickers also load straight from your environment’s metadata. Meanwhile, the Microsoft Dataverse OAuth2 credential supports both delegated user access and app-only access. Every operation and option is documented on the Microsoft Dataverse node page in the n8n docs.

The same Dataverse skills across coding agents

Under the hood, every coding agent integration is built from the same open-source skills. As a result, the experience stays consistent wherever you work. A connect skill handles one-time setup and authentication. Specialist skills then cover the rest of the job:

• Querying records and bulk data import
• Data modelling for tables, columns, relationships, forms and views
• Solution lifecycle
• Security roles and access
• Environment administration
• Finance and Operations X++ development and deployment

In addition, an overview skill routes each request to the right specialist. Behind the scenes, the plugin picks the right tool for each job. That might be the Dataverse MCP server, the Dataverse CLI, the Python SDK or PAC CLI.

Most importantly, the guardrails travel with the skills. The plugin follows a least-privilege model, so it cannot exceed the permissions of the signed-in user. Dataverse authorizes every API call on the server. Credentials stay in the operating system’s secure credential store or in memory. Finally, the only telemetry is application-level metadata. It excludes prompts, tool arguments or record data.

Why Dataverse belongs wherever you build

Dataverse already holds the records, relationships and rules that run the business. It is also built into Power Apps, Power Automate, Copilot Studio and Dynamics 365. Agents and automations are only as good as the context they work with. So our job is to make that same context available wherever developers and makers build, with enterprise security intact. Each added surface is one less reason to copy data somewhere else. In turn, it is one more place where the same trusted data model does the work.

We are not done yet. Tell us which platform you would like to see next. You can also contribute skills or improvements directly on GitHub.

Learn more

• From one prompt to a governed Dataverse app: the Dataverse plugin lands in Copilot Cowork
• Dataverse documentation
• Microsoft Dataverse node in the n8n docs
• Dataverse skills on GitHub
• Custom APIs in the Dataverse MCP server
• Dataverse and Work IQ at PPCC 2026
• July 2026 update on the Dataverse plugin and MCP

The post Dataverse goes where you build: Copilot Cowork, coding agents and n8n appeared first on Microsoft Power Platform Blog.