Skip to content
Nappai Documentation

Google Forms Webhook

This component automatically watches a specific Google Form you select. When someone submits a new response, it captures the answers, organizes them into a clear format, and sends the data forward in your workflow so other nodes can use it.

How it Works

The component works like a continuous observer for your Google Form. Instead of you manually checking for new entries, it regularly checks (polls) Google’s servers for any new responses. When a new submission is detected, the component automatically extracts the answers, matches them to the correct questions, and structures everything into a clean, easy-to-read format. This data is then passed along to the next steps in your workflow, ready for storage, analysis, or AI processing.

The component is designed to handle data smoothly: it accepts raw submissions, converts them into a structured layout, and provides both a human-readable summary and a precise data structure that other nodes in Nappai can easily read and use.

Connection & Credentials

This component requires configuring a credential in the Nappai panel before interacting with the external service:

  1. Go to the Credentials section in your Nappai panel.
  2. Create a new credential of the type Google Forms and fill in the required fields (Project, Client ID, Client Secret, and Google Forms access). You can find your API key in the Google Cloud Console.
  3. In your workflow, select the saved credential in the Credential input field of this node.

Inputs

The following fields are available to configure this component. Each field may be visible in different operations:

  • Form: Select the Google Form you want to monitor for new responses. You will see a dropdown or file selector where you can pick the specific form connected to your Google account.

Outputs

The component generates a Data output containing every new form submission it detects. Each output item includes a human-readable summary and a structured list of all answers, making it easy to pass to other nodes like databases, AI agents, or notification systems.

Output Data Example (JSON)json

{ “preview_text”: “Submitted on 2024-05-20: ‘What is your name?’, ‘Jane Doe’; ‘How satisfied?’, ‘Very Satisfied’ (+0 more)”, “event_data”: { “form_id”: “1FAIpQLSc…”, “submitted_at”: “2024-05-20T14:30:00Z”, “answers”: [ {“question”: “What is your name?”, “value”: “Jane Doe”}, {“question”: “How satisfied are you?”, “value”: “Very Satisfied”} ] } }

Connectivity

This component is typically placed at the start of a workflow to capture incoming form data. You can connect its Data output to:

  • Database or Spreadsheet nodes to automatically save every submission for record-keeping.
  • AI/LLM nodes to analyze feedback, summarize comments, or categorize responses automatically.
  • Notification nodes (like Email, Slack, or Teams) to alert your team when a high-priority or specific response comes in.
  • Filtering or Transformation nodes to clean, sort, or route only certain answers based on user criteria.

Usage Example

Imagine you run a monthly customer satisfaction survey using Google Forms. By adding the Google Forms Webhook node and pointing it to your survey, Nappai will automatically check for new entries every few minutes. Whenever a customer submits their feedback, the node captures it and passes the data to an AI agent that summarizes the comments and sends a daily digest to your team’s Slack channel. No manual checking required!

Tips and Best Practices

  • Always ensure your Google Form is publicly accessible or shared with the connected Google account to avoid polling errors.
  • Use connected AI or LLM nodes immediately after this component to automatically categorize, summarize, or flag important responses.
  • If you expect a high volume of submissions, add a filtering node downstream to only process responses that meet specific criteria (e.g., rating = “Low”).
  • Keep the polling frequency reasonable in the webhook settings to balance timely updates with Google’s API usage guidelines.
  • The component automatically handles data validation, but always verify that sensitive personal information (PII) is handled securely in downstream nodes according to your compliance policies.

Security Considerations

  • The credential setup requires API keys from Google Cloud Console. Keep these keys secure and never share them publicly or commit them to version control.
  • Only grant the necessary permissions (Google Forms access) to your Nappai credential to follow the principle of least privilege.
  • Regularly rotate or update your Google Cloud credentials if you notice any unauthorized access or API quota issues.
  • The component automatically handles data validation, but ensure any downstream nodes handling personal data comply with your organization’s security and privacy policies.