Weekly

Back up all your Linear issues weekly

Every week you get a CSV of all your issues as a backup.

Runs: Weekly
Apps: Linear
AI: Not needed
Access: read

Send this to your assistant

Create a ClickRuntime automation: every Sunday at 8pm, export all my Linear issues with title, status, assignee, priority and dates to a CSV and email it to me.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Add to ChatGPT Add to Claude

First time? Adding ClickRuntime to your assistant takes about two minutes.

Why use it

Why teams use this automation

Linear holds a company's engineering history: every bug, every decision made in comments, every estimate. Yet it is hosted by someone else, and teams rarely think about what happens if an account is deleted by mistake, a workspace is restructured or an integration wipes a field. Auditors and customers in regulated industries also ask for records that sit outside the tool itself.

Every week, ClickRuntime pages through all the issues in your Linear workspace, builds a CSV with the key fields and emails it to you, either as an attachment or as text, depending on size. You end up with a dated file for each week that you can store in your own archive or drive.

It is a low-effort safety net for managers and operations leads who want one.

What you get out of it

A copy exists outside Linear
If a mistake or a bulk edit damages data, you have last week's file to compare with. That is peace of mind that costs nothing but a weekly email. That kind of peace of mind is cheap for what it protects.
Audits and customer requests are easier
Some customers and auditors want evidence of how issues were handled. A dated export lets you produce it without a rushed manual extraction. It saves a stressful scramble the day the request arrives.
Bulk analysis happens in a spreadsheet
Teams that want to count issues by label or compute average age can open the CSV in a spreadsheet. That is simpler than building a report for every question. That makes ad hoc questions easy to answer.
Data changes can be traced
With weekly snapshots, you can see how an issue's status or estimate changed between files. It helps when people disagree about what was said or decided. That evidence settles most arguments about history.
Migrations are easier
If you ever move to a different tracker, a recent export of all issues is the starting point. You are not scrambling to extract data from a tool you are about to leave.

How it works

What happens, step by step

Once a week, ClickRuntime pages through every issue in your Linear workspace.
It builds a spreadsheet-style list with each issue's ID, title, status, assignee, priority, and created and completed dates.
You get the export by email, giving you a regular backup you can open in Excel or Google Sheets.

Before it runs live

Connect Linear

What you get

RunsWeekly

Back up all your Linear issues weeklytoday, 9:00Succeeded

Email · Linear exportLinear export: 842 issues id,title,status,assignee,priority,created,completed

Build your own

Need it to work differently?

This template is a starting point. Copy the prompt and change it, or describe a different automation from scratch, with your own conditions, more apps or an AI step. Your assistant writes it, tests it and runs it on ClickRuntime.

Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

Changes you can ask for

Run it at a different time, more or less often, or only on weekdays
Add an AI step, for example to summarize, sort or draft a reply
Add another app, for example also send it to Slack
Combine it with other Linear steps into one automation

Under the hood

The code that runs this automation

This is the Python script that runs each time the automation starts. Your AI assistant writes it for you when you send the prompt, and you allow each step in your assistant. To change how the automation works, describe the change to your assistant and it updates the script for you. For every function it can use, see the script reference.

weekly_export_of_all_issues.pyexample

import csv, io
from clickruntime import on_trigger, http, credentials, notify

def linear(query, variables=None):
    r = http.post(
        "https://api.linear.app/graphql",
        headers={"Authorization": credentials.secret("LINEAR_API_KEY")},
        json={"query": query, "variables": variables or {}},
    )
    r.raise_for_status()
    return r.json()["data"]

@on_trigger
def run(event):
    rows, cursor = [], None
    while True:
        page = linear("""query($after: String) { issues(first: 250, after: $after) {
          nodes { identifier title state { name } assignee { name } priorityLabel createdAt completedAt }
          pageInfo { hasNextPage endCursor } } }""", {"after": cursor})["issues"]
        rows += page["nodes"]
        if not page["pageInfo"]["hasNextPage"]:
            break
        cursor = page["pageInfo"]["endCursor"]
    out = io.StringIO()
    w = csv.writer(out)
    w.writerow(["id", "title", "status", "assignee", "priority", "created", "completed"])
    for i in rows:
        w.writerow([i["identifier"], i["title"], i["state"]["name"], (i["assignee"] or {}).get("name", ""),
                    i["priorityLabel"], i["createdAt"], i["completedAt"] or ""])
    notify.email_me(f"Linear export: {len(rows)} issues", out.getvalue())
    return {"issues": len(rows)}

FAQ

Common questions

Which fields are in the CSV?

The default columns are the issue ID, title, status, priority, assignee, team, labels, created date and updated date. If your workflow depends on other fields, such as estimates or cycle, name them and they are added to the export. The file name includes the date, which makes weekly backups easy to tell apart.

What if my workspace has thousands of issues?

The automation pages through Linear's results until it has everything, which works for large workspaces but takes longer. If the file becomes too big to attach, the email can contain a link to the file in your storage instead, which is a common change.

Does the export include comments and attachments?

The default export covers issue fields, not comment threads or uploaded files. If you need comments for compliance, they can be added as a second column or a separate file, though that makes the file considerably larger.

What permissions does it need?

read. Nothing else in your accounts is used.

Does it need AI?

No. It runs without AI, so it doesn't use your plan's AI allowance.

How many runs does it use?

One run each time it runs (weekly). Checks that find nothing to do and stop right away aren't counted.

Can I change how it works?

Yes. Describe the change to your AI assistant, for example a different schedule, channel or filter. It updates the automation, tests it and tells you what changed.

On a schedule