Keep your internal knowledge base fresh and reliable with this automated FAQ freshness monitoring system. π§ π
This workflow tracks FAQ update dates in Notion, calculates SLA compliance, logs results in Google Sheets, and sends Slack alerts for outdated items. Perfect for documentation teams ensuring content accuracy and operational visibility across platforms. ππ¬
1οΈβ£ Triggers every Monday at 10:00 AM to start freshness checks. β°
2οΈβ£ Fetches FAQ entries from your Notion database. π
3οΈβ£ Computes SLA status based on the last edited date (30-day threshold). π
4οΈβ£ Updates a Google Sheet with current FAQ details and freshness status. π
5οΈβ£ Filters out overdue FAQs that need review. π
6οΈβ£ Aggregates all overdue items into one report. π§Ύ
7οΈβ£ Sends a consolidated Slack alert with direct Notion links and priority tags. π¬
β
Maintains documentation freshness across systems.
β
Reduces support friction from outdated FAQs.
β
Centralizes visibility with Google Sheets reporting.
β
Notifies your team in real time via Slack.
β
Enables SLA-based documentation governance.
Knowledge management and documentation teams π§Ύ
SaaS product teams maintaining FAQ accuracy π‘
Support operations and customer success teams π¬
QA and compliance teams monitoring SLA adherence π
1οΈβ£ Connect Notion credentials and set your FAQ database ID.
2οΈβ£ Create a Google Sheet with required headers (Title, lastEdited, slaStatus, etc.).
3οΈβ£ Add your Slack credentials and specify the alert channel ID.
4οΈβ£ Configure the cron schedule (0 10 * * 1) for Monday 10:00 AM checks.
5οΈβ£ Run once manually to verify credentials and mappings.
6οΈβ£ Activate for ongoing weekly freshness monitoring. β


