View all app connections
View all AI automations
View all chatbots
View all lead automations
View all booking automations
View all payment automations
View all workflows
View all Shopify
View all WooCommerce
View all HubSpot
View all Salesforce
View all Stripe
View all Google Sheets
View all Slack
View all dental practice
View all law firm
View all medical practice
View all real estate
View all restaurant and food
View all home services
View all construction
See all: get more leads
See all: get paid faster
See all: save admin time
See all: support customers
See all: book more appointments
See all: sell more online
See all: hire and onboard
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations
View all AI automations

Lever to Google Sheets automation for teams that report from a spreadsheet

Lever to Google Sheets automation that keeps opportunities, stage history and archive reasons current, merged on opportunity ID and paced inside Google's quotas

Google asks for truncated exponential backoff with a typical ceiling of 32 to 64 seconds after a 429 and allows 300 reads and 300 writes a minute per project. BoldBellows records the opportunity ID, the stage and the time Lever reported before a cell is written, writes in batches and backs off politely after a rate-limit response, then upserts each updated opportunity into an Opportunities tab on its ID, appends each stage change to a History tab with its time, records archive reasons with their hired or non-hired type on a Reasons tab, counts opportunities and hires by posting on a Summary tab, and leaves out pay, confidential opportunities and sensitive columns. A rerun updates in place and adds nothing twice.

View Pricing

From $415, paid once. Sync Lever to Google Sheets.

  • Sync Lever to Google Sheets
  • Opportunities, history and reasons
  • Inside Google's quotas
Lever opportunities stage history and archive reasons written to Google Sheets merged on opportunity ID refreshed from updates and paced inside Google quotas, built by BoldBellows

The guarantees built into the Google Sheets route

  • A row per opportunitykeyed on ID
  • History keptevery stage move
  • Quota-safebatched writes
  • Sensitive columns offnever written
  • Scoped accessCredentials are limited to the objects in scope and can be revoked
  • A price you can plan aroundfrom $415 in a single payment, no seats and no usage fees

B2Before and after

Each export replaces the story with the latest page of it

A weekly export keeps the present and erases the past. The sheet cannot tell how long people sit in a stage, an opportunity moved twice looks moved once, and a pivot built on yesterday's layout breaks when a column shifts. Scripts that write cell by cell run into Google's per-minute quotas and stop halfway, and a column of pay figures ends up in a sheet dozens of people can open.

Sound familiar?

Last week's data overwritten

The export replaced history.

No time in stage

Moves were not logged.

A script that stopped halfway

Quotas were exceeded.

Pay in a shared sheet

Sensitive columns were copied.

A pivot that broke

A column moved.

A candidate listed twice

No merge key.

The same reports, with the history behind every number

Before

Before Lever to Google Sheets automation: manual candidates exports, duplicates and broken formulasThe old way: a broken VLOOKUP formula with #N/A, #VALUE! and #REF! errors that take three hours to fix.Lever_candidates_MASTER.xlsxfx=VLOOKUP(A2,Candidates!A:F,6,FALSE)ABC#1048Maya Chen9#1049Omar Hale#N/A#1050#N/A#REF!Sam Ortiz#VALUE!!!!!3 hours to fix
  • Every hook delivery becomes a write
  • A weekly export replaces the last one with Lever to Google Sheets
  • Cell-by-cell writes hit the quota

After

After Lever to Google Sheets automation: one clean sheet that matches LeverThe new way: six live tiles for candidates, net hires, stage changes, average candidate, pipeline and match rate.SYNC · TODAYLIVECandidates1,204Hires hires4.82kStage changes12Avg candidate4PipelineIn syncMatch100%
  • Identity is fixed by the opportunity ID, plus the stage and time for history rows and never re-guessed
  • Opportunities are keyed rows with a history
  • Writes are batched inside the quota

D4How it works

How Lever opportunities become keyed rows and history in Google Sheets

Every step has a check before it, so a fault stops the run instead of spreading.

How Lever to Google Sheets automation works: candidates in, one clean row each, on a scheduleYour account feeds one Google Sheet, which fans out into Candidates, Pipeline, Stage changes and Reports tabs.Your Lever accountread-onlyYour Google SheetCandidateHiresStage changeStatus#10489–Hired#104914–Hired#10505-1Part#105121–New#10527Live rows land hereCandidates1,204 rowsPipeline318 candidatesStage changes12 fixedReports46 hiredRead-onlyHow Lever to Google Sheets automation works: candidates in, one clean row each, on a schedule, stacked: your account feeds one Google Sheet with four tabs: Candidates, Pipeline, Stage changes and Reports.Your accountread-onlyRead-onlyYour Google SheetCandidateHiresStage changeStatus#10489–Hired#104914–Hired#10505-1Part#105121Candidates1,204 rowsPipeline318 candidatesStage changes12 fixedReports46 hired

