Skip to main content
Per-app Google setup is deprecated. All Google apps now share one Google OAuth client and one Redirect URI. To use your own client, follow the Google setup guide. Credentials saved for one Google app apply to all of them.

​
Overview

OneCLI connects AI agents to Google Forms through Google’s OAuth flow. Agents can create forms, add questions, and read submitted responses. The gateway injects OAuth credentials into requests to the Google Forms API automatically. This is useful for agents that need to collect feedback, create surveys, or process form submissions.

​
What you will set up

  • A Google OAuth client shared by every Google app in OneCLI
  • A Google Forms connection authorized with your account
  • Per-agent, per-tool access to forms and responses

​
Connect Google Forms

This applies on OneCLI Cloud and self-hosted alike. One Google client serves every Google app in OneCLI, so you set it up once. If you already did it for another Google app, skip to step 2.

1. Set up your Google client

Follow the Google setup guide. It enables the Google APIs, sets up the consent screen, creates the OAuth client, and adds the Redirect URI.
Open Connections > Google Forms, select Connect Google Forms, pick your Google account, and click Allow.
OneCLI connect window for Google Forms showing Configuration required, the setup guide link, and the Configure credentials button.

The Google Forms connect window before a Google client is set up.

​
What agents can do

  • Create new forms with a title and description
  • Add questions (multiple choice, short answer, paragraph, checkbox, dropdown, scale)
  • Read form structure (questions, sections, settings)
  • Read all submitted responses
  • Get individual response details
  • Set up and manage response watches (notifications for new submissions)
  • Update form metadata (title, description)
  • Modify existing questions

​
Controlling access

Access is per agent: grant the connection to each agent that needs it, choosing per tool what runs freely, what needs human approval, and what stays blocked — a read-only agent is a single grant. Organization rules add guardrails on top, like rate limits and blanket blocks. Everything is checked before credential injection, so a blocked request never reaches Google Forms.

​
FAQ

Yes. Follow the Google setup guide once. One client serves every Google app in OneCLI.
No. The token stays in OneCLI, and the gateway adds it at the proxy. See How it works.
Yes. Allow read tools and block writes when you grant the connection.