How to Map a ClickUp Hierarchy and Custom Fields from a Workflow

ClickUp maps rot when they add Story Points and a Slack automation you never connected. Lists and fields only from the brief. Not Notion.

The matching generator is the ClickUp Hierarchy and Custom Fields from a Workflow prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).

Tree Space then lists, no extra folders

Turn a workflow description into a ClickUp space, folder, list, and custom-field map. No invented statuses, users, or automations. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.

Paste these fields before you hit run:

Workspace and Space name I own: [Workspace]
Workflow stages I actually use: [Stages]
Lists I want (one job type per list): [Lists]
Custom fields I can prove (type + name): [Fields]
Members I may assign (emails as pasted): [Members]
Statuses per list I can prove: [Statuses]
Automations I allow (or NONE): [Autos]
What must never be a field: [Never]
Words I must not use: [Banned]
Sprint or points I use (or NONE): [Sprint]

That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.

Statuses only the set you pasted

Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.

Walk the Generate list in order:

1. Honesty ledger: workspace, stages, lists, fields, members, statuses, autos. Forbidden: users and fields not listed.
2. Tree: Space -> folders if Inputs grouped them -> lists from Lists. Do not add a folder the brief did not name.
3. Status map: each list gets only Statuses. Do not copy Scrum defaults if Statuses is a custom set.
4. Field table: name, type, which list. Types only from Fields. Never-list stays out.
5. People: assign only Members emails. If a list has no member, leave unassigned.
6. Autos: only Autos. If NONE, write no ClickUp automations in this pack.
7. Sprint: only Sprint. If NONE, omit points and sprints.
8. Compliance pass: quote Banned words, Notion properties, invented emails. Cut them.

If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.

If Autos is NONE, skip automations

Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.

Honor the constraints as hard stops, not vibes:

• ClickUp hierarchy and fields only. Not Notion, Airtable, Jira, or Linear.
• Never invent a member, status, or custom field.
• If Autos is NONE, do not add automations.
• If Sprint is NONE, do not add sprint points.
• No emojis.

When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.

Not Notion, Airtable, Jira, or Linear

Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.

Tags on the card (clickup hierarchy custom fields, clickup space folder list, clickup workflow map) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.

Fill the card, then run

Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.