An average nobody could check
The dates behind it were not stored.
BoldBellowsLinear to Google Sheets automation for delivery metrics
Linear to Google Sheets automation that keeps every state change with the state it left and one current row per issue, so lead time and cycle time are a pivot and not an estimate
Linear to Google Sheets automation gives a lead the dates behind the averages. Linear sends updatedFrom with the previous values on every update, so a state change arrives with the state it left. It also meters API reads by the hour, so rebuilding a history by polling is expensive. BoldBellows stamps each webhook with its delivery UUID, its type and its issue, gives a late delivery time to land and checks the order before it writes, then appends each state change to a ledger, keeps one current row per issue, protects the key column, and reads the workspace on a schedule inside the hourly limits to fill any gap.
View Pricing
One-off setup from $415
No monthly subscription
- Log Linear state changes to Google Sheets
- From-state and to-state in a ledger
- Lead time and cycle time as pivots
- From and to each ledger row keeps both states
- One current row the issues tab always shows the latest state
- Protected key the issue UUID column cannot be overtyped
- Limit-aware backfills stay inside Linear's hourly budget
- Evidence kept Each decision stores the identifiers and timestamps behind it
- Simple commercial terms $415 up front for the entry package, with no renewal to remember
Chapter 01 the average-without-dates problem
An average cycle time with no dates behind it cannot be argued with or checked
A dashboard says the average cycle time is four days. Nobody knows which issues made it or whether last month was different. A sheet that only appends grows into a pile where one issue has twenty rows; a sheet that only overwrites keeps the final state and loses the dates. Rebuilding the history by polling Linear spends the hourly request and complexity budgets.
The sheet only knew when an issue was closed, so every average was wrong.
Twenty rows for one issue
Each event, and each retry, appended another.
History overwritten
A new state replaced the old one with no trace.
Before
After
Before
- A retried delivery adds another row
- Averages come from a dashboard
- History is rebuilt by polling
After
- A current-state row keyed by Linear issue UUID, with a state-change ledger keyed by delivery UUID links every row to its source
- Every state change is logged with from and to
- A scheduled read fills gaps inside the hourly limits
Chapter 02 How it works
How a Linear update becomes a ledger row and an updated issue row
Three moves: decide whether it counts, locate the Google Sheets row, then write and prove it.
Interpret the source state
The route reads the Linear record behind the event and confirms the issue event meets the documented rule.
Check, unpack, append
The signature is checked, updatedFrom is read, and the delivery UUID is searched in the ledger before a row is appended.
Update, throttle, reconcile
The issue row is updated only if the delivery is newer, reads are paced under the complexity budget, and a scheduled read compares the workspace with the sheet.
What we know about Linear and Google Sheets
- Sixty seconds of tolerance: Linear asks receivers to reject a delivery whose timestamp is more than 60 seconds from the current time, which is how a replay of an old request is refused.
- Appends find the table: The Sheets API append method writes below the last row of the logical table in the range it is given, which is why the ledger holds only state changes.
- Uncertain results: A missing confirmation starts a lookup in Google Sheets by a current-state row keyed by Linear issue UUID, with a state-change ledger keyed by delivery UUID; a new write is never the first response.
Chapter 03 What ships in the build
The parts of a Linear to Google Sheets build, and what each does
Start with Core, which admits events and claims identity; Scale then shapes the Linear row; Stewardship checks Google Sheets long after go-live.
Trigger gatekeeper
Lets only the agreed issue events through and keeps a reason for every one it stops.
Stable identity ledger
Turns a Linear record into a traceable Google Sheets entry by storing both identities together.
Payload trimmer
Cuts each Linear payload down to the fields Google Sheets needs before the row is prepared.
Ledger appender
Writes each state change as a new row with the issue, team, from-state, to-state and time.
Issue-row updater
Finds the issue's row and rewrites it only when the delivery is newer than what is stored.
Tab layout matrix
Defines which columns live on the ledger and which on the issues tab, with state types kept beside names.
Sheet register
Finds records where Google Sheets has drifted from Linear and shows how long they have been wrong.
Budget watch
Tracks the remaining request and complexity budget before a scheduled read begins.
Case register
Keeps evidence, status and next step for every Linear row that could not be confirmed.
Linear to Google Sheets without Zapier or track linear cycle time in Google Sheets, plus linear to Google Sheets consultant: it is all in scope. Related searches include linear lead time report sheet, linear to Google Sheets duplicate prevention, linear labels Google Sheets sync, linear roadmaps Google Sheets, linear projects data Google Sheets, linear comments data sheets, linear state changes spreadsheet, linear webhook Google Sheets, linear to Google Sheets service, sync linear issues to Google Sheets, linear to Google Sheets, linear Google Sheets integration, connect linear to Google Sheets, export linear cycles to spreadsheet, linear to Google Sheets implementation, linear to Google Sheets error handling, linear Google Sheets automation, linear to Google Sheets Zapier and linear to Google Sheets historical migration.
Chapter 04 Who this fits
If you are among the platform teams tracking reliability work in Linear, you may also need to calculate lead time and cycle time from Linear without exports
Let Linear run the work and a sheet keep the dates, so every average can be traced.
Engineering manager
"What's our real cycle time?"
The ledger answers with start and finish dates for every issue.
Delivery lead
"Which states slow us down?"
Filter the ledger by state to see where work waits.
Sheet owner
"Don't let anyone break the match."
The issue UUID column is protected and formulas stay clear of it.
Chief of staff
"Give me numbers I can defend."
Every average traces to dated rows.
Agency owner
"One report per client."
Each client's teams write to their own sheet.
Founder
"Delivery speed at a glance."
In the Linear to Google Sheets route, one clean tab stays readable on a phone.
Chapter 05 The options
A manual export, a zap or a state-ledger workbook: choosing how Linear reaches Google Sheets
Each can add a row. Only one keeps the from-state and the present apart.
| Question | a manual export | A no-code Linear to Google Sheets recipe | Our state-ledger workbook |
|---|---|---|---|
| What starts the work | Whoever is watching Linear | Whatever the trigger allows | An approved issue event, judged before any write |
| How identity is decided | Matched by eye | The title or a label | Rows appended on every event |
| What reaches Google Sheets | A pasted summary | A raw payload | A state-change ledger plus one current row per issue |
| After an uncertain result | Staff search Google Sheets manually | A blind retry | Finds the row first, then decides |
Events arrive out of order
Delivery order is not trusted. Each Linear event is ranked by its own time against the state already held in Google Sheets.
An issue is deleted in Linear after its changes were already logged
The removal is added to the ledger, the current row is marked as removed, and the earlier history is kept. A search on a current-state row keyed by Linear issue UUID, with a state-change ledger keyed by delivery UUID finds what exists; a comparison says whether it matches; the outcome is written down. Creation is allowed in one case alone: the Linear row is confirmed missing.
Everything in this route hangs from a current-state row keyed by Linear issue UUID, with a state-change ledger keyed by delivery UUID, so it is agreed before any mapping begins.
Interlude The price follows ledger and issues tabs
Build your Linear to Google Sheets quote, one choice at a time
Price the Linear to Google Sheets route in your own time. The configurator handles the sums and starts at $415.
View Pricing
One setup fee · Range shown first
Pricing
Build your Linear to Google Sheets price
Pick a package, answer three short questions about how Linear data should reach Google Sheets, and your price and turnaround move as you choose.
Chapter 06 The process
The six steps that end in a sheet with dates behind it
Every step ends with something you can inspect: a map, a key, a test result or a signed note.
-
About 30 minutes
Choose the events
We pick which Linear events earn a ledger row, which update an issue row and which are left out.
-
Access review
Approve access
We connect to the Linear data in scope and to Google Sheets, and agree the identifiers the route will store.
-
Most of the project
Agree tabs and columns
Tab layout, column types, the protected key and the sharing rules are written down and signed off, on the Linear to Google Sheets route.
-
Before you review
Rehearse the failures
Duplicates, out-of-order events, blank values and timeouts are staged in a test area so the repairs are proven.
-
Handover day
Launch with notes
Handover closes the project: a live route, a checkpoint to prove it, and documentation to run it.
-
About 30 minutes
Settle in
We watch the live route through its first cycle, compare both sides and tune thresholds where the data says to.
Chapter 07 Turnaround
Days to delivery, package by package
With Linear to Google Sheets in place, the schedule assumes credentials arrive in the first day or two.
Core
4 to 7 business days
Scale
7 to 11 business days
Stewardship
11 to 17 business days
Chapter 08 Getting started
Items to hand over at kickoff
Consent from your Linear owner to read the agreed records
Edit access to the Google Sheet and a Linear admin able to add the webhook
Read access to the Linear objects this route depends on
A plain-language list of the issue events to include and exclude
The people who should be told when something fails
A time window in which testing can happen safely
Chapter 09 Trust
Scoped access, small payloads, and no changes to either tool
For Linear to Google Sheets, no product code is patched and no bulk export is made.
Published interfaces only
Every request goes through the public interfaces of Linear and Google Sheets. No core file, theme or application code is touched.
Scoped, revocable access
Connections are restricted to the objects on the approved list.
Data kept to the job
The row carries the values the business needs and no more; the rest of the Linear record is never copied across.
Retries that cannot duplicate
Every repair starts from a current-state row keyed by Linear issue UUID, with a state-change ledger keyed by delivery UUID and a read of Google Sheets, so trying again is safe by construction.
Minimal logging
Only technical identifiers reach the run history.
Full handover
The finished route and its explanation are delivered together.
"Cycle time is a subtraction, so the build keeps the date an issue started and the date it finished side by side."
Steven GrratFounder, BoldBellows
Chapter 10 In their words
What BoldBellows clients say
Verified reviews from business owners who use BoldBellows automations every day, from marketing and data to support and operations.
AI Workflow Automation for Agencies
Running a digital agency with many clients was overwhelming. BoldBellows built one automation dashboard that tracks tasks, sends updates and creates client reports automatically.
Clients love the transparency and we love the time we get back. Productivity is up, and project delays have dropped to almost zero.
AI Data Entry & Reporting Automation
We used to spend hours collecting data and building weekly reports by hand. BoldBellows automated all of it.
The reports are clean, visual and easy to read, and our managers rely on them for quick decisions. Human error is gone and our numbers are more accurate across the board.
AI Video & Voice Automation
We publish product videos every week, and BoldBellows introduced us to AI video automation. The system writes the script, voices it and produces the finished video in minutes.
The quality is remarkable: professional voiceovers, clean visuals and smooth editing. Production time went from three days to under 30 minutes, and we scaled our video marketing without adding cost.
AI Email & Smart Inbox Management
Our inbox used to be chaos. BoldBellows built an AI email system that sorts messages, drafts replies and flags anything urgent.
It learns how we write and gets better every week. We reply faster and no longer miss important messages. It feels like having a personal assistant working around the clock.
AI Booking & Scheduling Automation
Our coaching business needed a better way to schedule. BoldBellows automated all of it: bookings, reminders, cancellations and follow-ups.
No-shows fell by 60% and clients enjoy how smooth it is. It feels personal, not robotic. One of the best upgrades we’ve made.
AI Translation & Localisation
When we expanded abroad we needed fast, accurate translations. BoldBellows built an AI translation system that turns our content into several languages instantly.
The translations read naturally and suit each culture. We now serve customers in five new countries without hiring translators. BoldBellows helped us go global.
AI HR & Recruitment Automation
Our HR team was drowning in applications. BoldBellows automated screening, skills-based filtering and interview scheduling.
It saves us hours every week and means we only interview qualified people. Hiring is now faster, better organized and more professional.
AI Accounting & Invoice Automation
BoldBellows automated our whole invoicing process: creating invoices, sending reminders and tracking payments.
Late payments dropped sharply, and our accounting team finally has time for strategy instead of repetitive admin. Worth every penny.
AI E-commerce Listings Automation
BoldBellows automated our product listings. The AI writes descriptions, organizes photos and publishes listings across several marketplaces.
It even answers customer questions instantly. Our store looks more professional and sales have noticeably increased.
AI Chatbot & Customer Support
BoldBellows built an AI support chatbot for our online boutique, and it has changed how we run the business. We used to have two full-time staff answering the same questions all day. Now the AI handles order tracking, product recommendations and even refund requests on its own.
What surprised me most is how natural it sounds. Customers compliment the ‘agent’ without realizing it’s AI. Our support workload dropped by 75% and customer satisfaction went up dramatically.
AI Content & Social Media Automation
Our marketing agency couldn’t keep up with content. BoldBellows set up an AI content engine that writes blog posts and captions and even designs our social media creatives.
It spots trends and suggests topics for us, so we stay ahead of competitors. We now produce three times the content with the same team, and engagement has soared. They didn’t just automate our workflow, they lifted our whole brand.
AI Lead Qualification & Sales Automation
Our sales team wasted hours chasing cold leads. BoldBellows built an AI lead-scoring system that reads behavior, email engagement and buying signals.
It filters out weak leads and sends personalized follow-ups automatically, so our team only talks to people who are ready to buy. Conversions rose 40% in the first month. It paid for itself straight away.
AI Customer Journey Automation
We wanted a smoother path from first contact to purchase. BoldBellows built an AI system that guides each customer there automatically.
It sends personalized messages, recommends products and follows up at just the right moment. Customer retention has improved dramatically.
AI Document & Contract Automation
Onboarding was slow because we wrote every contract by hand. BoldBellows automated the lot: contracts, welcome emails and client setup.
What took 48 hours now takes under 10 minutes, and clients regularly tell us how professional it feels.
AI Social Comment & DM Automation
We get thousands of comments and messages every week. BoldBellows built an AI system that replies instantly, filters spam and surfaces the important ones.
Engagement is up and our page looks active around the clock. It’s like having a full social media team that never stops.
AI CRM Automation
Our CRM was barely used because updating it by hand was tedious. BoldBellows automated data entry, tagging, segmentation and follow-ups.
Now the CRM is always up to date and our campaigns are far more accurate. It improved our whole sales pipeline.
AI Voice Assistant
BoldBellows built a custom AI voice assistant for our customer hotline. It answers questions, books appointments and handles simple requests.
Customers love how fast it is, and our call-centre workload dropped dramatically. One of the smartest upgrades we’ve made.
AI Automation Partner
BoldBellows is hands-down the best AI automation partner we’ve worked with. Their systems are fast, reliable and built around how our business actually works.
Every automation they’ve delivered, from customer service to content, runs flawlessly. We’ve saved time, cut costs and grown faster than we expected.
Chapter 11 Questions
Linear and Google Sheets: questions from engineering leads
The essentials in question-and-answer form, with room for your own in the quote request.
Should we just use a Linear to Google Sheets Zapier recipe?
For a row appended on every event alone, a basic zap is enough. What it will not do is keep every state change with the state it left, one current row per issue, and stay inside Linear's hourly limits. This build covers exactly what a basic connector leaves open.
How do I calculate cycle time from Linear in Google Sheets?
Each state change is logged with the state it left and the time, so lead time and cycle time are pivots over the ledger.
Why keep a ledger and an issues tab?
The ledger holds the history and the issues tab holds the present, so you get both without one overwriting the other.
Does a repeated delivery add a Linear row?
No. The delivery UUID is searched in the ledger first, so a repeat is recognised and nothing is added.
What about Linear's API limits?
An API key gets 2,500 requests and 3,000,000 complexity points an hour. Scheduled reads are paced inside that budget.
Can I load history from before the sheet?
Yes. Existing issues are read in checkpointed pages that respect the hourly budget and written with the same key as live events.
Can sheet edits change Linear?
No. The route only receives from Linear, so a stray edit cannot change an issue.
What does the mapping document contain?
A signed-off Linear Google Sheets field mapping service output is required before we write to Google Sheets.
Can the route branch on region, value or stage on the Linear to Google Sheets route?
Yes. Your rules decide what moves, so the route becomes a custom Linear workflow for Google Sheets. A Linear Google Sheets integration consultant's advice comes with it, from $415.
Will I be told if something stops working in the Linear to Google Sheets route?
Dependencies are listed at handover. A breaking change pauses just the part it touches and alerts your owner, and post-review fixes are quoted separately.
Give your team a sheet that matches Linear
Tell us how Google Sheets should look when things work, and we will automate Linear data to Google Sheets to produce exactly that. From $415.
- From $415, paid once
- From and to
- Budget-aware
- No monthly fee from us