> ## Documentation Index
> Fetch the complete documentation index at: https://www.octoparse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Google Sheets integration

> Export Octoparse task data to Google Sheets for spreadsheet-based review, sharing, and reporting.

The Google Sheets integration lets you send Octoparse task results to a spreadsheet. It is useful when teams want to review, share, filter, or report on extracted data without downloading files manually.

Use Google Sheets for lightweight workflows where spreadsheet access is enough and the dataset size is manageable.

## When to use Google Sheets

Use Google Sheets when:

* Business users need to review extracted data
* The data should be shared with teammates
* You need a simple destination for recurring exports
* The results feed a report, dashboard, or manual process
* You do not need a database or custom application pipeline

## Typical workflow

<Steps>
  <Step title="Prepare the task output">
    Run a sample task and confirm field names, record count, and data quality.
  </Step>

  <Step title="Connect Google Sheets">
    Authorize the Google account that should receive the exported data.
  </Step>

  <Step title="Choose the spreadsheet destination">
    Select or configure the target spreadsheet and sheet.
  </Step>

  <Step title="Set export behavior">
    Octoparse automatically exports non-exported data records only.
  </Step>

  <Step title="Run and verify">
    Run the task and confirm that the data appears correctly in Google Sheets.
  </Step>
</Steps>

## Before exporting

Check:

| Check                                     | Why it matters                                                         |
| ----------------------------------------- | ---------------------------------------------------------------------- |
| Field names                               | Become spreadsheet column headers                                      |
| Data volume                               | Very large datasets may be better suited for databases                 |
| Duplicates                                | Recurring exports can create repeated rows if not configured carefully |
| Access permissions                        | The connected Google account needs access to the target sheet          |
| [Data cleaning](/docs/en/platform/refine-data) | Cleaner field values reduce manual spreadsheet cleanup                 |

## Best practices

* Finalize field names before connecting the export.
* Test with a small dataset first.
* Use clear sheet names.
* Avoid manually editing column headers that are controlled by the export.
* Monitor the first few scheduled exports if the task runs automatically.

## Common errors

| Error                      | Cause                                                   | Fix                                                               |
| -------------------------- | ------------------------------------------------------- | ----------------------------------------------------------------- |
| Account dropdown is empty  | No Google account authorized                            | Click Authorize new account                                       |
| Sheet list won't load      | Account authorization expired                           | Re-authorize the account                                          |
| `Insufficient permissions` | Connected account lacks edit access to the target sheet | Share the sheet with the connected account, or pick another sheet |
| `Spreadsheet not found`    | Target spreadsheet was deleted or moved                 | Re-select the destination spreadsheet                             |
| Export stops mid-run       | Google Sheets row limit (1,048,576 rows) reached        | Switch to a database destination                                  |

<Tip>
  Google Sheets is convenient for collaboration and review. For larger or production-grade pipelines, consider a [database](/docs/en/platform/postgresql) or cloud storage destination.
</Tip>