Allow API Keys that Perform Actions as ClickBot or an API Bot instead of the User Account
Michael Wells
We currently use the API to integrate ClickUp with custom enterprise software systems and databases. Currently, the API actions have to be performed under a user account so all of these automated actions appear to be from a single user. It would be useful for the workspace owner to be able to generate an API Key where the actions are shown to be performed by an API Bot, similar to how automations show that they are performed by ClickBot.
Log In
A
Andrew Seme
I would very much appreciate this feature being added. It’s not good practice to use one user account with super admin permissions to do all actions on the api. Plus it forces me to have all spaces visible to be which clutters my views. Please make this a priority.
F
Fabian Jura
We are new to ClickUp and just started with some API integrations. I was also very surprised it is only possible to use the API in a specific user context.
Creating tasks via the API from some external systems looks very odd as they all show my name.
We definitely need a solution for this as well.
S
Stefano Iavarone
Here's a simple solution Clickup team can easily implement until a proper solution is found:
Allow each Clickup account owner to create one free user dedicated to APIs only. This user would be on the same plan as the account owner but could only access Clickup via API and have view access via GUI/app. This would restrict Clickup account owners from using this user as a typical user and instead only use it for dedicated system changes (API/webhooks).
This user will NOT count as a charged user, because it's basically a fix to the current problem at hand. Other competitors offer a solution to system changes / API / webhooks being visible as system (not user) changes without any additional cost, so it's only fair to do the same.
James Hogg
I can't believe this is not just available. I do not want to add a User named BotBot and have that coming up when people search to add an Assignee etc. Why should CustomForms in ClickUp have their own bot, but integrations be forced to authenticate with a user account.
N
Nick Rotundo
This is the closest to what I would like, which is just keys that can be revoked without messing up a lot of things. At least if it was tied to one "integration" account, it could be more easily managed.
Kasper Dam
We use a dedicated seat for this that we just named ClickUp Bot, and paying for that seat. Certainly not ideal, and a lacking feature compared to other platforms, but gets the job done.
R
Rob Fitzgerald
Agree - we use workato to fill in gaps in CU automation abilities and that user ends up "watching" every task making it hard to properly use the tool themselves.
Janessa Christine
Agree with this, adding comments as a user via automation skews up my activity data and reporting.