How to connect ClickUp to Google Sheets with columns that stay stable

To connect ClickUp to Google Sheets with stable columns, decide the column set first, map each list's fields onto it by field identifier, and report any list that cannot supply a column. An export that discovers columns from the data comes out ragged, because ClickUp defines custom fields and statuses per list.

The fixed-column approach turns a confusing sheet with many empty cells into a configuration problem somebody can solve.

Key takeaways

• ClickUp custom fields and statuses are defined per list, so a field with the same name in two lists is two different fields.
• Fix the column set before you export, then map each list onto it by field identifier.
• Keep the mapping in its own sheet and publish a report of unmapped lists next to the data.
• Time in current status is a better health signal than the status itself.
• Decide whether subtasks are included, say which you chose, and mark subtask rows in a column.

What we'll cover

• Why does the sheet come out ragged?
• How do you fix the columns and map to them?
• How do you build it with CodeWords?
• What belongs in the sheet?
• How do you report time in status?
• How do you handle subtasks and double counting?
• Which field types arrive awkwardly?
• What reporting will people act on?
• How do you keep the export reliable?
• What are the limits?
• What should you set up first?
• Frequently asked questions

Why does the sheet come out ragged?

The sheet comes out ragged because ClickUp configuration differs between lists. An export from one list is straightforward, but an export that spans several lists meets five differences:

• Custom fields are per list. A field called "Priority" in two lists has two identifiers and possibly two option sets.
• Statuses are per list or per space. A single status column can hold values that are not comparable across lists.
• Option sets differ. Two "Priority" dropdowns may offer different options, so grouping by the column mixes scales.
• Some lists have no equivalent field. The empty cells look like missing data, when the field is missing.
• The hierarchy is uneven. Folders are optional, so a "Folder" column is blank for lists that sit directly in a space.

An export that discovers columns from the data reflects all of this faithfully and unusably. Decide the columns first.

How do you fix the columns and map to them?

Fix the columns by writing down what the report needs, then mapping each list's fields onto that set by field identifier. This is the approach that produces a usable sheet.

• Write down the columns the report needs. Usually these are name, status, assignee, due date, one or two custom fields, and the source list.
• Map each list explicitly, by field identifier.
• Keep the mapping in a sheet of its own. Whoever owns the lists can then see and maintain it, without asking somebody to change an automation.
• Report the lists you could not map, with the missing column. This report tells somebody exactly what to configure.
• Normalize the values. If one list says "Urgent" and another says "P1", map both to a common vocabulary.
• Never invent a value to fill a gap. An empty cell with a clear explanation beats a plausible guess.

How do you build it with CodeWords?

Build it in CodeWords by describing the export to Cody, the automation builder, in plain language. CodeWords connects to 3,000+ integrations (CodeWords pricing page, 2026), and you make the connection once and reuse it.

1. Open CodeWords and start a new automation.
2. Describe to Cody which lists, which fixed columns and which sheet.
3. Authorize the connection to ClickUp with a token belonging to a dedicated integration user, plus access to the target spreadsheet.
4. Describe the exceptions: a list missing a mapped field, a status not in your vocabulary, a task moved between lists.
5. Run it against two lists with different configurations and check the mapping before extending it.

You describe the outcome, and Cody builds, connects and deploys it. The Free plan costs $0, Pro costs $39 per month and Business costs $100 per month (CodeWords pricing page, 2026). Details are on the pricing page.

What belongs in the sheet?

The sheet holds the fixed column set plus a few fields that keep the data traceable and current.

• The fixed column set, in a fixed order, so formulas pointing at it do not break.
• The list and space of each task. This lets a combined sheet be split apart again.
• The task identifier as text, so rows can be matched against a later export.
• Derived values computed before export: days in current status, days until due, and whether the task is overdue. Spreadsheet formulas for these get broken.
• A visible run timestamp. A stale project sheet looks identical to a current one.

Leave out comments, descriptions and attachments. They make the sheet very large, and nobody reads them there.

How do you report time in status?

Report time in status by calculating how long each task has spent in its current status from the status change history. Almost no export includes this value, and it is a better health signal than the status itself.

• Report the distribution per status. It shows where work queues, not where anybody assumes.
• Watch the tail. Most tasks move through review quickly, and the few that sit for three weeks are the problem. An average hides them.
• Compare across lists. A status that takes twice as long on one team's list is a question worth asking.
• Do not make it a target. A team measured on time in status moves tasks sooner, which improves the number and not the work.
• Use it for a monthly conversation about where work waits.

How do you handle subtasks and double counting?

Handle subtasks by deciding whether to include them, stating the choice in the sheet and adding a column that marks subtask rows. Subtasks are separate tasks with their own statuses, assignees and sometimes custom fields.

• Including them double-counts anything summed, because the parent often carries the same estimate or value.
• Excluding them omits most of the work on lists that use subtasks heavily.
• The marker column lets the reader filter either way.
• Checklists are not subtasks and do not appear as tasks, which is a third behavior teams confuse with the other two.
• Multiple list membership adds to the problem: a task in two lists appears twice unless you deduplicate on identifier.

