Skip to main content

Integration guideSeal API and Scripts

Google Sheets

Exchange spreadsheet data with structured Seal records.

Illustration of a seal beside a laptop showing a data table and an evidence binder linked by a red thread.

Google Sheets and SealSeal API and Scripts

Seal reads
Rows from sheets with a fixed layout
Writes back
Seal data, to a sheet for reporting
Source of truth
Agreed when scoped
Set up
Scoped with your team
Neil › Linked record review
draft

Link these Google Sheets records to the change they support.

Neil

  • Once the connection is configured, I’ll use the records it provides and cite each one. Anything it doesn’t supply stays listed as missing.
Reads
Rows from sheets with a fixed layout
Returns
  • Google Sheets records and the work they support
  • Missing or unmatched information
  • Next steps for your team to review
Illustrative work with Google Sheets: a request to Neil, the source it reads and the draft it returns for your review.

1What’s connected.

Import structured data from Google Sheets into Seal records, or send Seal data to a sheet for reporting, through a connection set up with Seal’s API or Scripts. Fix the sheet layout and check each import against the expected columns.

Connection setup and permissions

Use Seal’s APIs or scripting engine for a connection tailored to your process. Agree the data mapping, access and direction of transfer before implementation.

2Read and write fixed-layout Google Sheets ranges.

Route

values.get reads a range from a spreadsheet, values.update writes one, and values.append adds rows after the last row of the table it finds.⁠¹²³ Reads return formatted values by default. UNFORMATTED_VALUE returns calculated values without formatting, and dates and times then arrive as serial numbers.⁠¹⁴ A write is RAW, stored as sent, or USER_ENTERED, parsed as if typed.⁠⁵

Record identity

Spreadsheet and sheet IDs stay the same when renamed, but a cell has no ID of its own: it is identified by its coordinates.⁠⁶

Revisions

Each change creates a Drive revision, but revisions may be merged, so the API may not show every change.⁠⁷

When it fails

Requests are refused with 429
The quota is 300 reads and 300 writes a minute per project and 60 per user, and going over returns 429.⁠⁸ Send rows in batches and back off before retrying.
An update changed nothing
Requests are atomic: if any part is invalid, no change is applied.⁠⁸ Fix the invalid part and resend the whole request.

Check one record

Import one sheet with the agreed columns and another with a column inserted. The first should create Seal records with dates and numbers intact. The second should be rejected, because an inserted column moves every cell after it.

3Start with the job.

Tell us what Neil needs to do and which records it needs. We’ll confirm the interface, permissions and implementation scope with your team.

Discuss this connection →

4Before it goes live.

Access and any write-back

Define which records are in scope and whose permissions apply. Whether the connection writes back at all is a separate decision, with its own mapping and approval.

Verification and release

Review the configured connection for its intended use. Keep the requirements, checks and evidence with the change, and approve the release through your team’s controls.

Read the assurance detail →

References

  1. 1Sheets API: spreadsheets.values.get.
  2. 2Sheets API: spreadsheets.values.update.
  3. 3Sheets API: spreadsheets.values.append.
  4. 4Sheets API: ValueRenderOption.
  5. 5Sheets API: ValueInputOption.
  6. 6Sheets API: concepts.
  7. 7Drive API: changes and revisions overview.
  8. 8Sheets API: usage limits.