Installs in ~2 min· 2 assets · 4 steps

Collect course feedback that is genuinely anonymous

Anonymous means anonymous. No name, no email, no student ID, anywhere in the chain.

Students tell you the truth about a course only when they're certain it can't be traced back to them. This recipe collects no identifying field at any point, so there's nothing to trace. AI reads each submission, flags anything abusive or off-topic before staff ever see it, and tags sentiment and themes onto the row. When a rating is low or the sentiment turns negative, the department head is alerted in seconds: with the course, the instructor, and the comments, and nothing about who wrote them.

Free · no credit card · you connect your own apps

The blueprint
Trigger
Anonymous Course Feedback is submitted
Every run starts from one submission.
Transform
Analyze & Moderate Feedback
AI reads the input and returns a structured result.
Transform
Save AI Analysis
Logic
Low Rating, Negative, or Flagged?
Branches on the outcome, so each path is handled.
Action
Alert Department Head
What gets built

2 things appear in your workspace.

Installing provisions each one, wired together and ready to run.

FormAnonymous Course Feedback

A fully anonymous course and teaching-quality survey. Publishing it auto-creates the response sheet (the single system of record) which the workflow extends with moderation_flag, sentiment, and themes.

WorkflowProcess Course Feedback

Fires on each new anonymous row. Moderates the free text, classifies sentiment and themes, saves the analysis back to the row, and alerts the department head when a rating is low, sentiment is negative, or the text is flagged.

What you connect

The apps this recipe needs.

You connect your own accounts. Swap any app that offers an alternative at install.

Department Alert
Slack *

Alerts the department head when a rating is low, sentiment is negative, or the text is flagged, so teaching-quality issues get attention. Swap for Telegram, Discord, or Google Chat.

How it works

Step by step, once it is running.

  1. 01
    A Student Shares Feedback

    The student opens the Anonymous Course Feedback survey and rates the course, the teaching quality, and the workload, then adds free-text comments. No name, no email, no student ID is ever asked for, which is the entire point, and the reason the answers are worth reading. Publishing the form auto-creates its response sheet, so every submission is captured with no extra setup.

  2. 02
    AI Moderates and Classifies It

    One TinyGPT step reads each submission and returns structured JSON: a moderation_flag of clean or flagged (abusive, harassing, or off-topic text gets caught here), a sentiment of positive, neutral, or negative, and themes: comma-separated tags naming what the comments are actually about, from teaching-clarity, workload, pacing, materials, assessment, engagement, support, and facilities.

  3. 03
    The Analysis Is Saved to the Row

    The moderation flag, sentiment, and themes are written straight back onto the same anonymous row. No second sheet, no join key, and nothing added that could identify the student. What you end up with is a clean aggregate dataset you can actually use in a teaching-quality review.

  4. 04
    The Department Head Is Alerted

    When a rating falls at or below the threshold you set, when sentiment is negative, or when the text is flagged, the course, instructor, ratings, sentiment, themes, and improvement text are posted to the department head's Slack channel, with no student identity attached. Swap Slack for Telegram, Discord, or Google Chat at install.

What you walk away with
FAQ

Questions about Student Feedback Collection.

How anonymous is it really?
No name, email or student ID is collected anywhere in the chain. There is no identity attached to a response, which is what makes students willing to say something useful about a course.
What does AI do with the feedback?
It moderates and classifies each submission, then saves the analysis to the same row. Moderation matters here because anonymous channels attract abuse, and a department head should see substance rather than sift it.
When is the department head alerted?
When a response crosses your alert_threshold. Routine feedback accumulates on the sheet for review, and serious issues generate an alert to your department channel rather than waiting for end of term.
What do I need to connect?
Slack, and that is the only integration. Alerts go to the department channel you nominate, and Telegram, Discord and Google Chat are supported swaps at install.
Can we run it for multiple courses?
Yes. The form and workflow are permanent workspace objects, so the same anonymous feedback channel serves every course and term, with the institution name held as configuration.
More recipes

Install it, then make it yours.

Everything it creates is an ordinary form, table and workflow in your workspace. Edit any of it after install. Nothing is locked.