Power your event schedule page from a Google Sheet

Why run your agenda from a spreadsheet

Event schedules change up to the last minute — a talk gets moved, a speaker drops, a room changes. The one tool your organizers already share and edit in real time is a spreadsheet, not a CMS. Keep the agenda there, one row per session, and let the website read from it.

PasteSheet sits in front of the sheet and serves it as clean, typed JSON. Your schedule page — Next.js, Astro, a no-code builder, or plain HTML — fetches the rows and renders the grid. Edit a start time in the sheet and the page reflects it after the cache refreshes.

What each row becomes

Give every session a row and a few columns, then slice it however the page needs:

• ?day=Thursday — build a per-day tab from an exact-match filter.
• ?track=Frontend — split the agenda into parallel tracks or stages.
• ?sort=start_time — order sessions chronologically without touching code.
• ?search=livewire — let attendees find a talk by keyword across every column.

Fetch the agenda as JSON

Point your schedule page at one tab and pull the sessions you want. Filters, sorting, and paging are plain URL parameters:

curl "https://pastesheet.com/your-endpoint/Sessions?day=Thursday&track=Frontend&sort=start_time"

{
  "data": [
    {
      "title": "Scaling Livewire to a Million Users",
      "day": "Thursday",
      "track": "Frontend",
      "room": "Hall B",
      "start_time": "14:30",
      "speaker": "Amara Okafor"
    }
  ]
}

Safe to publish, nothing to wire up

Because the endpoint is read-only by design, it is safe to expose publicly or hand to a teammate: consumers can read and query the data but can never change the sheet. And there is no Google Cloud project, OAuth screen, or service account to set up — you paste a share URL and get a live API.

What it costs

Frequently asked questions

Sources

• Usage limits — Google Sheets API — Google

Related use cases