1. Check it is real and in scope

The Lever notice is validated, the underlying record is read, and only a qualifying Lever event moves on.

2. List, match, append

The latest changes are fetched, matched to rows by ID and added or updated, and stage changes go to a history tab.

3. Batch, back off, protect

Writes are batched, a 429 triggers backoff, and sensitive columns are never written.

E5Inside your sheet

The Lever Google Sheets route, one capability at a time

Signal answers whether this should happen. Control answers what exactly gets written. Reconcile answers whether it is still right next month.

What lands in your sheet: candidates, tabs and reports from LeverGoogle Sheets pivot of hires by role with in-cell bars, beside a live chart of net hires by day.Hires by rolePivot table · updates every syncRoleOpenHires hiresApplied412Hiring manager306Offer244Referral188Reference check160Take-home task961.84k1.22k0.96k0.79k0.24k0.88kHires hires by dayBest day 0.42kCandidatesScorecardsDaily applicantsPipelineStage changesReportsCandidatesDashboard

Signal

Intake rule reader

Interprets the Lever payload against the intake rule and stamps the decision on the ledger.

Signal

Stable identity ledger

Records the source key, the time of change and the Google Sheets identifier for each sync, in the Lever to Google Sheets route.

Signal

Map change log

Records every change to the Lever field map, so a later question about a Google Sheets value has an answer.

Control

Keyed row writer

Merges the opportunity and appends history.

Control

Opportunity-and-stage matcher

Keeps a repeat from becoming a second row by checking the opportunity ID, plus the stage and time for history rows before the write.

Control

Tab and column matrix

Decides which tab, columns and exclusions each Lever field uses.

Reconcile

Sheet register

Measures how far each row has slipped from the Lever record and reports it.

Reconcile

Header drift monitor

Spots a renamed header before writes land in the wrong column.

Reconcile

Failure ledger

Records every failed or refused write to Google Sheets with its cause and what was done, for this Lever to Google Sheets route.

Lever offers Google Sheets, lever to Google Sheets historical migration and lever Google Sheets automation are all handled here. Related searches include lever to Google Sheets error handling, lever opportunities data Google Sheets, lever Google Sheets integration, lever opportunities Google Sheets, lever feedback Google Sheets, export lever interviews to spreadsheet, lever to Google Sheets consultant, lever archive reasons sheets, lever Google Sheets Zapier, sync lever candidates to Google Sheets, connect lever to Google Sheets, lever referrals data sheets, lever offers Google Sheets sync, lever to Google Sheets duplicate prevention, lever to Google Sheets, lever to Google Sheets service, lever to Google Sheets Zapier and lever to Google Sheets implementation.

G7Who it is for

Where retail and consumer brands need to keep a Google Sheet of opportunities, stage history and archive reasons, keyed on opportunity ID and updated from Lever changes

Lever holds the record, and Google Sheets is where it is shared, charted and argued over.

Recruiter

"Is the sheet current?"

Opportunities refresh on a schedule.

Head of talent

"Where do people wait?"

History rows give time in stage.

Analyst

"Do not break my pivots."

The layout is fixed and keyed.

Hiring manager

"Show me my postings."

A Summary tab counts by posting.

Security lead

"Keep confidential searches out."

They are never written.

Founder

"No more Monday exports."

The sheet updates itself.

Where the money goes: opportunities, stages and archive reasons

Set the scope, see the Google Sheets price, pick your speed

From $415, with no monthly fee.

View Pricing

One setup fee

I9Your options

Where a weekly export pasted over last week's and zaps stop, a keyed sheet sync begins

Each can fill a sheet. Only one merges opportunities, keeps history and stays inside Google's quotas.

