The best content brief is a question someone actually asked
Each community produces hundreds of questions every month. Most are individual cases that need a solution rather than an article. A small number are phrased entirely differently and show a real gap in the content you have published.
The difficulty is spotting recurrence, because the same fundamental confusion appears across five questions that share no keywords. If you group them by meaning rather than by exact phrases, the support backlog becomes a content plan.
Distinguish the two in both directions. If a genuine support issue is sent to the content queue, the remedy is delayed. If a recurring gap is sent to support, it has to be addressed one instance at a time, forever.
Quotes are more valuable than topics. A page built from the exact words people used sounds as if someone who was actually there wrote it.
How the agent is built in Agent Studio
You have to set the recurrence threshold explicitly. The system prompt specifies how many distinct askers are required for something to be considered a pattern, and it instructs the agent to group queries by underlying confusion rather than by similar wording.
Prompt skills carry the distinction between a content gap and a product problem in your specific case, which is a line only your team can draw.
A Start Scheduled flow gathers the material. A Discord node and a Slack node read your community channels, an HTTP Request node covers anything else, and the Agent Chat node hands the collected questions over.
Notion receives a ranked list of opportunities. Each item contains the actual quotes. Those quotes count as the deliverable as much as the ranking does.
Another output sends genuine support issues to Linear or Jira, because in some cases the right response is a fix rather than a page.
You should not publicly quote any members of a community without first obtaining their permission. Put this rule in the system prompt so the output is flagged at once to show who needs to be asked.
What this agent is built from
- System prompt: states the recurrence threshold and the instruction to cluster by meaning, not wording.
- Prompt skills: state where the line falls between a content gap and a product problem for you.
- Discord (Integration): reads community channels. Slack fits the same slot.
- Agent Chat (Util): a scheduled flow hands the collected questions over for clustering.
- Notion (Integration): receives the ranked opportunities with the real quotes attached.
- Linear (Integration): receives genuine support issues, which need a fix rather than a page.
- When an ActionFlow is enough: Exporting questions into a spreadsheet is a workflow. The clustering judgment is the agent.
Frequently asked questions
Start building AI workflows
Create a free account, open a template or a blank canvas, and run your first ActionFlow.
Newsletter
Get product updates
New nodes, agents, and product notes. We send mail only when we have something worth opening.