You’re offline. This is a read only version of the page.
Announcements
37
Bad news: Twitter is blocking the standard Power Automate actions because of the dispute with Microsoft over advertising. Boo.
Good news: the good folks in the Power Automate community came up with a solution that works in Power Automate: creating a dev app in Twitter and using that for a custom Twitter connection in automate. Yay!
That said, more bad news: I can't get the custom connection to work in the Virtual Agents Teams app. When I add a Twitter action to a flow in Virtual Agents in the Virtual Agents Teams app, the options are Use default shared application or Bring your own application, for which you can add the key and secret for your app from dev.twitter.
Both options are currently giving me the same error:
"Failed to create connection for connection id '/providers/Microsoft.PowerApps/apis/shared_twitter/connections/shared-twitter...'. error putting existing connection for connector /providers/Microsoft.PowerApps/apis/shared_twitter"
A few notes and limitations:
Any thoughts? The community's help is always appreciated!
Solved! At the top right of https://make.powerautomate.com/, I changed my environment to the environment associated with the Teams channel for my Virtual Agent and found the flows for that Virtual Agent. There, I once again followed the instructions linked here to create a custom connection in that environment and used that custom connection in my flow.
Share
Report
All responses (
Answers (
