How do I connect Wayback Machine to Lodol?

Authenticate Wayback Machine once from your workspace and every action and trigger it supports becomes available to drop into a workflow. There is no glue code to write or maintain.

All integrations

Wayback Machine

Research & AcademiaWeb SearchUtilities

Read the web's past from the Internet Archive's Wayback Machine: check whether a page is archived, list every copy of it, find the captures where it actually changed, and read or download any of them. Audit a list of links for dead ones, watch a competitor's pricing page for changes, recover a document a site has taken down, or map every page a site had before it disappeared. Free and public: no account, no API key, and nothing to pay for.

Get Started Browse all integrations

20 actions

Actions

Steps your workflow can run in Wayback Machine.

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.

List a site's archived pagesThe distinct pages the archive holds under a site, one row per page rather than per capture of it. This is the site map of a site that no longer exists, or the list to run the rest of a workflow over. Cover a path, a host, or the site and all of its subdomains. No API key required.

List a site's archived filesThe files of one kind the archive holds under a site: the PDFs a regulator published and later withdrew, the images a brand used, the feeds a blog served. One row per file, each with a link that serves the original bytes. No API key required.

List a site's broken pagesThe pages under a site that a crawler found broken: 404s, server errors and redirects, as they were when the archive reached them. Run it after a migration to find what the redirects missed, or over a competitor's site to see what they took down. No API key required.

Get a page's capture historyHow often a page has been captured, year by year and month by month, with its first and last capture. This is the shape of a page's life in the archive: whether it is watched closely, was captured once and forgotten, or stopped being captured at some point. No API key required.

Count captures day by dayHow many times a page was captured on each day of a year, or of one month. This is the calendar the Wayback Machine draws, and the cheap way to find the days worth looking at before asking for the captures themselves. No API key required.

List captures on one dayEvery capture of a page on one day, with the crawl behind each one. The archive is filled by many projects at once, and this is the only view that says which: the live-web crawler, a focused crawl, an Archive-It partner's collection, or someone clicking Save Page Now. No API key required.

Summarize what is archived for a siteHow much of a whole site the archive holds, year by year: how many captures it made, how many distinct pages those covered, how many pages it saw for the first time, and the breakdown by file type. Run it before a deeper crawl of the archive to know what is there. No API key required.

Get a page's Memento timemapA page's history in the Memento format defined by RFC 7089: the original URL, the gateway that resolves a date to a copy, and the first, last and intermediate copies with their dates. Use it when the history has to be handed to another Memento-aware tool rather than read here. No API key required.

Read an archived pageRead a page as it was, so a later step can summarise it, search it or answer questions about it. The text comes back with the markup stripped and none of the Wayback banner in it, or as the original source if that is what you need. Leave the date blank for the most recent copy. No API key required.

Download an archived fileDownload an archived file as it was captured, so a later step can attach it to an email, post it to a chat or put it in storage. Anything the archive holds comes back this way: a PDF a site has taken down, an image, a data file, a page. No API key required.

Compare two snapshotsCompare a page as it was at two moments and get back what was added and what was removed, in the words a reader would have seen rather than as a diff of markup. The archive's own content fingerprints are checked first, so a page that did not change at all is reported as identical outright. No API key required.

Export snapshots as CSVWrite a capture list out as a CSV file instead of into the workflow, so tens of thousands of rows can be attached to an email, put in storage or handed to a spreadsheet. Takes the same filters as the listing actions, with a much higher ceiling. No API key required.

Search archived sitesSearch the archive for sites by name or by what they are about, and get back how many captures each has and the years they run between. Use it to find the site to point the rest of a workflow at when you do not already know the address. No API key required.

Suggest archived hostsComplete a partly typed address into hosts the archive actually holds, subdomains and all: 'nasa' becomes www.nasa.gov, science1.nasa.gov and the rest. Run it before a site-wide query so the query is spent on a host that exists. No API key required.