clickup-ci-integration
Set up CI/CD pipelines for ClickUp API integrations with GitHub Actions, automated testing, and task status sync. Trigger: "clickup CI", "clickup GitHub Actions", "clickup automated tests", "CI clickup integration", "clickup pipeline", "clickup CI/CD".
Best use case
clickup-ci-integration is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Set up CI/CD pipelines for ClickUp API integrations with GitHub Actions, automated testing, and task status sync. Trigger: "clickup CI", "clickup GitHub Actions", "clickup automated tests", "CI clickup integration", "clickup pipeline", "clickup CI/CD".
Teams using clickup-ci-integration should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/clickup-ci-integration/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How clickup-ci-integration Compares
| Feature / Agent | clickup-ci-integration | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Set up CI/CD pipelines for ClickUp API integrations with GitHub Actions, automated testing, and task status sync. Trigger: "clickup CI", "clickup GitHub Actions", "clickup automated tests", "CI clickup integration", "clickup pipeline", "clickup CI/CD".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# ClickUp CI Integration
## Overview
Automate ClickUp integration testing in CI and sync task statuses from your pipeline. Uses GitHub Actions with live API testing against ClickUp API v2.
## GitHub Actions Workflow
```yaml
# .github/workflows/clickup-integration.yml
name: ClickUp Integration Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
jobs:
unit-tests:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- run: npm ci
- run: npm test -- --coverage
integration-tests:
runs-on: ubuntu-latest
needs: unit-tests
env:
CLICKUP_API_TOKEN: ${{ secrets.CLICKUP_API_TOKEN }}
CLICKUP_TEST_LIST_ID: ${{ secrets.CLICKUP_TEST_LIST_ID }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- run: npm ci
- name: ClickUp API health check
run: |
STATUS=$(curl -s -o /dev/null -w "%{http_code}" \
https://api.clickup.com/api/v2/user \
-H "Authorization: $CLICKUP_API_TOKEN")
if [ "$STATUS" != "200" ]; then
echo "::warning::ClickUp API returned $STATUS, skipping integration tests"
exit 0
fi
- name: Run integration tests
run: CLICKUP_LIVE=1 npm run test:integration
```
## Configure Secrets
```bash
# Store ClickUp token in GitHub Secrets
gh secret set CLICKUP_API_TOKEN --body "pk_12345678_YOUR_TOKEN"
# Store test list ID (for integration tests to create/delete test tasks)
gh secret set CLICKUP_TEST_LIST_ID --body "900100200300"
```
## Integration Test Suite
```typescript
// tests/integration/clickup-ci.test.ts
import { describe, it, expect, afterAll } from 'vitest';
const TOKEN = process.env.CLICKUP_API_TOKEN!;
const TEST_LIST = process.env.CLICKUP_TEST_LIST_ID!;
const BASE = 'https://api.clickup.com/api/v2';
const createdTaskIds: string[] = [];
async function api(path: string, options?: RequestInit) {
const res = await fetch(`${BASE}${path}`, {
...options,
headers: { 'Authorization': TOKEN, 'Content-Type': 'application/json', ...options?.headers },
});
return { status: res.status, data: await res.json() };
}
describe('ClickUp API Integration', () => {
it('authenticates successfully', async () => {
const { status, data } = await api('/user');
expect(status).toBe(200);
expect(data.user.id).toBeDefined();
});
it('creates a task in test list', async () => {
const { status, data } = await api(`/list/${TEST_LIST}/task`, {
method: 'POST',
body: JSON.stringify({
name: `CI Test Task - ${new Date().toISOString()}`,
description: 'Created by CI pipeline, safe to delete',
priority: 4,
}),
});
expect(status).toBe(200);
expect(data.id).toBeDefined();
createdTaskIds.push(data.id);
});
it('reads the created task', async () => {
const { status, data } = await api(`/task/${createdTaskIds[0]}`);
expect(status).toBe(200);
expect(data.name).toContain('CI Test Task');
});
afterAll(async () => {
// Cleanup: delete test tasks
for (const id of createdTaskIds) {
await api(`/task/${id}`, { method: 'DELETE' });
}
});
});
```
## Sync CI Status to ClickUp Task
```typescript
// scripts/update-clickup-task.ts
// Run after deploy: npx tsx scripts/update-clickup-task.ts TASK_ID "deployed"
async function updateTaskFromCI(taskId: string, newStatus: string) {
const response = await fetch(
`https://api.clickup.com/api/v2/task/${taskId}`,
{
method: 'PUT',
headers: {
'Authorization': process.env.CLICKUP_API_TOKEN!,
'Content-Type': 'application/json',
},
body: JSON.stringify({ status: newStatus }),
}
);
if (!response.ok) {
console.error(`Failed to update task ${taskId}:`, await response.text());
process.exit(1);
}
console.log(`Task ${taskId} status updated to "${newStatus}"`);
}
const [taskId, status] = process.argv.slice(2);
updateTaskFromCI(taskId, status);
```
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Secret not found | Missing GitHub secret | `gh secret set CLICKUP_API_TOKEN` |
| 401 in CI | Token expired/rotated | Update secret value |
| Rate limited in CI | Too many test runs | Add pre-flight rate check |
| Integration test cleanup fails | Task already deleted | Ignore 404 on cleanup |
## Resources
- [GitHub Actions Secrets](https://docs.github.com/en/actions/security-for-github-actions/security-guides/using-secrets-in-github-actions)
- [ClickUp API Reference](https://developer.clickup.com/)
## Next Steps
For deployment patterns, see `clickup-deploy-integration`.Related Skills
running-integration-tests
Execute integration tests validating component interactions and system integration. Use when performing specialized testing. Trigger with phrases like "run integration tests", "test integration", or "validate component interactions".
workhuman-deploy-integration
Workhuman deploy integration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman deploy integration".
workhuman-ci-integration
Workhuman ci integration for employee recognition and rewards API. Use when integrating Workhuman Social Recognition, or building recognition workflows with HRIS systems. Trigger: "workhuman ci integration".
wispr-deploy-integration
Wispr Flow deploy integration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr deploy integration".
wispr-ci-integration
Wispr Flow ci integration for voice-to-text API integration. Use when integrating Wispr Flow dictation, WebSocket streaming, or building voice-powered applications. Trigger: "wispr ci integration".
windsurf-ci-integration
Integrate Windsurf Cascade workflows into CI/CD pipelines and team automation. Use when automating Cascade tasks in GitHub Actions, enforcing AI code quality gates, or setting up Windsurf config validation in CI. Trigger with phrases like "windsurf CI", "windsurf GitHub Actions", "windsurf automation", "cascade CI", "windsurf pipeline".
webflow-deploy-integration
Deploy Webflow-powered applications to Vercel, Fly.io, and Google Cloud Run with proper secrets management and Webflow-specific health checks. Trigger with phrases like "deploy webflow", "webflow Vercel", "webflow production deploy", "webflow Cloud Run", "webflow Fly.io".
webflow-ci-integration
Configure Webflow CI/CD with GitHub Actions — automated CMS validation, integration tests with test tokens, and publish-on-merge workflows. Use when setting up automated testing or CI pipelines for Webflow integrations. Trigger with phrases like "webflow CI", "webflow GitHub Actions", "webflow automated tests", "CI webflow", "webflow pipeline".
vercel-deploy-integration
Deploy and manage Vercel production deployments with promotion, rollback, and multi-region strategies. Use when deploying to production, configuring deployment regions, or setting up blue-green deployment patterns on Vercel. Trigger with phrases like "deploy vercel", "vercel production deploy", "vercel promote", "vercel rollback", "vercel regions".
veeva-deploy-integration
Veeva Vault deploy integration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva deploy integration".
veeva-ci-integration
Veeva Vault ci integration for REST API and clinical operations. Use when working with Veeva Vault document management and CRM. Trigger: "veeva ci integration".
vastai-deploy-integration
Deploy ML training jobs and inference services on Vast.ai GPU cloud. Use when deploying GPU workloads, configuring Docker images, or setting up automated deployment scripts. Trigger with phrases like "deploy vastai", "vastai deployment", "vastai docker", "vastai production deploy".