Download the PHP package revolution/laravel-google-sheets without Composer

Google Sheets API v4 for Laravel

Overview

This package provides a Laravel-idiomatic and streamlined interface for interacting with Google Sheets API v4. It abstracts away the underlying Google PHP client complexity, letting developers read, write, update, and manage spreadsheets with expressive, fluent methods that feel natural in Laravel applications.

Key Features:

• Multi-method Authentication: Supports OAuth 2.0 (user-specific access), Service Account (server-to-server), and API key (public data access)
• Fluent API: Chainable methods for data and sheet operations with intuitive syntax
• Laravel Collection Integration: Seamlessly converts Google Sheets data into Laravel Collections for easy manipulation
• Extensibility: Macro system allows you to add custom methods to the main facade
• Drive Integration: Built-in Google Drive API support for spreadsheet management

Common Use Cases:

• User Dashboards: Display and interact with Google Sheets data in your application
• Import/Export: Bulk data operations between your Laravel app and Google Sheets
• Automated Reports: Generate and update reports programmatically
• Multi-user Applications: Each user can manage their own Google Sheets with proper authentication

Concept

The main purpose of this package is reading from Google Sheets. Instead of specifying detailed conditions before reading, it is assumed that you first retrieve all data as a Laravel Collection and then process the data on the Laravel side.

Requirements

• PHP >= 8.2
• Laravel >= 11.0

Installation

Composer

Laravel Configuration

1. Run php artisan vendor:publish --tag="google-config" to publish the google config file

2. Enable Google APIs in Google Cloud Console:

   • Google Sheets API
   • Google Drive API
3. Choose your authentication method and configure accordingly (see Authentication section below)

Demo & Examples

• Working Demo: Laravel Google Sheets Demo
• Example Project: google-sheets-project

Related Google API Packages:

• Laravel Google Photos
• Laravel Google Search Console

Authentication

You must choose an authentication method based on your use case. This package supports three authentication methods:

Scopes setting is required in config/google.php for both OAuth and Service Account authentication. Example:

Authentication Methods Comparison

Service Account (Recommended for most applications)

Best for: Background jobs, automated systems, server-to-server access

Access spreadsheets that your application owns or has been granted access to. No user interaction required.

📖 Complete Service Account Setup Guide →

OAuth 2.0

Best for: Applications where users access their own Google Sheets

Users grant permission to access their personal Google Sheets. Requires user consent flow.

📖 Complete OAuth Setup Guide →

API Key (Public Access Only)

Best for: Accessing publicly shared, read-only spreadsheets

Limited to reading data from spreadsheets that are publicly accessible. No authentication flow required.

To use API Key authentication:

1. Get an API Key from Google Cloud Console
2. Ensure your spreadsheet is publicly accessible (shared with "Anyone with the link")
3. Use the key in your application:

⚠️ API Key Limitations:

• Read-only access
• Only works with publicly shared spreadsheets
• No write operations (update, append, delete)
• No access to private spreadsheets

Quick Start

Here's how to get started quickly with each authentication method:

Using Service Account (Recommended)

1. Setup: Follow the Service Account Setup Guide

2. Configure: Add to your .env file:

3. Share: Share your Google Sheet with the service account email
4. Use: Start reading/writing data:

Using OAuth 2.0

1. Setup: Follow the OAuth Setup Guide
2. Configure: Add OAuth credentials to your .env file
3. Authenticate: Handle user authentication flow
4. Use: Access user's spreadsheets:

Using API Key (Public Access)

1. Setup: Get API key from Google Cloud Console

2. Configure: Add to your .env file:

3. Use: Read public spreadsheets:

Usage

Consider this example spreadsheet structure:

Spreadsheet URL: https://docs.google.com/spreadsheets/d/{spreadsheetID}/...

Service Account Usage

When using Service Account authentication, no token setup is required:

OAuth Usage

When using OAuth authentication, you need to set the user's access token:

Get a sheet's values with the header as the key (Recommended)

Collection conversion is simple and subsequent processing is flexible, so this method is recommended.

Blade

Using A1 Notation

About A1 Notation

A1 Notation is the standard way to specify a cell or range in Google Sheets (e.g., 'A1', 'A1:B2').

• 'A1' refers to the cell at column A and row 1.
• 'A1:B2' refers to the range from cell A1 to B2 (rectangle).
• 'A:B' refers to all rows in columns A and B.

If you are not familiar with A1 Notation or your range is dynamic/complicated, it is often easier to fetch all data and use Laravel Collections to process/filter it after retrieval.

Updating a specific range

Append a set of values to a sheet

Append a set of values with keys

Add a new sheet

Deleting a sheet

Specifying query parameters

https://developers.google.com/sheets/api/reference/rest/v4/spreadsheets.values/get#query-parameters

Use original Google\Service\Sheets

see https://github.com/google/google-api-php-client-services/blob/master/src/Google/Service/Sheets.php

FAQ

Which authentication method should I use?

• Service Account: Best for most Laravel applications, automated systems, and background jobs
• OAuth 2.0: Use when users need to access their own Google Sheets
• API Key: Only for reading public spreadsheets (very limited use cases)

How do I share a spreadsheet with my Service Account?

1. Open your Google Sheet
2. Click the "Share" button
3. Find the client_email in your service account JSON file
4. Share the spreadsheet with this email address
5. Grant "Editor" permissions for read/write access

Can I access multiple spreadsheets?

Yes! You can access any spreadsheet that:

• Is shared with your service account (Service Account method)
• The authenticated user has access to (OAuth method)
• Is publicly accessible (API Key method)

How do I handle authentication errors?

Common solutions:

• Service Account: Ensure the spreadsheet is shared with the service account email
• OAuth: Check if the access token is expired and refresh it
• API Key: Verify the spreadsheet is publicly accessible

How do I deploy this to production?

• Store service account credentials securely (outside web root)
• Use environment variables for all configuration
• Never commit credential files to version control
• Consider using different service accounts for different environments

LICENSE

MIT License