ClickUp tasks

What it does

Nexus creates ClickUp tasks for the client four ways: from a Google Sheet, from a pasted list, by planning a project from a brief, or by pulling action items out of meeting notes. Every way shows you a preview first (count, sample, and for plans a roadmap Google Sheet), and nothing is created until you approve.

Set it up

1. ✋ Pin the client's ClickUp list: "Pin this ClickUp list for the client: [url]." A link to any task in the list works. A link to a view of the list is not the list itself.
2. Assignees are matched against the team roster, so keep the roster current.

Use it

From a sheet or a pasted list. "Create ClickUp tasks from this sheet: [link]." Nexus parses every row and replies with the count and the first few tasks.

• Fold columns into the description by name or by letter: "Create ClickUp tasks from this sheet: [link], and put columns K and L in the description." When you use letters, Nexus first shows which header each letter is and waits for you to confirm, so a shifted column can't put the wrong text on every task.
• Add a prefix to every title: "Import these tasks and add TEST in front of each task name: [link]."
• Columns like Sprint Month, Phase or Workstream become ClickUp custom fields, not description text.

Plan a project from a brief. "Build a project plan for the website migration." Nexus drafts tasks grounded in the client's strategy and team, and delivers a roadmap Google Sheet to review. Say who owns what and it's honored: "anything SEO goes to Ana".

Roadmap from the strategy. "Build a roadmap from the client's G2M." Nexus reads the G2M first, then plans from it.

Action items from meeting notes. "Turn these meeting notes into a task plan." Paste the notes in the same message. For a meeting Nexus already ingested, see the meeting history guide.

Approve. "Approve, create all the tasks." One approval creates everything. To create only part: "Create only rows 1 to 10." Due dates that land on a weekend move to the next business day; name holidays and they're skipped too.

Copy recurring tasks to next month. "Duplicate the June sprint tasks for July." Nexus finds the tasks by their custom field, shows the copies it would make (same assignees, priority and description, new month, shifted dates), and creates them after you confirm.

One task at a time.

• "Create a ClickUp task to update the pricing page, due Friday." Nexus previews it, then creates it on your yes.
• "Move the pricing page task to next Tuesday."
• "Comment on the pricing page task: copy is approved."
• "What's overdue in the client's ClickUp?"

Troubleshooting

• Nexus says the proposal wasn't found. A plan or import is stored until it's used, so a yes hours later still works. If Nexus can't find it, ask it to parse the sheet again; you get a fresh preview.
• A custom field was dropped. The field name in the sheet doesn't match a field on the ClickUp list. Nexus names the field in its reply; add it to the list or rename the column.
• The sheet can't be read. Share it with the Google account your Nexus team gave you as Viewer.

Prompts

• "Pin this ClickUp list for the client: [url]."
• "Create ClickUp tasks from this sheet: [link]."
• "Create ClickUp tasks from this sheet: [link], and put columns K and L in the description."
• "Import these tasks and add TEST in front of each task name: [link]."
• "Build a project plan for the website migration."
• "Build a roadmap from the client's G2M."
• "Turn these meeting notes into a task plan."
• "Approve, create all the tasks."
• "Create only rows 1 to 10."
• "Duplicate the June sprint tasks for July."
• "Create a ClickUp task to update the pricing page, due Friday."
• "Move the pricing page task to next Tuesday."
• "Comment on the pricing page task: copy is approved."
• "What's overdue in the client's ClickUp?"

Machine twins: /help/clickup-tasks.json · /help/clickup-tasks.md · /help.json · /llms.txt

Reviewed 2026-10-15. In Slack, ask Nexus how do I … and it answers from this guide, with where your company stands.