Google Forms Python API Docs | dltHub

Build a Google Forms-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Google Forms API is a RESTful interface that allows users to programmatically create and modify forms, retrieve form responses, and set up notifications for form changes. The REST API base URL is https://forms.googleapis.com and all requests require a Bearer token via OAuth 2.0.

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Google Forms data in under 10 minutes.


What data can I load from Google Forms?

Here are some of the endpoints you can load from Google Forms:

ResourceEndpointMethodData selectorDescription
formsv1/forms/{formId}GETGet a form
forms_responses_listv1/forms/{formId}/responsesGETresponsesList a form's responses
forms_responses_getv1/forms/{formId}/responses/{responseId}GETGet one response from the form
forms_watches_listv1/forms/{formId}/watchesGETwatchesReturn a list of the watches owned by the invoking project
forms_createv1/formsPOSTCreate a new form
forms_batch_updatev1/forms/{formId}
POSTChange the form with a batch of updates

How do I authenticate with the Google Forms API?

Authentication requires an OAuth 2.0 access token passed in the Authorization header using the Bearer scheme. The header must be formatted as 'Authorization: Bearer <ACCESS_TOKEN>'.

1. Get your credentials

The Google Forms API requires OAuth 2.0 authentication, not a simple API key, to access user data. Follow these steps in the Google Cloud Console: 1. Go to APIs & Services > Credentials. 2. Configure the OAuth consent screen if you haven't already. 3. Click Create Credentials > OAuth client ID. 4. Select Application type (e.g., Desktop app). 5. Download the JSON file containing your client secrets. 6. Use these credentials to obtain an OAuth access token, which your application will include in requests as a Bearer token in the 'Authorization' header.

2. Add them to .dlt/secrets.toml

[sources.google_forms_source] oauth_access_token = "ya29.a0AfH6SMA..."

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Google Forms API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python google_forms_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline google_forms_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset google_forms_data The duckdb destination used duckdb:/google_forms.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads v1/forms/{formId} and v1/forms/{formId}/responses from the Google Forms API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def google_forms_source(credentials=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://forms.googleapis.com", "auth": {"type": "bearer", "token": credentials}, }, "resources": [ {"name": "forms_responses_list", "endpoint": {"path": "v1/forms/{formId}/responses", "data_selector": "responses"}}, {"name": "forms_watches_list", "endpoint": {"path": "v1/forms/{formId}/watches", "data_selector": "watches"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="google_forms_pipeline", destination="duckdb", dataset_name="google_forms_data", ) load_info = pipeline.run(google_forms_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("google_forms_pipeline").dataset() sessions_df = data.forms_responses_list.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM google_forms_data.forms_responses_list LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("google_forms_pipeline").dataset() data.forms_responses_list.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Google Forms data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Google Forms?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines