OTHER

Weekly voice-feedback theme clustering digest

On a weekly schedule, pulls all transcribed voice notes from the past week, clusters them into recurring themes with an LLM, and posts a ranked digest to Slack.

CategoryOther
Enginesim
Difficultyintermediate
Triggerschedule
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule (Monday morning)
  • ActionFetch last 7 days of transcripts from PostgresPostgreSQLPostgres
  • ActionCluster transcripts into named themes with OpenAIOpenAI
  • LogicSeparate single-mention themes into emerging bucket
  • OutputPost ranked theme digest to SlackSlack

What it does

Aggregates a week of customer voice feedback and finds the patterns. It collects every transcript stored in your database, clusters them into named themes (e.g. "onboarding friction," "export missing"), counts how many notes hit each theme, and delivers a ranked summary so the team sees what matters most this week.

When to use it

Run it when individual feature cards pile up faster than anyone can read them and you need the signal: which themes are surging, which are one-offs. Great for a Monday product standup input.

How it works

  1. 1A weekly schedule triggers the run every Monday morning.
  2. 2Postgres returns all voice-note transcripts captured in the last 7 days.
  3. 3OpenAI clusters the transcripts into themes, names each cluster, and tallies mention counts and representative quotes.
  4. 4A logic step drops themes with only a single mention into an "emerging" bucket so they don't crowd the headline list.
  5. 5A formatted digest ranked by mention volume is posted to a Slack channel.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect OpenAIModels, embeddings, files.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.