Google Forms

Operate Google Forms through your OOMOL-connected account. This skill calls the googleforms connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected Google Forms. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "googleforms" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "googleforms" --action "<action_name>" --data '<json>' --json

• --data takes a JSON object string or @path/to/file.json; omit it to send {}.
• The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

• batch_update_form — Apply a batch of Google Forms update requests with optional revision controls and an optional updated form payload. [write]
• create_form — Create a Google Form with a simple title-based input and optionally initialize the description and unpublished state. [write]
• get_form — Retrieve the current structure, settings, publish state, and items of a Google Form.
• get_response — Retrieve a single Google Forms response by its response ID.
• list_responses — List responses for a Google Form with optional filtering and pagination.
• list_watches — List watches configured for a Google Form.
• set_publish_settings — Update whether a Google Form is published and whether it is accepting responses. [write]

Safety

• Untagged actions are reads (get / list / search) — safe to run directly.
• Actions tagged [write] change Google Forms state — confirm the exact payload and effect with the user before running.
• Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell
  

• Not signed in / authentication error — sign in to your OOMOL account once:

  oo auth login
  

• scope_missing / credential_expired / app_not_ready / app_not_found — Google Forms is not connected, or the connection expired or lacks a scope. Connect once (auth type: OAuth2) at:

  https://console.oomol.com/app-connections?provider=googleforms
  

• HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources

• Google Forms homepage: https://workspace.google.com/products/forms/