Comparison table: Where a weekly export pasted over last week's and zaps stop, a keyed sheet sync begins
How it gets goinga weekly export pasted over last week'sA typical trigger-and-action zapA BoldBellows keyed sheet sync
What starts the workThe next person to lookEach delivery, repeats includedRule-approved events, logged with the reason
How identity is decidedGuessed from contextA single field treated as the keyOpportunity ID, with stage and time for history
What reaches Google SheetsA few fields, entered lateA copy without contextOne row per opportunity and one history row per stage move
After an uncertain resultOpen both apps and compareRuns again from the startMatches on the opportunity ID, plus the stage and time for history rows, then repairs or holds
BY HANDAUTOMATEDExportCopyPasteFixCheckSendEvery Monday · about 3 hours · errors creep inSync runs on its ownEvery 15 minutes · nobody's time · totals checked

A late arrival

Events that reach the route after a newer one are recognised by timestamp and routed for review instead of applied, for this Lever to Google Sheets route.

Thirty opportunities change stage in the same minute

They are merged in one batched write, history rows are appended in order, the quota holds, and a rerun changes nothing. Finding the row comes first: the opportunity ID, plus the stage and time for history rows is searched, the hit is compared, and only then is an action chosen.

Nothing is written to Google Sheets until the opportunity ID, plus the stage and time for history rows is defined and stored for each row.

Pricing

Build your Lever to Google Sheets price

Pick a package, answer three short questions about how Lever data should reach Google Sheets, and your price and turnaround move as you choose.


Choose your packageRequired

The three packages differ by how much routing, reconciliation and governance sits around the Lever to Google Sheets route.

A focused production route for one Lever environment and one Google Sheets destination, delivering Lever opportunities, stage history and archive reasons written to Google Sheets, merged on opportunity ID, refreshed from updates and paced inside Google's quotas with identity and failure controls from day one.

  • One approved Lever event family and business-state admission rule within the Lever to Google Sheets service.
  • One authorized account, workspace, organization, or base boundary within the Lever to Google Sheets service.
  • One Google Sheets object contract with field and relationship mapping within the Lever to Google Sheets service.
  • Stable matching through Lever account plus candidate, opportunity, posting, interview, or offer ID and a hidden source-key column and destination row ID
  • Tests for duplicates, stale events, malformed data, denied access, and timeouts within the Lever to Google Sheets service.
  • Implementation map, test record, and premium PDF operations handover within the Lever to Google Sheets service.

Adds branching, matching and a bounded historical pass for teams whose route into Google Sheets cannot be one straight-through action, while still delivering Lever opportunities, stage history and archive reasons written to Google Sheets, merged on opportunity ID, refreshed from updates and paced inside Google's quotas.

  • Everything in Launch
  • Up to four approved routing or state-transition branches within the Lever to Google Sheets service.
  • Existing-record resolution and one bounded historical checkpoint within the Lever to Google Sheets service.
  • Lookup-before-replay protection for uncertain writes
  • Named exception ownership and a decision-ready evidence packet within the Lever to Google Sheets service.
  • Field, permission, and destination-state validation before mutation within the Lever to Google Sheets service.

Adds reconciliation and governance for teams that now depend on Lever opportunities, stage history and archive reasons written to Google Sheets, merged on opportunity ID, refreshed from updates and paced inside Google's quotas, with drift detection and an exception register for Google Sheets.

  • Everything in Operations
  • Scheduled source-to-destination reconciliation
  • Schema, field, scope, and webhook drift checks within the Lever to Google Sheets service.
  • Volume-aware retry ceilings and stale-event protection
  • Aged-exception reporting with ownership status
  • Thirty-day release watch and operating review

For Lever to Google Sheets, multi-business-unit routing, unrestricted bidirectional synchronization, regulated archives, unsupported extensions, or additional destination systems receive a separate written quote. Third-party subscriptions and usage charges are excluded.

Which Lever events should reach Google Sheets?Required

Governed lifecycle set: Use this when several approved Lever transitions must converge on one Google Sheets row.

How should Google Sheets recognise a Lever record it has already handled?Required

Ambiguity queue: Route zero-match and multi-match cases to an owner instead of letting Google Sheets guess.

How much Lever context should travel into Google Sheets?Required

Managed repair case: Capture evidence, ownership and a safe next action whenever a Google Sheets write is uncertain.

How soon do you need it live?Required

Standard follows the schedule your other choices set. Pay to move up the queue and go live sooner.

Optional extrasOptional

Each one begins switched off. Turn on what your rollout needs, watch the total, switch it back off.

J11The process

Six steps from weekly paste to a sheet that stays current

Each of the six steps has an output you can read, not just a status update.

  1. Design the tabs

    We map opportunities, history, reasons and summary to tabs, columns and keys.

    Day 1
  2. Approve access

    Access is granted, tested and documented on both the Lever and Google Sheets sides.

    Access review
  3. Fix the tabs and exclusions

    Tab layout and which columns stay blank are drafted and agreed first, along with how rows are matched, on the Lever to Google Sheets route.

    Build phase
  4. Stress the edges

    Late deliveries, doubled events and partial failures are simulated in a test Google Sheets and the results reviewed with you, on the Lever to Google Sheets route.

    Before you review
  5. Launch with notes

    Production begins at a boundary you have agreed, with a PDF covering the rules, owners and repair steps.

    Release day
  6. Post-launch review

    We go through the exception list and the checkpoint log with you and agree what, if anything, needs a change.

    Day 1
Handover for Lever to Google Sheets automation: notes, a checked run and a health checkHandover runbook: a table of what to do when a sync is late, a stage change looks off or a column is added, with an owner for each.RUNBOOK · PLAIN ENGLISHReviewedIf this happensDo thisOwnerA sync is lateCheck the status tab, then re-runYouA stage change looks offOpen Stage changes, match the candidate idYouA column is addedFollow the safe-add stepsUsSheet is shared wronglyRemove the user, keep read-onlyYouYou want a changeSend us one line, we book it inUsYYouYYouUUsYYouUUsWritten for the person who runs the account, not for engineers

K12Turnaround

Delivery windows by package

In the Lever to Google Sheets route, the schedule runs from the day access is granted.

Signal

4 to 7 business days

Control

7 to 11 business days

Reconcile

11 to 17 business days

L13Getting started

What to gather before day one

A named Lever administrator who can approve the connection

Lever read access and a Google Sheet you can edit

Access to the Lever account that holds the records in scope

Your expected behaviour for edits, cancellations and repeats

The hours when changes to Google Sheets are safest to release

Records or dates that the route should ignore

M14Safety and ownership

Narrow permissions, narrow payloads, nothing patched

Neither Lever nor Google Sheets is modified.

Read-only Lever to Google Sheets access: your data stays yoursA vault door with a combination dial and a tick, marked as owned by you and read-only.You own itRead-only

Untouched core, documented edges

Both Lever and Google Sheets are used as their own documentation describes; no workaround reaches into their internals.

Scoped, revocable access

Credentials are limited to the agreed scope, and withdrawing them stops the route at once.

Nothing extra travels

The route forwards what was agreed and ignores the rest, so Google Sheets never becomes a second copy of everything in Lever.

Proof before repetition

Nothing is created twice: a missing confirmation triggers a search of Google Sheets by the opportunity ID, plus the stage and time for history rows before any further write.

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.

N15In their words

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.

Olivia MartinezVerifiedAustin, USA

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.

Sarah MüllerVerifiedZurich, Switzerland

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.

Ravi PatelVerifiedNew Delhi, India

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.

Pedro LimaVerifiedSão Paulo, Brazil

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.

Nadia HassanVerifiedCairo, Egypt

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.

Michael O’ConnorVerifiedDublin, Ireland

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.

Sofia DimitrovVerifiedSofia, Bulgaria

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.

David KimVerifiedSeoul, South Korea

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.

Hannah JohnsonVerifiedChicago, USA

P16FAQ

Lever in Google Sheets: what recruiting teams ask

These are the queries we hear most, with straight replies.

Do I need to be there?No. You send one short brief.Then you review a finished result.Search any question
When is a Lever to Google Sheets Zapier automation not enough?

A zap can provide a hiring sheet that is current without exports. It is not built to merge each opportunity into one row, keep stage history or stay inside Google's quotas. The work here is the judgment around the connector, not the connector itself.

Why not paste a weekly export?

It overwrites history.

What are Google's limits?

300 reads and 300 writes a minute per project, which the route stays inside.

Are pay columns filled in?

By default sensitive columns are excluded.

Will a rerun duplicate rows?

No. Opportunity ID and stage time are the keys.

Can it count hires by posting?

Yes, on a Summary tab.

Does the sheet change Lever?

No. It only receives.

What if my fields change after mapping on the Lever to Google Sheets route?

Mapping is a standard step. Our Lever 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 Lever to Google Sheets route?

Yes. We convert your conditions to a custom Lever workflow for Google Sheets and explain each choice like a Lever 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.

Q17Report 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 Lever data to Google Sheets around them. Signal starts at $415.

  • From $415, paid once
  • Keyed rows
  • Quota-safe
  • No monthly fee from us

Those are scoped and quoted separately.