Clickup
157 operations0 webhooks
Clickup plugin for Corsair
Supported operations
- Channels CreateWrite
Create a chat channel
- Channels Create DmWrite
Create a direct message channel
- Channels Create LocationWrite
Create a location chat channel
- Channels DeleteDestructive
Delete a chat channel
- Channels FollowersRead-only
List followers of a chat channel
- Channels GetRead-only
Get a single chat channel
- Channels ListRead-only
List chat channels in a Workspace
- Channels MembersRead-only
List members of a chat channel
- Channels UpdateWrite
Update a chat channel
- Messages CreateWrite
Send a chat message
- Messages DeleteDestructive
Delete a chat message
- Messages ListRead-only
List messages in a chat channel
- Messages UpdateWrite
Update a chat message
- Reactions CreateWrite
React to a chat message
- Reactions DeleteDestructive
Remove a reaction from a chat message
- Reactions GetRead-only
List reactions on a chat message
- Replies CreateWrite
Reply to a chat message
- Replies GetRead-only
List replies to a chat message
- SubtypesRead-only
List post subtype IDs for a Workspace
- Tagged UsersRead-only
List users tagged in a chat message
FAQ
Install corsair and @corsair-dev/clickup, add the Clickup plugin, and connect with an API key. Then call methods like corsair.clickup.api.chat.channelsCreate() from your app. Corsair keeps each tenant isolated.
Yes. Clickup requires an API key from your Clickup account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.
Yes. One Corsair client can hit Clickup, GitHub, Notion, Stripe, and the rest. Trigger Clickup from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.
Teams use Corsair for clickup plugin for corsair. Common builds include sync jobs, admin tooling, and agents that call Clickup APIs from your backend.
The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Clickup API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.
We maintain @corsair-dev/clickup in the open repo. When Clickup ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.
No. Corsair does not read your Clickup data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Clickup data on your behalf.