ClickUp OAuth2 API

Questions
,
1

Describe the problem/error/question

I am trying to connect ClickUp to n8n using the ClickUp OAuth2 API credential.
After clicking “Connect” and logging in to ClickUp, I am redirected back and see this message in ClickUp:

“Whoops! Unable to authorize your teams. Please try again.”

Because of this, the OAuth2 process never completes and the credential in n8n does not become “connected”.

I contacted ClickUp support. They mentioned that since n8n is not a native ClickUp integration, the n8n team should first confirm whether the issue is caused by the OAuth flow or configuration on the n8n side. They can support further once n8n can provide logs or technical details about the failed OAuth handshake.

What is the error message (if any)?

On the ClickUp side:
“Whoops! Unable to authorize your teams. Please try again.”

In n8n Cloud there is no detailed error shown in the UI for the credential.

Please share your workflow

I cannot share a workflow because I cannot create one.  
The ClickUp credential cannot be connected, so I cannot add or configure any ClickUp nodes in a workflow.

Information on your n8n setup

n8n version:
1.121.2 Starter license

Database:
SQLite (default)

n8n EXECUTIONS_PROCESS:
own (default)

Running n8n via:
n8n Cloud

Operating system (local machine):
macOS 14.1 Sonoma
<<>>

Additional information

The only thing I have been able to verify is:

  1. The ClickUp OAuth app is created and active.

I have not modified anything else yet.
I would like to understand whether this issue is caused by the n8n Cloud OAuth configuration, the redirect URL handling, or something else.

If you can let me know which logs n8n Cloud can provide, I can share them so we can identify where the authorization process is failing.

1 Like
2

Hey @DJKD reach out to N8n team via email.

3

I’m experiencing the same issue rn, did you manage to get it solved?

4

Just worked it out a solution I think - instead of setting it up as Oauth2, do it as a personal token

ClickUp > Settings > Apps > API Token > Generate

2 Likes
5

I’ve been in contact with ClickUp support and they’ve confirmed that the problem probably is on their side. They are currently investigating it. I’ll update this thread once I hear more from them.

1 Like
6

@DJKD any update on this, i’m also unable to authenticate clickup on a self hosted platform with netiher access token nor OAuth 2 credentials

7

Unfortunately, no update yet. They also haven’t given a timeframe for when the problem will be resolved. I’ll follow up on it again.

8

I have been in contact with ClickUp and wanted to share an update here.

ClickUp indicated that at this moment there is no update on the timeline for when this issue will be fixed or moved into the next development stage. They have escalated the follow up internally to their Technical Impact Manager to make sure the impact and concerns are visible.

I have shared the link to this forum thread with ClickUp as requested.

If anyone else reading this thread is experiencing the same issue, please leave a short message here. This helps ClickUp understand how many users are affected and how big the impact of this issue is.

Thanks everyone.

9

Having same issue here. Any workaround you found other than using a pErsonal Token?

10

Hi, I have the same problem

11

Same issue here.

12

Same issue here!

13

Same issue here too

14

I am experiencing the same issue, even when using a personal token I get an Oauth error

15

After coming across this while I was trying to “fix” things, let me write you guys something that might solve a few problems: triple- or quadruple-check if your data is correct. n8n mumbles something about a refreshToken, but that’s not the issue. Under the hood, your input data was wrong. I for example was entirely sure that I put in the correct ID for the space I wanted to access and I ended up giving it the workspace ID. This also happens with AI Agents a lot. They mess up. So make sure that you’re using the correct data. Also double check in swagger UI. I ended up actually creating the Bearer token manually to verify which thing in the chain of events was messing things up. And it’s n8n and ClickUp at the same time. ClickUp will also give you some BS about missing OAuth Tokens when in fact you were just accessing something that doesn’t exist.

I hope this helps somebody. I could get my workflow back to function by just getting the test-data right again. And don’t tell me you’re certain because it worked before :slight_smile: I know for a fact that this gets messy with tons and tons of IDs you’re handling and I myself was 100% sure that my data was correct.

16

Having the same issue, did anyone already solve this?

17

@Maximvd
Which version of n8n are you currently running?

There is an ongoing issue on github regarding oAuth: ClickUp - OAuth2 Connection Error · Issue #22051 · n8n-io/n8n · GitHub

I can confirm that on Cloud version 2.4.1 and 2.4.4 oAuth does not work.
But the API key does work for me.

On self-hosted with version 1.123.6 oAuth and API key do both work.

1 Like
18

Using the Cloud version, seems like this has been a problem for a while now.

I did manage to get it working with the API, but after sometime it also starts rejecting that one.

Let’s see how long it lasts.

1 Like