Skip to content

A weekly AI summary of customer feedback, set up from your assistant

Your assistant builds an automation that gathers the week's new feedback from your sheet, survey tool or help desk, groups it into themes with the built-in AI, and posts the summary with real quotes.

Your assistantClickRuntime connected
Create a ClickRuntime automation: every Monday at 9, summarise last week's rows in my Feedback sheet into themes and post it to #product.
I'll read the new rows since last Monday, group them into themes with counts and one quote each, and post to #product.
Weekly feedback themesLive
When
Mondays 9:00
Uses
Google Sheets, Slack
RunsClickRuntime dashboard
  • Mon 9:00✓ Weekly feedback themes · SucceededLast runMon 9:00 · 5 themes

Can ChatGPT or Claude summarise customer feedback every week?

If you paste feedback into a chat, an assistant will summarise it. Doing that every week without pasting means something has to collect the new feedback and run the summary on a schedule. With ClickRuntime, the assistant sets up an automation that reads only the feedback added since the last summary, uses the built-in AI to group it into themes, and posts the result to Slack or email.

Why the assistant can’t do this on its own

  • No schedule and no collection: a chat can't fetch last week's survey answers on Monday morning by itself.
  • Only new feedback should be summarised. The automation remembers the last row it read.
  • The built-in AI needs no API key, so the summary works including on the free plan.

Set it up from your AI assistant

The same steps work in ChatGPT, Claude, Cursor and any assistant that supports MCP connectors.

  1. Step 1Connect ClickRuntime to your assistantAdd ClickRuntime as a connector (MCP server) in ChatGPT, Claude, Cursor or another MCP client, using https://clickruntime.com/api/mcp. You sign in with Google or email; there is no API key to copy. This is done once per assistant.
  2. Step 2Paste the promptStart a new chat and paste: “Create a ClickRuntime automation: every Monday at 9:00, read the rows added to my Feedback sheet since last time (columns: Date, Source, Text), group them into up to 6 themes with a count and one short quote each, and post it to #product in Slack.” Change the details (times, channels, addresses) to yours.
  3. Step 3Read the draftThe assistant restates what will happen, asks for anything missing, such as your timezone or which channel to post to, and saves a draft automation. A draft never runs on its own, so nothing happens until you agree.
  4. Step 4Connect accounts and save keysThe assistant asks you to connect Google and pick the Feedback sheet, and to connect Slack for notifications. For Typeform, Zendesk, Intercom or app-store reviews it asks for that service's API key, saved in the ClickRuntime dashboard.
  5. Step 5Test itThe assistant runs it now on the existing rows and shows you the summary before turning on the schedule.
  6. Step 6Turn it onThe assistant tells you what will run, when, and which services it will contact, then asks your permission to turn it on. From then on it runs on ClickRuntime's servers, and you can close the chat.
  7. Step 7Check it in the ClickRuntime dashboardEach Monday's run shows how many new items it read and the summary it posted. State keeps the last row read, and the run result keeps the themes so you can compare weeks.
Prompt to copy.txt

“Create a ClickRuntime automation: every Monday at 9:00, read the rows added to my Feedback sheet since last time (columns: Date, Source, Text), group them into up to 6 themes with a count and one short quote each, and post it to #product in Slack.”

Connector setup for each assistant: ChatGPT, Claude, Claude Code, Cursor, and other assistants.

What the assistant writes

A typical script for this job. Yours matches your pages, accounts and wording, and you can read every version in the ClickRuntime dashboard.

