Answered

Call back url is not set as the trigger is being used as an action

(0) Share

Report

Posted on by Community Power Pla... Microsoft Employee

Hello,

I am getting an error while trying to trigger a create event : Call back url is not set as the trigger is being used as an action.

{
  "status": 400,
  "message": "Call back url is not set as the trigger is being used as an action",
  "source": "dynamicscrmonline-eus2.azconn-eus2.p.azurewebsites.net",
  "debugInfo": "clientRequestId: 49446494-7d2c-486d-ae13-cfe0d6e8b37c"
}

Can someone help me with the issue?

Thanks

Categories:

General topics

All responses (5)

Answers (2)

Sort by

v-bacao-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @agupta1112,

Could you share full screenshot of your Flow configuration?

I can't reproduce this mistake on my side.

The error message is the trigger is being used as an action and error code is 400. I wonder if there would be a problem with the configuration of action.

Flows will fail if a setting in an action of the flow doesn't function as expected.

Please provide more details and we would provide proper workaround for you.

Best Regards,

Barry
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

I am able to fix the issue
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

@v-bacao-msft : Thank You
Verified answer

v-bacao-msft Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @agupta1112,

It seems that you have solved your problem, please go ahead and mark your post as solved by clicking “Accept as Solution” so that this thread will be marked for other users to easily identify!

In addition, I am still curious as to why such errors occur. If it is convenient, could you briefly introduce the reasons and solutions for the errors? Curiosity drives.

Best Regards,

Barry
Verified answer

Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

My requirement was to send an email when a record is created in CRM. So instead of creating a flow directly, I was creating it through power apps therefore it was taking power apps as the default step. That was a very simple mistake.