Connecting to the Twitter API to use in a Logic App gives "Create and authorize OAuth connection failed"

keef urquhart 15 Reputation points


Recently noticed that my Twitter bot stopped on the 20th April, this was due to an error in the Twitter connector.

I created a new connection using "Use default shared application" but had the same problem.

I created my own Twitter app and used "Bring your own application" instead with the correct keys but still get the error "Create and authorize OAuth connection failed"

Is this because of recent changes to the Twitter API? Would love any tips on how to get my Logic App going again


Azure Logic Apps
Azure Logic Apps
An Azure service that automates the access and use of data across clouds without writing code.
2,898 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Sonny Gillissen 3,346 Reputation points

    Hi keef urquhart

    I've managed to test it in my test lab, and fix the issue.

    The problem lies with all the types of keys (I used my own app as the default wouldn't work at my end either). The Logic App Twitter Connector is asking for a 'Consumer Key' and 'Consumer Secret', however what you get when creating an app is a 'Client ID' and 'Client Secret'. This is necessary for the OAuth2 flow, however the Twitter Connector seems to still use the OAuth flow (so without the 2). Therefor you'll need other keys. When you go to the Developer Portal you can browse to your App, and then select the 'Keys and tokens' tab where you can click 'Regenerate' next to 'API Key and Secret'. This will provide you with a new 'Consumer Key' and 'Consumer Secret': User's image

    The newly provided keys can be added to your Logic App when choosing 'Bring your own application': User's image

    Then the connection should work. Please click "Accept answer" if you find this helpful. Feel free to drop additional queries in the comments below!

  2. Vinícius Neves Costa 0 Reputation points

    The same issue here. I even cleared my browser cache.
    User's image

    0 comments No comments