Skip to content
TidyKB

Help

How TidyKB works, written from the shipped product: connecting Freshdesk, what we read, the scan and score, bulk fixes and undo, translations, plans and limits.

Eight pages, written from the shipped product rather than from a plan. They are the reference for the parts that are easy to get wrong: what the connection test actually checks, which Freshdesk endpoints are called, how the health score is worked out, and what one-click undo can and cannot put back.

Start with connecting Freshdesk: creating a knowledge-base-only agent, pasting its API key, and reading each error the connection test can return. What TidyKB reads lists the exact endpoints, what is stored about your help center, what is sent to a translation model and how long any of it is kept. The scan and the health score explains the checks, and the cases where a scan refuses to claim that something is broken or fixed rather than guessing.

The rest is day-to-day work: ignoring an issue you will not fix, running a bulk find and replace with its read-only preview, its second Freshdesk key and its typed confirm, translation sync and your glossary, when scans and the weekly report run in your workspace time zone, and how articles and translation words are counted against your plan.

These pages are maintained with the product. Where one of them disagrees with what the app does, the app is right and the page is the bug.