Share
Report
37Bad 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:
- I'm running a MacBook, so I don't have access to Power Automate for desktop.
- My Virtual Agent is running entirely in the Virtual Agent Teams app — I'm a noob to Virtual Agents. I have not exported the bot to https://powervirtualagents.microsoft.com/
- I have a Power Automate flow successfully running with a custom Twitter connection, so I can confirm that solution works.
Any thoughts? The community's help is always appreciated!
All responses (
Answers (
