Hi ​@leeolee2833 

Try reaching out to Unshape Support for help with their Zap app integration.

https://www.unshape.app/bluesky-bot/#how-it-works

Hi ​@leeolee2833 

Here's the Zapier doc that might help: link

If you're still running into issues, drop a screenshot of the error and a quick description of what your Zap is doing, happy to take a look!

And if you'd rather just get it sorted quickly, I offer a free 20-min Zapier troubleshooting call. Book it under Resources on my Zapier Directory profile: https://zapier.com/partnerdirectory/automatemybiz

!-->

This usually means the app connection is broken on the Threads by Unshape side, not on your side.

Zapier is trying to log in, but the app is not sending back the access token it needs.

Since you already tried logging in again and changing browsers, this is probably an app bug or setup problem in Unshape’s Zapier connection.

So the simple answer is:

• it is likely not your mistake

• the app needs to fix their Zapier connection

• you may need to contact Unshape directly and show them this error:
  Field named access_token not found in OAuth2 results

Hi ​@leeolee2833 

Just checking in—were you able to get this resolved, or is the access token error still coming up when you try to connect?

If you're still running into issues, drop a screenshot of the error and a quick description of what your Zap is doing, happy to take a look!

And if you'd rather just get it sorted quickly, I offer a free 20-min Zapier troubleshooting call. Book it under Resources on my Zapier Directory profile: https://zapier.com/partnerdirectory/automatemybiz

!-->

This looks less like a browser issue and more like a broken app auth setup on the Threads by Unshape side. The Zapier error means Zapier completed the OAuth redirect, but the connection did not return an access_token in the auth result, so Zapier can’t finish connecting.

Since the app is still listed in Zapier, the integration exists, but this specific error usually has to be fixed by the app developer/provider, not by the end user.

So the practical answer is:

• retry in incognito once,
• remove and reconnect the account,
• but if the same access_token error remains, it’s likely an issue in Threads by Unshape’s Zapier OAuth configuration and only their team/Zapier support can resolve it.