Google Calendar Live Query Actor

What does Google Calendar Live Query Actor do?

This Google Calendar Actor sends a user-provided query to a live public Google Calendar source and writes multiple normalized records to the Apify dataset. The default query is deliberately non-empty and is tested with a default maxItems of 10; increase it up to 100 when the source supports more results. It does not use static fixtures, log in, solve CAPTCHAs, or access private account data.

This service uses a strict live adapter: if the public source does not expose enough rich records, the run fails and does not pad the dataset with unrelated autocomplete suggestions.

The Actor is packaged as an independent Apify project with API access, scheduling, monitoring, integrations, and local dataset output. Open the official service at Google Calendar to compare the live results with the source UI.

Why use Google Calendar Live Query Actor?

Use it for live research, search discovery, market monitoring, content planning, QA checks, and downstream automation. Each run preserves the original query, source URL, result URL, record position, and retrieval timestamp so consumers can distinguish current results from older runs. Rich adapters expose service-specific fields inside details; account-only services remain public-only and never fabricate private metrics.

Apify adds reliable dataset storage, API download, scheduling, run monitoring, integrations, and optional proxy configuration. The Actor never treats scraped page text as code and never fabricates a result when the public source is unavailable.

What data can this Actor extract?

Field	Type	Description
query	string	The live query used for this run.
itemPosition	number	One-based position in the returned dataset.
title	string	Result, topic, place, app, book, video, translation, or suggestion title.
description	string	Live snippet, address, summary, or source description when available.
url	URL	Public result or service reference URL.
sourceUrl	URL	Public endpoint/page used for live retrieval.
details	object	Service-specific metadata such as ratings, authors, image URLs, coordinates, or translations.
scrapedAt	date-time	UTC time at which the record was fetched.

How to scrape Google Calendar data

1. Open the Actor input tab and enter a query such as Google Calendar events.
2. Set maxItems to 10 for a quick run or a higher value up to 100. Keep minItems at 10 when you want the Actor to fail rather than accept an undersized live response.
3. Choose hl, gl, and a request timeout when regional or language-specific results matter.
4. Click Start. Inspect the dataset and download it as JSON, HTML, CSV, or Excel, or call the Actor through the Apify API.

Input

See the Input tab for the full configuration. The important fields are query, maxItems, minItems, hl, gl, requestTimeoutSecs, optional proxyConfiguration, optional flight departureDate/returnDate, optional hotel checkInDate/checkOutDate, and targetLanguages for Google Translate. The local default input is stored in storage/key_value_stores/default/INPUT.json.

Run locally from this directory with:

apify validate-schema
apify run --purge

Google access challenges

If Google presents an unusual-traffic or regional access challenge during a local Search, Images, or Lens run, provide an enabled proxy in proxyConfiguration (for example {"useApifyProxy":true,"countryCode":"US"}) or provide custom proxyUrls. Apify Proxy external access must be enabled for the account. Search and Images can also use the official Google Custom Search JSON API when GOOGLE_API_KEY and GOOGLE_CSE_ID are configured as environment secrets. These strict Actors never replace blocked results with autocomplete, static fixtures, or unrelated records.

Output

The Actor writes one dataset item per live result, not one metadata record for the whole service. You can download the dataset in various formats such as JSON, HTML, CSV, or Excel.

{
  "serviceName": "Google Calendar",
  "query": "Google Calendar events",
  "itemPosition": 1,
  "maxItems": 10,
  "live": true,
  "recordType": "liveResult",
  "title": "Live result title",
  "url": "https://calendar.google.com/",
  "sourceType": "help-search-live",
  "scrapedAt": "2026-01-01T00:00:00.000Z"
}

How much does it cost to scrape Google Calendar?

Local runs have no Apify platform charge. Cloud cost depends on your Apify plan and runtime. The default run is bounded to a small number of public requests and 10 records; larger maxItems values can increase requests and compute usage. If you configure an official Google API key, that provider may apply its own quota or billing rules.

Tips and advanced options

• Keep maxItems at 10 while testing a query, then raise it to 100 for supported sources.
• Use a precise query and matching gl country code for more relevant live results.
• Inspect sourceType, details.extractionLevel, and details.accessNote to understand whether a row came from a direct public feed, a rendered result card, an official API, or live discovery autocomplete.
• Services that require OAuth are intentionally public-only. Supply an approved API integration in a future adapter if private account data is needed.

FAQ, disclaimers, and support

Some Google services are authenticated or client-rendered. In those cases this Actor reports live public information or live query suggestions and never inserts static placeholders. Google may rate-limit or change public markup, so review sourceType, scrapedAt, and run logs when a source changes.

Our Actors are ethical and do not extract private user data, such as email addresses, gender, or location. They only extract what the user has chosen to share publicly. You should not scrape personal data unless you have a legitimate reason and comply with GDPR and other applicable laws. Review the target site terms, use the Issues tab for feedback, and use the API tab for programmatic access.

For a custom authenticated integration, use the appropriate Google API with the user’s consent and credentials instead of bypassing access controls.