All templates
For support content teams, knowledge base managers & customer support leads

Find the support questions your knowledge base can't answer

Every night, WebRun opens LiveAgent, reviews the day's ticket tags and topics, checks each one against your knowledge-base article list in Notion, and logs every topic with no matching article to a Google Sheet for the content team to write up.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every night at 11:00 PM WebRun
1 LiveAgent pull today's ticket topics
2 Notion check knowledge-base coverage
3 Google Sheets log the content gaps
Run a sample
In short

How do I find which support topics are missing from my knowledge base?

WebRun compares recurring LiveAgent ticket topics against your Notion knowledge base every night and logs any topic with no matching article to a Google Sheet, ranked by how often it came up. This gives content teams a data-backed list of exactly which articles to write next instead of guessing from memory.

  • Content teams get a ranked, data-backed list of articles to write next
  • Recurring questions with no article stop repeating unnoticed
  • Knowledge-base coverage is checked automatically every night

Built for support content teams · knowledge base managers · customer support leads · documentation teams

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens www.liveagent.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    LiveAgent - pull today's ticket topics
    liveagent.com
    WebRun in LiveAgent: pull today's ticket topics
    WebRun opens LiveAgent to pull today's ticket topics.
    • Open LiveAgent and pull today's closed tickets with their tags
    • Group tickets by topic and count how many times each came up
    • Keep only topics that appeared more than once today

    Done when Every recurring topic from today's tickets is listed with its count.

  3. 2
    Notion - check knowledge-base coverage
    notion.so How to Automate Notion
    WebRun in Notion: check knowledge-base coverage
    WebRun opens Notion to check knowledge-base coverage.
    • Open the knowledge-base article index in Notion
    • Check whether each recurring topic already has a matching article
    • Note the article link for topics that are already covered

    Done when Every recurring topic is marked covered or uncovered against Notion.

  4. 3
    Google Sheets - log the content gaps
    google.com How to Automate Google Sheets
    WebRun in Google Sheets: log the content gaps
    WebRun opens Google Sheets to log the content gaps.
    • Open the content gap tracker in Google Sheets
    • Add a row for each uncovered topic with its ticket count
    • Sort so the most frequent uncovered topics sit at the top

    Done when Every uncovered topic from today is logged and ranked by frequency.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.liveagent.com
ScheduleRuns automatically on this cadence
Every night at 11:00 PM
DeliveryHow each run's result reaches you
Content gap list · Google Sheets
OutputWhat each run produces - A ranked Google Sheet of support topics with no matching knowledge-base article, updated nightly.
Spreadsheet
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Does WebRun write the missing knowledge-base articles?

No. It only identifies which topics lack coverage and logs them to a sheet. Writing and publishing each article is still done by your content team.

How does it decide a topic needs an article?

It groups today's closed LiveAgent tickets by tag and topic, then checks each recurring one against your existing Notion article index for a match.

What if a topic is only asked about once?

It only logs topics that came up more than once in a single day, so one-off questions do not clutter the content team's gap list.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.