1What FoxPlug reads from ClickUp
These are the exact things it reads, and nothing else.
| What | The details it takes |
|---|---|
| Your workspaces | the list of workspaces (teams) your token can see; the first 3 are read |
| Tasks finished in the window | tasks marked done since your last read (7 days on the first read), including closed ones; only tasks whose status type is closed are kept |
| Task id and name | the task id and its name, cut to 160 characters |
| Task tags | the names of the task's tags, used to decide feature, bug or other |
| Date done | when the task was marked done; becomes the moment's time |
| List or folder name | the name of the list the task is in, or its folder if no list, cut to 80 characters, shown in brackets |
2Moments it finds, and what each becomes
A moment is one thing that happened in ClickUp worth a second look. Each one is scored, then it becomes a post, a changelog entry, a thing to fix or an idea to email, or it is skipped.
A task tagged as a feature is finished
The moment is titled like this: Shipped: Add team invites
You finish a task 'Add team invites' tagged 'feature' in the list Sprint 14. FoxPlug writes 'Shipped: Add team invites' with 'A feature closed in ClickUp (Sprint 14): Add team invites.' The brain can offer it as a say card.
A task tagged as a bug is finished
The moment is titled like this: Fixed: Export button does nothing
You finish a task 'Export button does nothing' tagged 'bug'. FoxPlug writes 'Fixed: Export button does nothing' and keeps it as a changelog line, not a post.
A task with no feature or bug tag is finished
The moment is titled like this: Closed: Update the pricing doc
A task 'Update the pricing doc' with no tag is finished. FoxPlug writes 'Closed: Update the pricing doc', which is scored like any other update.
3How the brain uses it
The rules below are the ones that apply to ClickUp. The same rules, with worked examples, are on the brain page.
- A closed feature becomes a say line, 'Shipped: Dark mode'. How the brain decides
- A closed bug becomes 'Fixed:...' and is kept for the changelog. It is not a post, and a bug-only week adds to the Skip line. How the brain decides
- What counts as a bug or a feature is the labels and tags (ClickUp, GitHub) or the issue type (Jira). A bug tag wins over a feature tag. How the brain decides
4Set up ClickUp in a few steps
Access: personal API token, pasted by you. What to give it: personal API token (FoxPlug only reads).
- In ClickUp, open your avatar, then Settings, then Apps.
- Under API Token press Generate, or Regenerate if one exists (a new one replaces the old).
- Copy the token (it starts with pk_) and paste it into the ClickUp box in FoxPlug. Keep it private; FoxPlug only reads and never writes.
- Press Check for what's new.
5Limits worth knowing
Where it stops, so nothing surprises you.
- Reads the first 3 workspaces and only the first page of tasks (page 0) of each.
- Only tasks whose status type is closed count.
- Window: since your last read; on the first read the last 7 days.
- ClickUp tasks are sorted using tags only. A bug word (bug, defect, regression, hotfix, crash, incident, fix) wins over a feature word (feature, enhancement, improvement, story, epic, request, idea).
- On the first read after connecting, only the single newest finished task becomes a moment.
6What it never reads
Read only means read only, and the list below is what the code leaves alone.
- Assignee, comments and attachments
- Tasks that are not finished
- Anything it could write: only GET requests are made
7How ClickUp differs from the tools next to it
ClickUp versus Jira: both sort finished work into feature, bug or other. ClickUp uses a personal token, takes tasks marked done (status type closed) from up to 3 workspaces, and sorts by tags; Jira uses email plus API token on Jira Cloud, takes the Done status category, and sorts by issue type and labels. Versus Linear, Asana and Trello: those do not sort bugs from features.
8Questions
Does FoxPlug read who a ClickUp task is assigned to or its comments?
No. It reads the name, tags, list and when the task was finished. Assignee, comments and attachments are not read.
How does FoxPlug tell a feature from a bug in ClickUp?
By the task's tags. A tag containing a bug word wins over one containing a feature word. A task with neither is 'Closed'. Tag your finished tasks if you want 'Shipped' and 'Fixed' lines.
When does it read ClickUp?
Only when you press Check for what's new. Nothing is fetched on a timer for your project.
Has the ClickUp connection been tested against a real account?
No. It is marked code-path-only: the code path exists and its offline checks pass, but no real ClickUp workspace of ours has exercised it.
FoxPlug reads this tool only when you press Check for what's new, and only to read. Plans and limits are on the pricing page. Questions: support.