Automation library · Content

Convert YouTube videos to shorts with Klap

Started by an incoming Telegram message, and works across Google Sheets and Telegram. 32 steps, 2 branches, 2 loops or waits: large, and worth reading before you trust it with anything live.

Large

32 stepsLarge: read it before trusting it with anything live
2Branches: places the flow splits
2Loops or waits
2Services it connects to

The flow

Starts it 1Logic 11Service 20

The steps in the order they run, from what starts it.

  1. 1Trigger: Receive YouTube URL via TelegramTelegram triggerStarts it
  2. 2Extract YouTube URL & Number of ShortsCodeLogic
  3. 3Send Video to Klap for Shorts GenerationHttp RequestService
  4. 4Check Shorts Generation StatusHttp RequestService
  5. 5Is Video Processing Complete?IfLogic
  6. 6List Generated Clip IdeasHttp RequestService
  7. 7Wait Before Checking Status AgainWaitLogic
  8. 8Export HD Short from KlapHttp RequestService
  9. 9Fetch Final Shorts URLsHttp RequestService
  10. 10Are All Shorts Ready?CodeLogic
  11. 11Ready to Schedule Shorts?IfLogic
  12. 12Fetch YouTube Video TitleHttp RequestService
  13. 13Wait Before Rechecking Final ShortsWaitLogic
  14. 14Load Publishing Schedule from Google SheetsGoogle SheetsService
  15. 15Extract Scheduling Parameters (Posts/Day, Hours)CodeLogic
  16. 16Fetch Already Scheduled ShortsGoogle SheetsService
  17. 17Determine Last Scheduled TimeCodeLogic
  18. 18Calculate Publication Times for New ShortsCodeLogic
  19. 19Convert Times to Local Timezone (Paris)CodeLogic
  20. 20Log Shorts & Schedule Info to Google SheetsGoogle SheetsService
  21. 21Assign Social Media IDsSetLogic
  22. 22Upload Video to BlotatoHttp RequestService
  23. 23INSTAGRAMHttp RequestService
  24. 24YOUTUBEHttp RequestService
  25. 25TIKTOKHttp RequestService
  26. 26FACEBOOKHttp RequestService
  27. 27THREADSHttp RequestService
  28. 28TWITTERHttp RequestService
  29. 29LINKEDINHttp RequestService
  30. 30BLUESKYHttp RequestService
  31. 31PINTERESTHttp RequestService
  32. 32Send Publication Summary to TelegramTelegramService

How it's built

Starts on
An incoming Telegram message
Steps
32, with 2 branches, 2 loops or waits
Size
Large: read it before trusting it with anything live
Connects to
Google Sheets, Telegram
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Google Sheets and Telegram accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on an incoming Telegram message.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Take your time. At 32 steps it is large: read it before trusting it with anything live.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 32 steps before you point it at anything that matters.