sheetwork
Contribute on GitHubChat on Discord
v1.0.0 Nicolas Jaar
v1.0.0 Nicolas Jaar
  • Introduction
  • Installation & Configuration
    • Installation & Update
    • Configuration
      • Set up your sheetwork project
      • Connecting to Google Sheets
      • Set up your sheetwork profile
  • Usage
    • Quick CLI
    • Using sheets.yml configuration
      • Basic Configuration
      • Column Operations & Advanced Controls
  • Sheetwork Operations
    • sheetwork init
    • sheetwork upload
    • Under the Hood Cleanups
  • FAQ
    • Do I need to list ALL the columns in my sheets config?
    • Do the column names need to be in the format of the original sheet?
    • What kind of cleanups or reformating does sheetwork do?
Powered by GitBook
On this page

Was this helpful?

  1. Usage
  2. Using sheets.yml configuration

Basic Configuration

Basic Configuration

Sheet Details

  • sheet_name: this is the name by which you'll want to refer to your sheet. It can be anything you like and doesn't have to be the google sheet name. We will refer to the sheet using the sheet_key as it's less error prone

  • sheet_key: this is a unique key automatically created for every sheet by google. It's easy to spot, when you have your sheet opened, if you look at the URL it will be something like that. In the example below the key is 10JJdwwd_lm4556uwedu4zu5u6r0h2VIDTjRXg it always follows the /d/ and precedes the /edit part.

https://docs.google.com/spreadsheets/d/10JJdwwd_lm4556uwedu4zu5u6r0h2VIDTjRXg/edit#gid=0
  • target_schema: This one is optional if you set up a target_schema in your project file. If you did not, or you want to override the default you can just specify it here!

  • target_table: This will be the name of the table in which sheetwork will push your data from the sheet.

PreviousUsing sheets.yml configurationNextColumn Operations & Advanced Controls

Last updated 5 years ago

Was this helpful?