clickup-security-basics

Apply ClickUp security best practices for secrets and access control. Use when securing API keys, implementing least privilege access, or auditing ClickUp security configuration. Trigger with phrases like "clickup security", "clickup secrets", "secure clickup", "clickup API key security".

claude-code
3 Tools
clickup-pack Plugin
saas packs Category

Allowed Tools

ReadWriteGrep

Provided by Plugin

clickup-pack

Claude Code skill pack for ClickUp (24 skills)

saas packs v1.0.0
View Plugin

Installation

This skill is included in the clickup-pack plugin:

/plugin install clickup-pack@claude-code-plugins-plus

Click to copy

Instructions

ClickUp Security Basics

Overview

Security best practices for ClickUp API keys, tokens, and access control.

Prerequisites

  • ClickUp SDK installed
  • Understanding of environment variables
  • Access to ClickUp dashboard

Instructions

Step 1: Configure Environment Variables


# .env (NEVER commit to git)
CLICKUP_API_KEY=sk_live_***
CLICKUP_SECRET=***

# .gitignore
.env
.env.local
.env.*.local

Step 2: Implement Secret Rotation


# 1. Generate new key in ClickUp dashboard
# 2. Update environment variable
export CLICKUP_API_KEY="new_key_here"

# 3. Verify new key works
curl -H "Authorization: Bearer ${CLICKUP_API_KEY}" \
  https://api.clickup.com/health

# 4. Revoke old key in dashboard

Step 3: Apply Least Privilege

Environment Recommended Scopes
Development read:*
Staging read:*, write:limited
Production Only required scopes

Output

  • Secure API key storage
  • Environment-specific access controls
  • Audit logging enabled

Error Handling

Security Issue Detection Mitigation
Exposed API key Git scanning Rotate immediately
Excessive scopes Audit logs Reduce permissions
Missing rotation Key age check Schedule rotation

Examples

Service Account Pattern


const clients = {
  reader: new ClickUpClient({
    apiKey: process.env.CLICKUP_READ_KEY,
  }),
  writer: new ClickUpClient({
    apiKey: process.env.CLICKUP_WRITE_KEY,
  }),
};

Webhook Signature Verification


import crypto from 'crypto';

function verifyWebhookSignature(
  payload: string, signature: string, secret: string
): boolean {
  const expected = crypto.createHmac('sha256', secret).update(payload).digest('hex');
  return crypto.timingSafeEqual(Buffer.from(signature), Buffer.from(expected));
}

Security Checklist

  • [ ] API keys in environment variables
  • [ ] .env files in .gitignore
  • [ ] Different keys for dev/staging/prod
  • [ ] Minimal scopes per environment
  • [ ] Webhook signatures validated
  • [ ] Audit logging enabled

Audit Logging


interface AuditEntry {
  timestamp: Date;
  action: string;
  userId: string;
  resource: string;
  result: 'success' | 'failure';
  metadata?: Record<string, any>;
}

async function auditLog(entry: Omit<AuditEntry, 'timestamp'>): Promise<void> {
  const log: AuditEntry = { ...entry, timestamp: new Date() };

  // Log to ClickUp analytics
  await clickupClient.track('audit', log);

  // Also log locally for compliance
  console.log('[AUDIT]', JSON.stringify(log));
}

// Usage
await auditLog({
  action: 'clickup.api.call',
  userId: currentUser.id,
  resource: '/v1/resource',
  result: 'success',
});

Resources

Next Steps

For production deployment, see clickup-prod-checklist.

Ready to use clickup-pack?