Automatically enabled when you configure ClickUp permissions in your agent workflow.
What it does
- Find the Space, Folder or List an agent works in, and search tasks there by status, assignee, tag, dates or Custom Field
- Read a task with its subtasks, checklists, Custom Fields, comments and attachments
- Create tasks and subtasks, and set assignees, status, priority, due dates, tags and Custom Field values
- Add and tick checklist items, comment on tasks, and attach files
- Read ClickUp Docs and their pages, add a page, and add to one
- Log time, update goals, and manage Lists, Folders and views, as the permission groups allow. Safety Controls below lists what always asks
Choose where each agent works
Name the Space, Folder or List in the agent’s instructions, for example “Create onboarding tasks in the List Onboarding in the Space Service Desk”. The agent finds it by name and works there. To keep every agent out of a part of your Workspace, connect ClickUp with the token of a user who cannot open that part: ClickUp itself then refuses each call there.Start an agent on ClickUp changes
ClickUp events do not start a Neo agent. Run the agent on a schedule, for example every 15 minutes: each run asks ClickUp for the tasks created or changed since the last run, in the Lists it watches, and acts on each one. Tell it in its instructions which changes to act on, such as “a task moved to Ready for Neo”.Permission groups
Each group can be Disabled, Read Only or Read / Write, with or without a technician’s approval for changes.
Safety Controls
These always ask a technician, whatever the profile:- Deleting a Space, a Folder or a List, which deletes every task in it
- Every change to Workspace members and guests, user groups, guest access and sharing, because each can add a paid seat or open data to someone
- Making a Space no longer private, or creating or changing a Doc or a Chat channel with any visibility but private
- Creating or updating a webhook, which sends Workspace data to an outside address
