recipe-collect-form-responses

What This Skill Does

The recipe-collect-form-responses skill provides a structured, automated way to interface with your Google Forms environment directly from the OpenClaw terminal. By leveraging the underlying gws-forms module, this skill acts as an intermediary layer that streamlines the retrieval and visualization of form submission data. Instead of manually navigating through the Google Forms dashboard or parsing spreadsheet exports, users can query their form ecosystem to list existing forms, inspect their metadata, and extract submission responses in a clean, readable table format. This is particularly useful for teams that rely on asynchronous data collection via forms and require immediate, programmatic access to that information for quick decision-making.

Installation

To integrate this functionality into your OpenClaw environment, execute the following command in your terminal:

clawhub install openclaw/skills/skills/googleworkspace-bot/recipe-collect-form-responses

Ensure that you have the gws-forms prerequisite skill installed and properly configured with your Google Workspace authentication credentials before proceeding, as this recipe relies on the established connection to the Google Forms API to function.

Use Cases

• Event Feedback Aggregation: Quickly pull recent survey results after a company event to review attendee feedback without switching browser tabs.
• Application Triage: Monitor incoming applicant forms for a recruitment project to quickly get a snapshot of current candidates.
• Inventory Requests: Collect and review supply request forms submitted by team members during busy periods to streamline procurement tasks.

Example Prompts

1. "Check the responses for my 'Q3 Team Feedback' form and show them to me in a table."
2. "List all my forms, find the ID for the 'Volunteer Sign-up' form, and then pull all the submissions for it."
3. "Get the details for form ID 1abc-2def-3ghi and summarize the latest responses retrieved."

Tips & Limitations

• Prerequisites: Always verify that the form ID matches the specific form you intend to query; using an incorrect ID will result in a 404 or authorization error.
• Permission Scoping: Ensure your workspace account has the necessary viewer or editor permissions on the specific Google Form; otherwise, the gws-forms module will be unable to access the submission data.
• Formatting: The output is optimized for terminal display. If you have a very large volume of responses, the table view might become truncated; in such cases, consider using data-filtering skills if available or exporting to a CSV file through secondary tools.
• Data Privacy: Be mindful that this skill retrieves sensitive user-submitted content. Always handle the output with appropriate data privacy standards, especially if the form contains PII (Personally Identifiable Information).