How to Automate Collecting Post-Demo Feedback with n8n

Collecting post-demo feedback is essential for product teams to understand customer needs, improve demos, and close deals faster. 🚀 However, manually gathering this feedback can be time-consuming and error-prone.

In this article, we’ll explore how to automate collecting post-demo feedback with n8n, a powerful open-source workflow automation tool. We’ll guide startup CTOs, automation engineers, and operations specialists through building an end-to-end automated workflow that integrates services like Gmail, Google Sheets, Slack, and HubSpot.

By the end, you’ll have a comprehensive, practical, and scalable automation that improves feedback collection, reduces manual work, and accelerates your product iterations.

Understanding the Problem: Why Automate Post-Demo Feedback?

Post-demo feedback is the bridge between your product presentation and customer adaptation. Yet, collecting it manually poses challenges:

• Delayed feedback retrieval leads to stale or lost insights.
• Manual consolidation causes errors and inconsistency.
• Missed opportunities to address customer concerns promptly.

Automating this process benefits:

• Product teams by providing timely, structured feedback data.
• Sales and customer success by enabling quicker follow-ups.
• Operations and automation engineers by offering a robust, error-tolerant system.

Now, let’s move forward to building an automation that captures, aggregates, and notifies your team about demo feedback effectively.

Tools and Services for Automation

Our workflow uses the following tools, chosen for their integration capabilities with n8n and relevance to product teams:

• n8n — Workflow automation platform.
• Gmail — To send and receive post-demo feedback request emails.
• Google Sheets — For centralized storage and analysis of feedback.
• Slack — To notify product teams instantly about new feedback.
• HubSpot — To tag and track contacts related to demos.

An End-to-End Workflow to Automate Collecting Post-Demo Feedback

Our goal: After a demo, automatically send feedback requests, collect responses, log them, and alert the product team.

Here’s what our workflow looks like from trigger to output:

1. Trigger: Demo completion logged (e.g., HubSpot deal stage change).
2. Send feedback request: Email with a feedback form link sent via Gmail.
3. Feedback collection: Responses submitted via Google Forms linked to Google Sheets.
4. Detect new feedback: n8n polls Google Sheets or receives webhook notifications.
5. Process and store: Data normalized and logged in Google Sheets.
6. Notify team: Slack message sent highlighting new feedback.

Step 1: Setting the Trigger Node in n8n

We’ll use the HubSpot node’s “Watch Deal Stage” trigger to start the automation when a demo is marked as completed.

• Node: HubSpot Trigger
• Event: Deal Stage changed to “Demo Completed”
• Configuration Fields:
• Authentication: Connect your HubSpot API key or OAuth token.
• Watch Property: Deal Stage
• Property Value: “Demo Completed”
• Expression example:
  {{$json["properties.dealstage"] === 'demo_completed'}}

Step 2: Sending Feedback Request Email with Gmail

Once the demo completes, automatically send a personalized email asking for feedback.

• Node: Gmail
• Action: Send Email
• Fields:
• To: {{$json["properties.contact_email"]}}
• Subject: “We’d love your feedback on the demo!”
• Body:

Hi {{$json["properties.contact_name"]}},{br}{br}Thank you for attending the demo. Please share your feedback through this form: [Link to Google Form]{br}{br}Best regards,{br}The Product Team

• Dynamic placeholders use n8n expressions for contact details.

Step 3: Capturing Feedback in Google Sheets

The feedback form is keyed to a Google Sheet that collects all responses.

• Google Sheets is selected for real-time data access and n8n compatibility.
• Maintain columns for Timestamp, Contact Email, Rating, Comments.
• Ensure Google Sheets API credentials are securely stored in n8n.

Step 4: Watching for New Feedback Entries 🧐

To ingest new feedback, the workflow can use either:

• Polling the Google Sheet for new rows every 5 minutes.
• Webhook triggered by Google Forms add-on or Apps Script (more real-time).

Example Polling Node configuration:

• Node: Google Sheets Trigger
• Operation: Read Rows
• Filters: New entries based on latest timestamp
• Polling Interval: 300 seconds

Step 5: Processing Feedback Data

Normalize and enhance data to ensure consistency and enable action:

