[Copilot Studio] How to Create a “Loop” Using the ‘Go to Step’ Node (Conversation Retry Pattern)

Unlike Power Automate, Copilot Studio currently doesn’t have a dedicated “Do Until” or “While” loop action. However, the “Go to step” node is a powerful feature that effectively solves this limitation.

In this post, I will show you how to create a conversation loop (e.g., for user confirmation or retries) using this node.

What is “Go to step”?
Scenario: Meeting Setup Confirmation
Implementation Guide
Testing the Loop
Conclusion
Related Articles

What is “Go to step”?

The “Go to step” node allows you to jump to any previous node within the same topic.

This is perfect for creating feedback loops where the bot asks, “Is this correct?” and repeats the question if the user says “No.”

Scenario: Meeting Setup Confirmation

In our previous article, we built a topic that extracts “who to meet with” from user input using AI Builder. Originally, it proceeded immediately to the booking step.

Now, we will add a confirmation step: “Are you sure you want to meet with these people?”
If the user answers “No,” the bot will loop back and ask for the names again.

Implementation Guide

1. First, after the AI extracts the names (Japanese names in this case), add a new “Ask a question” node.

2. Configure the question to confirm the names and save the user’s choice (Yes/No) into a Boolean variable.

Pro Tip: Use a Power Fx formula to neatly display the extracted names.

Concat(Topic.result.structuredOutput, ThisRecord.name, ", ")

3. Add a “Condition” node to check the user’s answer.

Set the condition to check if the Boolean variable is equal to false (User said “No”).

4. In the “No” branch, select Topic Management > Go to step (or “Go to another step”).

5. Select the very first question node (“Who do you want to set up a meeting with?”) as the destination.

Now, the flow line connects back to the start, creating a visible loop.

The loop logic is now complete!

Testing the Loop

Let’s test it. When the bot asks for confirmation, select “No”.

As expected, the bot returns to the first question, allowing the user to re-enter the correct names.

Conclusion

The “Go to step” node is essential for building “Human-in-the-loop” workflows, such as input validation, corrections, and feedback cycles.

Note: While useful, overuse of “Go to step” (similar to GOTO statements in programming) can make your topic logic hard to read. Use it wisely to keep your flow clean!