Last week's data overwritten
The export replaced history.
Greenhouse to Google Sheets automation for teams that report from a spreadsheet
Greenhouse to Google Sheets automation that keeps applications, stage history and offers current, merged on application ID and paced inside Google's quotas
Google Sheets allows 300 reads and 300 writes a minute per project and 60 of each per user per project, and returns a 429 when they are exceeded. BoldBellows records the application ID, the stage and the time Greenhouse reported before a cell is written, writes in batches and backs off exponentially after a rate-limit response, then upserts each updated application into an Applications tab on its ID, appends each stage change to a History tab with its time, records offers on an Offers tab with their status, counts applications and hires by job on a Summary tab, and leaves compensation and demographic columns out. A rerun updates rows in place and adds nothing twice.
View Pricing
From $415, paid once. Sync Greenhouse to Google Sheets.
The guarantees built into the Google Sheets route
- A row per application keyed on ID
- History kept every stage move
- Quota-safe batched writes
- Sensitive columns off never written
- Transferable build Everything is documented so your team can run it without us
- A price you can plan around from $415 in a single payment, no seats and no usage fees
01 · the paste-over problem
Each Monday's export overwrites last Monday's truth
A weekly export shows the pipeline on the day it was made and erases how it looked before. Time-in-stage can't be calculated, a candidate who moved twice looks like they moved once, and a pivot table built on the old layout breaks when a column shifts. Writing row by row from a script hits Google's per-minute quotas and fails halfway, and a column of offer amounts ends up in a sheet that dozens of people can open.
No time in stage
Moves were not logged.
A script that failed halfway
Quotas were exceeded.
- Each event is treated as brand new
- A weekly export replaces the last one
- Row-by-row writes hit the quota
- The application ID, plus the stage and time for history rows is stored before anything is written
- Applications are keyed rows with a stage history
- Writes are batched and paced inside the quota
02 · how it works
How Greenhouse applications become keyed rows and history in Google Sheets
Each event passes the same gates: rule, key, lookup, write, proof.
- 01
Catch the event
The Greenhouse notification is received, confirmed as genuine and matched against the list of changes that should act.
- 02
List, merge, append
Updated applications are listed, merged on their ID, and stage changes are appended to a history tab.
- 03
Batch, back off, protect
Writes are batched, a 429 triggers exponential backoff, and sensitive columns are never written.
Source and destination facts
Sixty a minute per person
Google Sheets allows 300 reads and 300 writes a minute per project and 60 of each per user per project, so the route writes in batches and backs off exponentially after a 429.
A minute to recover
When a minute's quota is spent, Google asks for exponential backoff and requests succeed again after a minute, so a large sync is cut into batches that each fit inside one minute.
When a write is doubtful
The route finds the record in Google Sheets by the application ID, plus the stage and time for history rows, compares it with the intention and only then decides.
03 · what ships in the build
What you are buying: the Greenhouse to Google Sheets route in parts
Connect covers admission and the key, Resolve covers construction and matching, and Safeguard covers comparison and ownership.
This build speaks to sync greenhouse candidates to Google Sheets, greenhouse offers Google Sheets and greenhouse to Google Sheets consultant. Related searches include greenhouse applications data Google Sheets, greenhouse Google Sheets Zapier, greenhouse referrals data sheets, greenhouse to Google Sheets duplicate prevention, greenhouse scorecards Google Sheets, greenhouse Google Sheets integration, greenhouse to Google Sheets historical migration, greenhouse to Google Sheets service, greenhouse Google Sheets automation, greenhouse to Google Sheets, greenhouse to Google Sheets error handling, greenhouse to Google Sheets implementation, greenhouse offers Google Sheets sync, greenhouse to Google Sheets Zapier, export greenhouse interviews to spreadsheet, connect greenhouse to Google Sheets and greenhouse applications Google Sheets.
Change classifier
Sorts each Greenhouse event into act, ignore or review, with the reason saved.
ConnectStable identity ledger
Records the source key, the time of change and the Google Sheets identifier for each sync, in the Greenhouse to Google Sheets route.
ConnectTyped field translator
Converts Greenhouse values into the exact types Google Sheets expects, so nothing arrives as the wrong kind of data.
ConnectKeyed row writer
Merges the application and appends history.
ResolveApplication-and-stage matcher
Looks up the application ID, plus the stage and time for history rows first, then chooses the one safe action for the event.
ResolveTab and column matrix
Decides which tab, columns and exclusions each Google Sheets field uses.
ResolveSheet register
Checks Google Sheets against Greenhouse at intervals and raises anything that diverges.
SafeguardHeader drift monitor
Spots a renamed or moved header before writes land in the wrong column, on the Greenhouse to Google Sheets route.
SafeguardException ageing
Tracks how long each unresolved case has been open and raises the oldest first.
Safeguard04 · who it's for
Suited to busy staffing and recruiting agencies, and to those who keep a Google Sheet of applications, stage history and offers, keyed on application ID and updated from Greenhouse changes
Greenhouse holds the record. Google Sheets is where it is shared, charted and discussed.
Recruiter
"Is the sheet current?"
Applications refresh on a schedule.
Head of talent
"Which stage is slow?"
Dated rows show the delay.
Analyst
"Do not break my pivots."
The layout is fixed and keyed.
Hiring manager
"Show me my jobs."
A Summary tab counts by job.
Data protection officer
"Keep offer amounts out."
Sensitive columns are never filled.
Founder
"No more Monday exports."
The sheet updates itself.
Pricing depends on applications, stages and offers
Your Greenhouse to Google Sheets price, as you choose it
From $415, with no monthly fee.
View Pricing
- One setup fee
- Range shown first
- PDF handover included
05 · compare your options
Not a weekly export pasted over last week's, not a basic zap, but a keyed sheet sync
Each can fill a sheet. Only one merges applications, keeps history and stays inside Google's quotas.
| Where the work starts | a weekly export pasted over last week's | A one-step Greenhouse to Google Sheets zap | Built as a keyed sheet sync |
|---|---|---|---|
| What starts the work | Someone remembers | All events of the chosen type | The Greenhouse event you defined, nothing else |
| How identity is decided | Looked up in a spreadsheet | A convenient field, unchecked | Application ID, with stage and time for history |
| What reaches Google Sheets | Only what was noticed | Plain values with no types | One row per application and one history row per stage move |
| After an uncertain result | Check each tool in turn | Halts and waits | Verifies the result, then fixes or escalates |
A stale event shows up last
Time is checked before anything is written: the stale event is logged with its reason and the current row stays as it is, in the Greenhouse to Google Sheets route.
Forty applications change stage in the same minute
They are merged in one batched write, history rows are appended in order, the quota is not exceeded, and a rerun changes nothing. Matching on the application ID, plus the stage and time for history rows, the route sorts the situation into absent, present and correct, present but different, or ambiguous. If the Google Sheets row exists and matches, nothing more is written.
The application ID, plus the stage and time for history rows is the one thing that cannot change after launch, so it is settled on day one.
Pricing
Build your Greenhouse to Google Sheets price
Pick a package, answer three short questions about how Greenhouse data should reach Google Sheets, and your price and turnaround move as you choose.
06 · process & getting started
Six steps from weekly paste to a sheet that stays current
Brief, access, design, test, launch and review: six steps, each with a deliverable.
- Step 01
Design the tabs
We map applications, history, offers and summary to tabs, columns and keys.
- Step 02
Approve access
Access is granted, tested and documented on both the Greenhouse and Google Sheets sides.
- Step 03
Fix the tabs and exclusions
Tab layout and which columns stay blank are drafted and agreed first, along with how rows are matched.
- Step 04
Run the hard cases first
Repeats, stale events and permission changes are tested before the easy cases, in a copy of Google Sheets, in the Greenhouse to Google Sheets route.
- Step 05
Launch with notes
Production begins at a boundary you have agreed, with a PDF covering the rules, owners and repair steps.
- Step 06
Check the live results
The first runs are compared record by record with the source so you can see the route doing its job.
07 · turnaround
Delivery windows by package
With Greenhouse to Google Sheets in place, the schedule runs from the day access is granted.
Connect
4 to 7 business days
Resolve
7 to 11 business days
Safeguard
11 to 17 business days
08 · before we start
What to gather before day one
A named Greenhouse administrator who can approve the connection
Harvest v3 read access and a Google Sheet you can edit
A Greenhouse user or token limited to the objects in scope
Two real cases: one Greenhouse event that should act and one that should not
Your preferred naming for statuses, tags or labels in Google Sheets
Contact details for whoever manages Google Sheets access
09 · security and ownership
The Greenhouse row gets only what it needs, and nothing inside Google Sheets is altered
Neither Greenhouse nor Google Sheets is modified.
Supported connections, nothing more
Access runs through the approved connection points on both sides, so an update to Greenhouse or Google Sheets does not undo the build.
Scoped, revocable access
Credentials are limited to the agreed scope, and withdrawing them stops the route at once.
Private details stay private
Internal notes, payment information and anything outside the map remain in Greenhouse and never appear in Google Sheets.
Doubt goes to a lookup
When a write might have landed, the answer comes from Google Sheets, matched on the application ID, plus the stage and time for history rows, not from a second attempt.
Minimal logging
Operational history is limited to IDs, timestamps and outcomes.
Full handover
You leave with the mapping, the settings and a plain-language guide.
10 · verified reviews
What BoldBellows clients say
Verified reviews from business owners who use BoldBellows automations every day, from marketing and sales to support and operations.
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 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 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 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 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.
11 · questions
Greenhouse in Google Sheets: what recruiting teams ask
These are the queries we hear most, with straight replies.
When is a Greenhouse to Google Sheets Zapier automation not enough?
A hiring sheet that is current without exports is well within a zap's reach. It does not merge each application into one row, keep stage history or stay inside Google's quotas. The build is the part that handles what a simple zap cannot.
Why not paste a weekly export?
It overwrites history. The route merges rows and appends every stage move.
What are Google's limits?
300 reads and 300 writes a minute per project and 60 of each per user per project, which the route stays inside.
Are offer amounts copied?
By default, sensitive columns are excluded.
Will a rerun duplicate rows?
No. Application ID and stage time are the keys.
Can it count hires by job?
Yes, on a Summary tab.
Does the sheet change Greenhouse?
No. It only receives.
What if my fields change after mapping on the Greenhouse to Google Sheets route?
Mapping is a standard step. Our Greenhouse Google Sheets field mapping service ends with a table you approve and a test that proves it.
Does it support our own routing rules in the Greenhouse to Google Sheets route?
Yes. We convert your conditions to a custom Greenhouse workflow for Google Sheets and explain each choice like a Greenhouse Google Sheets integration consultant would. From $415.
How do you handle breaking changes?
Upstream changes are caught at the point of use: the step pauses, the reason is recorded, and your owner is notified. Repair work is quoted outside the review window.
Report from a sheet that stays current
Give your team a hiring sheet with history behind it
Bring one trigger, one destination and one person who owns exceptions, and we will build a route to automate Greenhouse data to Google Sheets around them. Connect starts at $415.
Those are scoped and quoted separately.