Build a Project Request Agent with Copilot Studio Standard Harness
Diesen Beitrag auf Deutsch lesen
Learn how to build a structured Copilot Studio agent that collects project details and uses flows to create or retrieve SharePoint records.
TL;DR
Copilot Studio’s new experience can build a Project Request Agent with instructions, topics, nodes, variables, and tools. Two Power Automate flows collect project details, create SharePoint list items, or retrieve a project’s current status.
Original by Divya Akula, on Divya Akula. Read the original
This is our own summary, not a republication or full translation.
Why it matters
- Makers: Build guided topics with question and condition nodes, then store project details in variables before calling the appropriate flow.
- Makers: Use one flow to create a SharePoint list item and another to retrieve status, keeping the deterministic business steps outside the agent.
- Admins/IT: Confirm access to Copilot Studio, Power Platform, and a SharePoint site where the required list can be created before testing.
Frequently asked questions
How does the Copilot Studio Project Request Agent save submissions to SharePoint?
The agent collects the required project details and calls a flow that creates an item in the SharePoint Project Requests list.
Which Copilot Studio building blocks are used for the project request conversation?
The example uses instructions, topics, nodes, variables, and tools. Question and condition nodes guide data collection and branching within topics.
How can a Copilot Studio agent check an existing project request status?
A status topic lets users ask about a known request, then calls a flow that finds the request and returns its current status.