Build a source-linked video-trend briefing with n8n and Virlo

Define the collection before scheduling it

Luke’s January tutorial builds an n8n workflow pulling topics, hashtags and videos from YouTube and TikTok through Virlo. It aims to deliver a morning email and support questions through an AI agent. Trending data is research input; it does not establish that a new video on the same topic will become viral.

1. Open Virlo at https://dev.virlo.ai/ and the retained n8n route at https://n8n.partnerlinks.io/trxvmi48ria4. Follow API setup at 2:27 with a small collection whose records you can inspect.
2. Define the platforms, time window and fields needed for your briefing. Preserve the video URL, retrieval context and the measurements supplied by the source rather than reducing every result to a catchy idea.

Process the records and inspect the saved sheet

The sequence gets data at 4:46, processes and formats it at 8:04 and logs it to Google Sheets at 11:16. Keeping those stages distinct makes a missing item easier to locate: retrieval, transformation and storage can fail independently.

1. Inspect a sample API result before transforming it. Compare the formatted record with that source and check for missing values or duplicated videos before writing the collection to Sheets.
2. Open the saved sheet and verify its columns and representative rows. Keep enough source detail to distinguish a fresh finding from a record already collected in an earlier run.

Test the email and chat against the same evidence

The briefing is created at 13:54, the chat agent at 17:43 and public availability at 20:52. These are different delivery surfaces for the research. A readable email or fluent chat answer is useful only if its claims remain tied to the collected records.

1. Run one briefing and inspect its actual destination, links and content. Check that the proposed ideas accurately reflect the collected videos and keep your editorial interpretation separate from measured trends.
2. Ask the chat agent a question with a known answer in the sheet and another the data cannot answer. Review access and the resulting answers before exposing it publicly or enabling the intended daily schedule.

The takeaway

Maintain one traceable research collection behind both outputs. Verify collection, storage, email delivery and chat answers separately before relying on a recurring routine.