web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

Welcome to the Power Platform Communities
News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Blogs / Power Apps - Community Blog / Bring Copilot Studio to Mod...

Bring Copilot Studio to Model-Driven Apps with Xrm.Copilot.executeEvent

Views (2)
Inogic Profile Picture Inogic 1,291 Moderator

Modern business applications increasingly rely on AI to provide users with insights rather than just data. However, there are many scenarios where users must manually combine information from multiple records before deciding.

The new preview Client API, Xrm.Copilot.executeEvent, helps bridge that gap by allowing client-side JavaScript in a model-driven app to trigger a specific Copilot Studio topic, pass business data to it, and receive a structured response.

Unlike a traditional chat interaction, the response can contain structured data that your application can consume directly, making it possible to embed AI-powered reasoning into forms, ribbon buttons, or Power Apps Component Framework (PCF) controls.

In this article, we’ll explore how Xrm.Copilot.executeEvent works, discuss its advantages and current limitations, and walk through a real-world scenario where it adds significant value.

Key Takeaways

  • Trigger Copilot Studio topics directly from JavaScript in model-driven apps.
  • Pass custom business data while automatically receiving page and record context.
  • Retrieve structured AI-generated responses instead of plain conversational text.
  • Ideal for AI-powered reasoning, summarization, and contextual insights.
  • Currently available as a preview feature and not recommended for production workloads.

What Xrm.Copilot.executeEvent Actually DoesUsing Xrm.Copilot.executeEvent to bring Copilot Studio into Your Model-Driven App

The method signature is simple:

EventName: a string identifying the Copilot Studio topic that should handle this call. It has to match a topic registered to respond to that named event.

EventParameters: A JSON payload of whatever data the topic needs to do its job. Inside Copilot Studio, this shows up as Activity.Value, and the topic uses a Parse Value node to break it into usable fields... Read More

Comments

*This post is locked for comments