MARKET RESEARCH

Emerging JTBD theme alert on threshold crossing

When a new interview theme is logged, this checks how often that job has now appeared across the corpus and fires a Linear issue plus Slack alert the moment a job crosses…

CategoryMarket Research
Enginesim
Difficultyintermediate
Triggerevent
Steps5
Setup~15 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew theme logged in AirtableAirtableAirtable
  • ActionCount interviews for this jobAirtableAirtable
  • LogicOnly on threshold crossing
  • ActionCreate Linear roadmap issueLinearLinear
  • OutputPost alert to SlackSlack

What it does

Watches the research corpus for jobs-to-be-done that are gaining momentum. Each time a new theme is logged, it counts how many distinct interviews have now raised that same job, and the first time a job crosses your recurrence threshold it creates a Linear issue for the product team and posts a Slack alert, so a repeating pain point becomes an action item instead of a footnote.

When to use it

Use it when you want discovery to feed the roadmap directly: the moment enough customers independently describe the same job, the team should hear about it without waiting for a quarterly synthesis.

How it works

  1. 1A new theme record created in Airtable triggers the flow.
  2. 2The flow queries Airtable for the total distinct-interview count of that same job.
  3. 3A logic step proceeds only when the count first crosses the configured threshold.
  4. 4A Linear issue is created summarizing the job, its frequency, and representative quotes.
  5. 5A Slack alert is posted linking the new issue so the team can triage.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect LinearIssues, projects, cycles, triage.
  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.