I can't return an action in my journey through Power Automate with a Power Virtual Agents trigger

(2) Share

Report

Posted on by LA-13031724-0

I can't return an action in my journey through Power Automate with a Power Virtual Agents trigger,

In this image I just show which trigger, every time I publish the journey, and the action goes on hold, even though my automate flow is running passing the answer to yes, the journey goes to no, even though the automate is running successfully without error, it is as if the journey did not receive.

The automation flow is started by a copilot agent after the user who received the WhatsApp responds. There is no problem at this stage, I am just explaining how the entire flow works.
A little while ago I tested how, instead of having a copilot's power agents call the automate, I made the call with a custom trigger within the journey, and the automate that I called through the journey managed to return an exact response to the action, but this caused me a doubt, does this mean that externally started automates cannot return value to waiting triggers on the journey? Does this mean that only automations started within the journey send requests to actions that are waiting? And if that is indeed the case, why then does Microsoft leave the trigger code for the action, and we send it, but the journey does not respond, this sounds a bit contradictory.

Categories:

Dynamics 365 Customer Insights - Journeys

I have the same question (0)

All responses (2)

Answers (1)

Verified answer

Saif Ali Sabri 2,351 Super User 2025 Season 2 on at

Like (0)

Report
Yes, your observation is correct. In Dynamics 365 Customer Insights - Journeys (formerly Marketing), only Power Automate flows triggered from within the journey itself can reliably return values to waiting actions. Flows triggered externally (e.g., from Power Virtual Agents) do not automatically link back to the journey’s waiting trigger, even if you pass the action’s trigger code.
Solution Options:

Trigger Power Automate from the Journey – Instead of starting Power Automate from Power Virtual Agents, trigger it directly from the journey using a custom action. This ensures that the journey correctly receives the response.

Use Dataverse as an Intermediary – Store the response in a Dataverse table and have the journey check for updates via a scheduled trigger.

Re-evaluate API Calls – If using external automation, ensure you're correctly calling the Dynamics 365 Marketing API for event triggers.

Microsoft provides trigger codes for external use, but their handling within journeys is limited. The safest approach is to initiate automation within the journey itself.

Was this reply helpful? Yes No
LA-13031724-0 14 on at

Like (0)

Report

I managed to do it, the problem was in the return that I was setting up in the automation initiated by power agents, the segment of my journey is from customers coming from customer insights, I needed to send the customerId and was sending the contact, in short if you send a wrong ID the journey does not receive it, so you have to pay attention to the body of the return for the journey.

Was this reply helpful? Yes No

Join the conversation

Community site session details

I can't return an action in my journey through Power Automate with a Power Virtual Agents trigger

Solution Options:

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates

Community site session details

I can't return an action in my journey through Power Automate with a Power Virtual Agents trigger

Solution Options:

Helpful resources

Quick Links

Responsible AI policies

Neeraj Kumar – Community Spotlight

Congratulations to the November Top 10 Community Leaders!

Subscribe to this forum!

Select categories

Leaderboard > Customer experience | Sales, Customer Insights, CRM

Featured topics

Product updates