Api Apps should have a 'bot' setting
not on the roadmap
Ray
when making api calls from an authed api client, it should allow a query to be passed up that specifies the 'app' as the issuer of an action, as opposed to the 'apps' authorizer. ie. when the api makes a comment, the comment says "'my-app-name' commented" in the history actions feed.
Log In
Matt Belanger
This one is important to us. Seeing the username on an API call that was done with a Personal Access Token makes sense. Seeing the username of the person who created the API App, as the user performing the action, does not make sense.
Further, what happens if the User who created the API App leaves the organization? Does the API App break? I would hope the App works independently of the User, but seeing their signature on the App's actions has me doubting this.
Canny AI
Merged in a post:
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.
Canny AI
Merged in a post:
Non-user API Key / Changes display as API rather than Account User
Sébastien Delvaux
ClickUp should offer a "global" API key for the workspace so that changes made via the API are displayed as such rather than coming from the user, which can not only create confusion with users, but also cause a notification barrage for that user who generated the API key. This would also be solved if Custom Apps showed the app name rather than user's name when making a change.
Canny AI
Merged in a post:
Global API Key / not tied to user
D
Drew Tumblin
Would be very nice to be able to make API requests with a name representing the Company as a whole, maybe as a 'ClickUp bot' account, or even give us an option for a 'ClickUp API Key: Display Name'.
It is not a good look for us to our users when they see '<my_user> changed <custom field> from <this> to <that>' when it was actually an automated change / message.
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.
F
Fabian Jura
We would also need this feature!
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.
Load More
→