weekly_feedback_themes.pyexample
1from google.oauth2.credentials import Credentials
2from googleapiclient.discovery import build
3from clickruntime import on_trigger, credentials, state, ai, notify
4 
5SHEET_ID = "your-spreadsheet-id"
6SCHEMA = {"type": "object", "properties": {"themes": {"type": "array", "items": {"type": "object", "properties": {
7"theme": {"type": "string"}, "count": {"type": "integer"}, "quote": {"type": "string"}},
8"required": ["theme", "count", "quote"]}}}, "required": ["themes"]}
9 
10@on_trigger
11def run(event):
12sheets = build("sheets", "v4", credentials=Credentials(credentials.connection("cr_google_sheets_picked", "work")),
13cache_discovery=False).spreadsheets()
14rows = sheets.values().get(spreadsheetId=SHEET_ID, range="Feedback!A2:C").execute().get("values", [])
15start = state.get("next_row") or 0
16new = [r for r in rows[start:] if len(r) >= 3 and r[2].strip()]
17if not new:
18notify.slack("No new customer feedback this week.", channel="#product")
19return {"summary": "No new feedback"}
20 
21lines = "\n".join(f"{i + 1}. [{r[1]}] {r[2][:400]}" for i, r in enumerate(new[:300]))
22try:
23themes = ai.generate(lines, system="Group this customer feedback into at most 6 themes. "
24"Quote one short, real sentence from the input per theme.",
25json_schema=SCHEMA, max_output_tokens=800).json["themes"]
26body = "\n".join(f"• *{t['theme']}* ({t['count']}): “{t['quote']}”" for t in themes)
27except ai.AIError:
28body = f"{len(new)} new items. AI summary unavailable this week; see the Feedback sheet."
29 
30notify.slack(f"Customer feedback, last week ({len(new)} items)\n{body}", channel="#product")
31state.set("next_row", len(rows))
32return {"items": len(new), "summary": body[:2000]}
  • Items are numbered and trimmed to 400 characters each, then sent in one AI call, which keeps token use low.
  • The JSON schema makes the AI return themes, counts and quotes in a fixed shape the script can format.
  • The row position is saved only after posting, so a failed run doesn't skip feedback.

A schedule, not a trigger link

Use a schedule for the summary: weekly or daily.

If feedback arrives by webhook (a survey tool), add a trigger link that stores each answer as it comes in, and keep the weekly schedule for the summary.

Limits

  • One AI call takes about 32,000 input tokens. Larger weeks are split into batches, or summarised per source first.
  • AI tokens count toward the workspace's monthly allowance, including on the free plan.
  • The AI reads text only. Screenshots and attachments are not sent.

Troubleshooting

The summary is too generic.

Ask your assistant to name your product areas so the AI groups by those, or to include two quotes per theme.

It summarised old rows again.

State was cleared or rows were deleted above the saved position. Ask the assistant to track a Date column instead of the row number.

What you can add next

The first version is rarely the last. Because the automation is a Python script with memory, AI and any API available, you grow it by asking your assistant for the change. Each change is a new version, and a failed deploy never replaces the working one.

  • Any app or API

    Pull feedback straight from Typeform and Zendesk instead of a sheet

    “Change my weekly feedback themes automation so it also reads last week's Typeform survey answers and Zendesk satisfaction comments.”
  • Built-in AI

    Tag each item with sentiment and theme as it arrives

    “Add to my weekly feedback themes automation: every hour, add sentiment and a theme label to new rows in the Feedback sheet.”
  • Trigger links

    Alert #support right away when very negative feedback comes in

    “Add a trigger link to my weekly feedback themes automation for new survey answers, and post answers scoring 1 or 2 to #support straight away.”
  • Memory between runs

    Compare themes with last week and flag what's rising

    “Change my weekly feedback themes automation so it remembers last week's themes and marks themes that grew or are new.”
  • Any app or API

    Create a Linear issue for any theme mentioned five or more times

    “Add to my weekly feedback themes automation: for each theme with 5 or more mentions, create a Linear issue in the Product team with the quotes.”
  • Multi-step logic

    Separate summaries for free and paying customers

    “Change my weekly feedback themes automation so it posts two summaries, one for paying customers and one for free users, using the Plan column.”

Which feedback sources can it read?

Any source with an API or export: a support tool such as Intercom or Zendesk, a survey tool, app store reviews, or a Google Sheet where feedback is collected. Save each key as a secret in the ClickRuntime dashboard.

Can ChatGPT summarise survey responses automatically?

With ClickRuntime connected, ChatGPT can set up an automation that collects new responses and posts an AI summary on a schedule, without you pasting anything.

Do I need an OpenAI or Anthropic key?

No. ClickRuntime's built-in AI needs no key and is included, including on the free plan.

Will it make up quotes?

It's told to quote sentences from the input, and you can ask the assistant to check each quote appears in the source before posting.

Where can the feedback come from?

A sheet, a form or survey tool, a help desk such as Zendesk or Intercom, app-store reviews, or any API.

Other use cases

Set up your first automation in ChatGPT or Claude

Free plan. No credit card.

Server URLhttps://clickruntime.com/api/mcp