Skip to main content
Integrations · ClickUp
A Guild agent can create, triage, and update work in ClickUp without leaving your team’s existing processes. Guild stores the ClickUp API key server-side and injects it into every request, so agent code never sees the credential. Credential policies let you restrict which operations each agent may call, and every request runs through Guild’s audit trail.

Book a demo

See how teams govern agents that use ClickUp.

Talk to sales

Get access to Guild, then connect ClickUp to your first agent.

What the ClickUp integration exposes

The tools cover tasks, comments, checklists, custom fields, time entries, and task dependencies. They also reach workspace structure: spaces, folders, lists, goals, views, webhooks, and user or guest permissions. Tools follow the clickup_ prefix and ship in the guildai~clickup package. Use pick() to give an agent only the subset it needs.

How it works

1

Get your ClickUp API key

Generate a personal API token from your ClickUp account settings. The token starts with pk_.
2

Connect the credential in Guild

In Guild, go to Access & setup > Credentials, click Connect, select clickup, and paste the key into API Key. See Credentials for workspace, member, and agent-scoped options.
3

Import and configure the tools

Import ClickupTools from @guildai-services/guildai~clickup and spread the tools into your llmAgent definition. Guild sends the key as Authorization: <key> on every outbound request.

Why ClickUp access needs governing in an agent context

ClickUp tools can delete tasks, remove users from a workspace, revoke guest access, and tear down workspace structure. A credential scoped to an agent limits blast radius: Guild supports account, workspace, member, and agent-scoped credentials, so you can give a triage agent a credential that cannot touch spaces or goals. See Credentials for scoping options. Credential policies add a second layer. Guild’s proxy evaluates ALLOW and DENY rules before any request leaves the platform, matching on operation name, HTTP method, agent, and workspace. A policy can block all clickup_delete_* operations while permitting read and update calls, or restrict destructive tools to one workspace. Because the credential is injected server-side only after the policy check passes, an agent cannot bypass it. See Credential policies for rule syntax. Without scoped rules the default posture is allow-all, so adding a targeted DENY is the fastest way to harden a new deployment.

About the ClickUp integration

Agents can create, update, and delete tasks, lists, folders, spaces, and goals within a ClickUp workspace. They can manage comments, checklists, custom fields, time entries, and task dependencies. Workspace structure, views, webhooks, and user or guest permissions can also be configured. The integration is guildai~clickup.

Authentication

  • Type: API key
  • Header: Guild sends the key as Authorization: <key>

Setup

1

Connect ClickUp

In Guild, go to Access & setup > Credentials, click Connect, select clickup, and paste the key into API Key.
See Credentials for workspace, member, and agent-scoped credentials.

Usage

Selecting specific tools

Tools are named with the clickup_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildai~clickup:

Frequently asked questions

No. The catalog entry for guildai~clickup lists no webhook events, so the integration does not deliver inbound ClickUp events to Guild triggers. The clickup_create_webhook and clickup_update_webhook tools let an agent register webhooks on the ClickUp side, but Guild does not consume those callbacks.
Write a credential policy with a DENY rule targeting clickup_delete_task and scope it to the agent that should be restricted. The other agent, using the same credential, is unaffected because the DENY rule matches only the agent you specified. See Credential policies.
Yes. Connect an account-level credential for the default and then connect a workspace-scoped credential in any workspace that needs a different ClickUp account. Guild picks the most specific credential in scope when an agent makes a call. See Credentials for the full resolution order.
No. Guild stores the key and adds it as the Authorization header server-side inside the credential proxy. The key never enters agent code, the container, the prompt, or agent state.

Put a governed agent on ClickUp this week

Book a demo

See how teams govern agents that use ClickUp.

Talk to sales

Get access to Guild, then connect ClickUp to your first agent.
Also runs on Guild: Asana · Google Calendar · Jira · monday.com Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 10, 2026