Google Sheets and Wayback Machine

Google Sheets

Triggers

• Google Sheets New RowTriggers when a new row is added to a Google Sheets spreadsheet.

Actions

• Append rowAppend a single row to the end of a Google Sheet.
• Create spreadsheetCreate a new Google Sheets spreadsheet.
• Delete spreadsheetDelete a Google Sheets spreadsheet permanently.
• Write rowOverwrite a whole row, from column A, with values in column order. To change only some cells of a row, use Update row.
• Update rowSet some cells of one row by column name, leaving the rest of the row as it is. Pair it with Read rows to write a result back to the row it came from. A column that doesn't exist yet is added to the header row.
• Clear row valuesClear values in a specific row without deleting the row itself.

Wayback Machine

Actions

• Check if a page is archivedAsk the Wayback Machine whether it has a copy of a page, and get a link to the nearest one. Point it at a date to ask for the copy closest to that moment instead of the most recent. This is the quickest check to run before following a link that may be dead, or to decide whether the rest of a workflow has anything to work with. No API key required.
• Check several pages at onceRun the same archived-or-not check over a list of URLs and get one row per link, with a Wayback link for the ones that have a copy. Built for auditing the links in a page, a document or a spreadsheet: a URL the archive cannot answer for is reported as unarchived rather than failing the step. Up to 50 URLs. No API key required.
• Get a link to a page as it wasTurn a URL and a date into a link to that page as it looked then, so a message, a document or a citation can point at the archived copy rather than at a page that has since changed. The archive picks the capture nearest the date and says which one it chose. No API key required.
• Get a snapshot's detailsEverything the archive's index records about one capture: when it was taken, what the server said, what kind of file it was, how much was stored, and the content fingerprint that says whether two captures hold the same bytes. Ask for the first capture, the most recent one, or the one closest to a date. No API key required.
• List a page's snapshotsEvery capture of one page, newest first, narrowed to the dates, the kind of response and the kind of file you care about. A busy page is captured many times a day, so thin the list to one capture per day, month or year when you want a timeline rather than every crawl. No API key required.
• List a page's content changesOnly the captures where a page actually changed, with the thousands of identical captures in between left out. This is how you find when a policy was rewritten, when a price moved or when a claim disappeared, without reading every crawl. No API key required.