Request - When a HTTP Request is received not found in the Community plan

[westerdaled]

Hi

I want test out putting a json message in an Azure queue using the "Http Request is received trigger".

Next, I  switched to the my personal community dev plan environment  and select create from blank. However, I can't locate the trigger. Request - When a HTTP Request is received .  

Is this a limitation of the personal community plan?  On my live tenant / environment I guess I would be looking at a per user plan https://unitedkingdom.flow.microsoft.com/en-us/pricing/?currency=GBP

[Jcook]

Hi @westerdaled 

The Http Actions/Triggers are Premium connectors. This requires a Flow Plan1/2 or higher

[westerdaled]

@Jcook

Thanks, for replying. I suspected that, in my Office 365 E3 environment however, the community dev environment does have premium connectors. Seemingly, not the ones I want to test out 😩

[Jcook]

Hi @westerdaled 

Glad I could help!

What connector are you looking for specifically. I am able to see HTTP request

[westerdaled]

@Jcook 

Now this is a conundrum 🤔, 

For my logged in account,  I have now set up Power Automate personal environments on 1) my live tenant and 2) a developer tenant as shown below:

 

Neither is showing this trigger - also searched for HTTP  in the connectors list and as you can see this is limited.  

Is there a config option I need to enable?

I thought the personal environment is the community developer plan for an existing user. 

[westerdaled · Accepted solution]

@Jcook 

I think I have worked out the issue: you need to skip the screen I showed above as apparently that just shows a small subset of the available triggers.

Thereafter,  you get to the good stuff - man that was intuitive - not 🙄

[Jcook]

Hello @westerdaled 

I am glad you got it figured out.

if your answer has been solved. Could you mark the post that solved your issue. This is to help others find the answer more quickly.

Thanks, and seat safe!

[westerdaled]

@Jcook 

I found this issue when following some official guidance: a step had been missed in the instructions.  I have now corrected this.