Power app connected to Power Automate is asking for Plumsail API key when starting the app

Hello,
i have a Power Automate flow which is called from a Power App.

My users are now being asked to enter the Plumsail API key when they start the power app.

I checked the Power Automate connection, and looks ok.

Why is this happening now?
Been running ok for 12 months !

Hello @PaulP,

Could you try to copy the key in the Plumsail account - API keys section?

https://account.plumsail.com/documents/api-keys

Then paste the key in the Power Automate connection window.

Does it save the key or keep asking again when the flow runs?

Best regards,
Petr
Plumsail team

Good morning,

I'm also having the same issue. I have updated the API key in my Connections tab, but some users are not having the connection shared. This issue just started yesterday after working for a little over a year.

Hello @BHoke, @PaulP

We didn't change something on our side and it seems to be related to some Microsoft update.

We're researching the issue and I'll keep you posted about the results.

Best regards,
Petr
Plumsail team

Hello @BHoke, @PaulP,

Indeed, Microsoft changes the sharing option for some reason.
We'll research it further. In the meantime, please use the Documents custom connector. It can be shared.

Best regards,
Petr
Plumsail team

i created a custom connector, but i can not seem to link it to the plumsail control in power automate.
It does not allow the option to chhose the custom connector.
need more guidance

did you manage to get anything working?

Hi @PaulP,

If you added the custom connector try to select it in the Runtime dropdown in Power Automate

Best regards,
Petr
Plumsail team

I tried to use the custom connector suggestion, but it was going to change to a "Premium" connector and require additional licensing. So, I decided to change my trigger from a PowerApps trigger to a "When an item is created" trigger from SharePoint. I no longer have the flow inside my PowerApp. This seems to be working for me.

Hello everyone! :slight_smile:

I’m experiencing the same issues as described above:

  • Users are now required to provide an API key;
  • I tried the custom connector, but it requires a Premium license to work;
  • It must be instantaneous and uses other data than the SP List, so @BHoke's workaround won’t work for us.

This issue is currently preventing my 60 users from using the application.
Has anyone found a solution or an alternative workaround?
Any quick help would be greatly appreciated.

Hello @PJ27, @PaulP, @BHoke,

Microsoft has published the fix for this issue, and the connection should now be shareable again. Please let us know whether the issue is resolved on your end.