Which field types arrive awkwardly?

Dropdown, relationship, formula, date and user fields arrive as identifiers or raw values, so each needs a resolving step before the sheet is readable.

• Dropdown fields return option identifiers. Resolve the option list.
• Relationship fields return task identifiers. A second lookup renders a name.
• Formula fields are computed and may be absent or stale for tasks that have not been recalculated.
• Dates arrive as timestamps and take the spreadsheet's timezone, a workbook setting nobody has checked.
• Users are identifiers. Resolve the user list once and cache it for the run.
• Task identifiers are strings. Custom task identifiers are optional and vary by workspace, so decide which one you key on.

What reporting will people act on?

People act on a summary that leads with what is overdue and what has not moved, grouped by team or list. A project export exists because somebody wants a picture, and the picture is more useful than the table.

• Lead with overdue and stalled tasks. These are the two lists anybody acts on.
• Group by team or list, not by individual, so the conversation is about where work waits and not about who is slow.
• Show the change since the last run: what arrived, what completed, what slipped. A static snapshot looks the same every week.
• Count tasks with no assignee and no due date. This measures how much of the board is decorative.
• Put the summary on its own tab, above the data, so a person who wants a glance does not scroll through thousands of rows.
• Keep the raw rows underneath. A summary people cannot verify is a summary they will not trust.

How do you keep the export reliable?

Keep the export reliable by resolving each list's configuration at the start of every run and reporting problems instead of hiding them.

• Resolve list configuration at run time, not from stored identifiers.
• Deduplicate on task identifier across lists, or multiple list membership inflates every count.
• Replace a named range instead of appending, since tasks change and a sheet of current state should reflect that.
• Report unmapped lists and missing fields instead of producing empty columns.
• Report the outcome: tasks exported, lists skipped, fields not mapped and duplicates removed.

What are the limits?

Four limits apply to a workspace-wide export: rate limits, pagination, spreadsheet size and plan-dependent features.

• Rate limits apply per token and depend on plan, so a workspace-wide export needs pacing. Check ClickUp's API documentation for your plan.
• Pagination applies to task listings. A sheet built from the first page understates.
• Google Sheets caps the number of cells per spreadsheet, and a workspace-wide export with many custom field columns reaches that cap quickly.
• Some features depend on plan, including parts of custom fields and time tracking.
• Status change history varies. Confirm you can get the data a time-in-status report needs before you design around it.

What should you set up first?

Set up a fixed-column export across two or three lists first, with the mapping in its own sheet and a report of anything unmapped. Start with the lists somebody already reconciles by hand, because that reconciliation is the work you remove.

Two habits make the difference. Decide the columns before you look at the lists, since letting the export discover them produces the ragged sheet. And publish the unmapped report next to the data, because it turns "this sheet is full of holes" into a short list of configuration changes.

Frequently asked questions

Why is my export full of empty cells?

Custom fields are defined per list, so a column that exists for one team does not exist for another. Fix the column set, map each list onto it explicitly by field identifier, and report the lists that could not supply a column so their owners can add the field.

Why does grouping by priority give odd results?

Two lists' priority dropdowns may offer different options, so grouping mixes two scales. Normalize the values to a common vocabulary as part of the mapping, for example by mapping both "Urgent" and "P1" to one value, before you group or count anything.

Should subtasks be included?

Decide, state the choice in the sheet and add a column that marks subtask rows. Including subtasks double-counts anything summed. Excluding them omits most of the work on lists that use them heavily. Both choices are defensible, but leaving the choice unstated is not.

Why does a task appear twice?

The task belongs to more than one list, where multiple list membership is enabled. A cross-list export returns it once per list. Deduplicate on task identifier across lists, or every count in the export is inflated by the repeated rows.

What is the most useful column nobody exports?

Time in current status. It is a better health signal than the status itself, it shows where work queues, and it needs only the status change history. Most exports never use that history, so most teams never see where tasks wait.

Why do dropdown and assignee columns show identifiers?

Those fields return identifiers instead of labels. Resolve the option list and the user list once per run and cache them, so each cell does not need its own lookup. The sheet then shows readable names and the run stays fast.

Where should the mapping live?

Keep the mapping in a sheet of its own, so whoever owns the lists can see and maintain it. A mapping buried inside an automation is one nobody can check when a column looks wrong, and every change then needs somebody to edit the automation.

What should the summary show?

Show what is overdue, what has not moved and what changed since the last run, grouped by team instead of by person. Add the count of tasks with no assignee and no due date, which measures how much of the board is decorative.

Should the summary and the data share a sheet?

Use the same workbook with separate tabs, and put the summary first. Somebody who wants a glance should not scroll through thousands of rows, and somebody who needs to check a number can still find the raw rows on the data tab.

Related reading

• ClickUp and CodeWords
• Connecting ClickUp to Slack
• CodeWords integrations and templates