gws-forms

What This Skill Does

The gws-forms skill provides a powerful command-line interface for OpenClaw agents to programmatically interact with Google Forms. It bridges the gap between static surveys and dynamic, automated workflows. By leveraging this skill, you can create new forms, retrieve existing form structures, modify form properties via batch updates, and manage response collection or watch triggers. It is designed to be highly modular, relying on the Google Workspace shared authentication framework to ensure secure interactions with your cloud-based data.

Installation

To integrate this skill into your environment, run the following command within your OpenClaw CLI: clawhub install openclaw/skills/skills/googleworkspace-bot/gws-forms Ensure that you have completed the prerequisite setup by checking ../gws-shared/SKILL.md to configure your API credentials and environment-specific security policies. If the shared configuration is missing, execute gws generate-skills to initialize the necessary framework.

Use Cases

This skill is ideal for automating data intake and survey lifecycle management. Common use cases include:

• Automated Survey Creation: Generate daily or weekly check-in forms with standardized titles based on project parameters.
• Response Monitoring: Use the watches resource to trigger notifications or further data processing when a new submission arrives.
• Dynamic Form Updates: Use batchUpdate to modify specific questions, validation rules, or settings based on changes in other integrated business systems.
• Enterprise Provisioning: Automatically create forms for new project folders or client accounts during the onboarding process.

Example Prompts

1. "Create a new Google Form titled 'Weekly Sprint Retro' and confirm it's ready for me."
2. "Get the current responses for the 'Customer Feedback' form and summarize the latest 5 entries."
3. "Update the publish settings for the 'Internal Event Registration' form to restrict responses to users within our domain."

Tips & Limitations

• Order of Operations: When creating a form, remember that forms.create only establishes the title. You must execute a secondary forms.update call to inject questions, description text, or specific item settings.
• Schema Inspection: Always use gws schema forms.<resource>.<method> before constructing complex --json payloads to ensure you are referencing the correct object fields and required parameters.
• Legacy Support: Be aware that the setPublishSettings method will fail on legacy forms, as they lack the necessary metadata field. If you encounter issues, verify the form version or migrate it to a modern form format.