Monitor TikTok keywords with a bounded API workflow
Run a repeatable keyword search, store the results, and identify newly observed videos. FetchFox provides the search operation; your scheduler, storage, and alert rules complete the workflow.
Start with a manual search
Choose a narrow query that represents the topic you actually want to follow. Request 20 results and inspect them before scheduling anything. The endpoint accepts query and limit; it does not offer a time filter or complete historical coverage.
Store observations separately from videos
Use one record for each source video and another for each search observation. The observation should contain your query, retrieval time, run identifier, and the returned metric snapshot. Deduplicate by returned video identifier or canonical URL before deciding what is new.
Choose a schedule your plan can support
One successful one-credit search per day would use about 30 credits per month, more than the 20 free monthly credits. A weekly pilot is a better way to evaluate relevance on the free allowance.
TikTok search reserves one credit per 20 requested results and charges at least one credit, then one per 50 returned results. Multiple queries and retries need their own budgets. Stop on exhausted capacity and respect Retry-After for HTTP 429.
Define an alert that means something
Alert only on previously unseen videos or a documented change in a stored metric. Search ranking can reorder results without any underlying content change. For ongoing metrics on one known video, call /tiktok/stats instead of assuming search will keep returning it.
The n8n guide shows the HTTP Request setup. Add persistence and notification nodes in your own workflow after validating the response. FetchFox does not send monitoring alerts on your behalf.