Duplicate & Delete a Report

Use the duplicateReport mutation to clone a report, and the deleteReport mutation to remove one. Duplicating copies the report’s title, description, config, and every data source — but not its shared collaborators; the duplicate starts private to you, and you become its creator. Deleting hard-deletes the report and cascade-deletes its data sources, and is restricted to the report’s creator.

A report aggregates records (Todo objects) across one or more workspaces (Project objects); see the Reports overview for the full model.

Request

Duplicate a report. The input argument is optional — omit it to accept the default title.

mutation DuplicateReport {
  duplicateReport(id: "report_123") {
    id
    title
    createdAt
  }
}

Pass a title to name the copy explicitly.

mutation DuplicateReportWithTitle {
  duplicateReport(id: "report_123", input: { title: "Q4 Pipeline (working copy)" }) {
    id
    title
  }
}

Delete a report. deleteReport returns Boolean!, so it takes no sub-selection.

mutation DeleteReport {
  deleteReport(id: "report_123")
}

Parameters

duplicateReport

DuplicateReportInput

deleteReport

Response

duplicateReport returns the newly created Report.

{
  "data": {
    "duplicateReport": {
      "id": "clm4n8qwx000008l0g4oxdqn7",
      "title": "Copy of Q4 Pipeline",
      "createdAt": "2026-05-29T14:03:11.000Z"
    }
  }
}

deleteReport returns true on success.

{
  "data": {
    "deleteReport": true
  }
}

Returns — duplicateReport

The mutation returns the new Report. The duplicate lives in the same organization as the original, and you are its creator.

For the full Report and ReportDataSource field reference (including the computed projectIds union and the todos / todoCount / aggregations query surface), see Query Reports and Report Data & Aggregations.

Returns — deleteReport

What gets copied

duplicateReport deep-copies the report into a new record in the same organization:

• The report — a new Report with a fresh id and uid. The title (defaulting to "Copy of <title>"), description, and config are copied verbatim.
• All data sources — every ReportDataSource is recreated with a fresh uid, preserving its name, sourceType, projectIds, filters, and order. A data source with projectIds: null (all workspaces the creator can access) stays null on the copy.
• Creator — the calling user becomes createdBy, regardless of who created the original.

It deliberately does not copy:

• Shared collaborators — reportUsers is not carried over. The duplicate starts private to you; re-share it with updateReport if needed.

Errors

{
  "errors": [
    {
      "message": "Report was not found.",
      "extensions": { "code": "REPORT_NOT_FOUND" }
    }
  ]
}

Omitting the required id is rejected by GraphQL as a non-null validation error before the resolver runs — it is not a Blue error code.

Permissions

The two mutations sit at opposite ends of the report permission model.

Anyone who can see a report can duplicate it (the duplicate is theirs, sharing nothing back to the original). Deleting is the most restricted report operation — even an EDITOR who can update the report cannot delete it. A caller who lacks the required access receives REPORT_NOT_FOUND rather than a distinct permission error.

The config field is a JSONObject — an opaque key/value blob whose internal shape is defined by the app, not the GraphQL schema. duplicateReport copies it as-is.

Related

• Reports overview — the report model, data sources, and how reports relate to records.
• Create a Report — build a report from scratch.
• Query Reports — fetch a report by id or list reports, with the full Report field reference.
• Manage Report Access — update a report and share it with EDITOR / VIEWER collaborators.
• Report Data & Aggregations — read the records, counts, and aggregations a report produces.