• Use Function Node in n8n to sanitize comments, parse ratings, add metadata like demo date.
• Example JavaScript snippet:
  return items.map(item => { item.json.cleanedComment = item.json.Comment.trim(); return item; });

Step 6: Logging Feedback in Centralized Google Sheets

Add or update a master Google Sheet with consolidated feedback to enable product analytics.

• Node: Google Sheets – Append Row
• Fields mapped exactly from processed data.

Step 7: Alerting the Product Team via Slack 🔔

Notify relevant Slack channel with key information to accelerate response.

• Node: Slack – Send Message
• Message content:

New demo feedback received from {{$json["Contact Email"]}}: Rating: {{$json["Rating"]}}, Comments: {{$json["cleanedComment"]}}

• Configure channel and authentication securely.

Executing Robustness and Error Handling Strategies

Reliable automation must handle failures gracefully and log issues:

• Error workflows: Use n8n error workflows to catch node failures, send error alerts via Slack.
• Retries/backoff: Enable retry options on API nodes with exponential backoff to manage transient faults.
• Idempotency: Deduplicate feedback based on unique IDs or timestamps to prevent double processing.
• Logging: Send runtime logs either to Google Sheets or external log management (e.g., Datadog) for audit trails.

Security and Compliance Considerations

When automating feedback collection, data protection is vital:

• API keys and tokens: Store using n8n credentials manager; never hard-code or expose publicly.
• Scopes: Minimize access scopes to only necessary resources (read/write sheets, send emails, post Slack messages).
• PII handling: Anonymize or encrypt sensitive customer data where possible to comply with GDPR and other regulations.
• Secure webhooks: Use secret tokens & HTTPS endpoints for webhook triggers to prevent unauthorized access.

Scaling and Adaptability of the Workflow

As your organization grows, your automation must scale effectively:

• Queues and concurrency: Use n8n’s built-in queuing system or external message brokers to handle high volume feedback submissions.
• Polling vs webhook: Prefer webhooks for real-time responsiveness; fallback to polling when webhooks are unavailable.
• Modular workflows: Split automation into smaller reusable sub-workflows for maintainability.
• Versioning: Use Git integration or export n8n workflows regularly to manage versions and rollback.

Testing and Monitoring Automation

Validate your automation to ensure reliability:

• Sandbox testing: Use test contacts and dummy data to verify each step without impacting real customers.
• Run history: Regularly inspect n8n execution logs to monitor performance and troubleshoot errors.
• Alerts: Configure automated alerts on failures using Slack or email to act quickly.

Comparing Workflow Automation Platforms for Post-Demo Feedback

Platform	Cost	Pros	Cons
n8n	Free self-host or from $20/mo cloud	Open-source, flexible, extensible, wide integrations	Self-host needs maintenance, learning curve higher
Make (Integromat)	From $9/mo	Easy UI, powerful scenarios, good support	Pricing increases with operations, less customization
Zapier	Free limited, $19.99+/mo paid plans	User-friendly, large app library, extensive templates	Limited free tier, expensive at scale

Polling vs Webhook for Feedback Collection

Method	Latency	Complexity	Resource Usage
Polling	5+ minutes delay	Simple to set up	Higher due to periodic checks
Webhook	Near real-time	Requires setup and security	Efficient event-driven

Google Sheets vs Database for Feedback Storage

Storage Option	Scalability	Integration Ease	Use Cases
Google Sheets	Limited to 10 million cells	Native n8n nodes, easy setup	Small to medium feedback logging
Relational DB (PostgreSQL, MySQL)	Highly scalable	Requires DB setup, connection node	Large datasets, complex queries

Conclusion: Accelerate Your Product Feedback Collection with n8n Automation

Automating the collection of post-demo feedback with n8n empowers product teams to gain actionable insights faster, reduce manual overhead, and improve customer satisfaction. We walked through designing an end-to-end system integrating HubSpot, Gmail, Google Sheets, and Slack, including vital considerations like error handling, security, and scalability.

As a next step, prototype this workflow on a sandbox account, tailor it to your tools, and gradually scale. Embrace automation to transform your feedback process from tedious to seamless and insight-driven.

Ready to revolutionize your post-demo feedback collection? Start building your n8n workflow today and watch your product’s success soar!