| name | clickup-multi-env-setup |
| description | Configure ClickUp API access across dev, staging, and production environments
with per-environment tokens and workspace isolation.
Trigger: "clickup environments", "clickup staging", "clickup dev prod",
"clickup environment setup", "clickup config by env", "clickup multi-env".
|
| allowed-tools | Read, Write, Edit, Bash(aws:*), Bash(gcloud:*), Bash(vault:*) |
| version | 1.6.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","productivity","clickup"] |
| compatibility | Designed for Claude Code |
ClickUp Multi-Environment Setup
Overview
Configure separate ClickUp workspaces and API tokens for development, staging, and production. ClickUp does not have sandbox environments, so the recommended approach is separate workspaces with separate tokens per environment.
Environment Strategy
| Environment | Workspace | Token | Rate Limit | Purpose |
|---|
| Development | Dev workspace | Personal token | 100 req/min | Local development, testing |
| Staging | Staging workspace | Service token | 100 req/min | Integration testing, QA |
| Production | Production workspace | Service token | Per plan | Live traffic |
Key point: All ClickUp API calls go to https://api.clickup.com/api/v2/ regardless of environment. Environment isolation comes from using different tokens that are authorized for different workspaces.
Configuration
interface ClickUpEnvConfig {
token: string;
teamId: string;
defaultListId?: string;
timeout: number;
retries: number;
cacheEnabled: boolean;
cacheTtlMs: number;
}
function getClickUpConfig(): ClickUpEnvConfig {
const env = process.env.NODE_ENV ?? 'development';
const base = {
timeout: 30000,
: ,
: ,
: ,
};
(env) {
:
{
...base,
: (),
: (),
: ,
: ,
};
:
{
...base,
: (),
: (),
};
:
{
...base,
: (),
: process.. ?? ,
: ,
};
}
}
(): {
value = process.[key];
(!value) ();
value;
}