Automation library · Scheduling

Schedule X posts, threads, images and polls

Started by another system calling it. It calls services over plain HTTP rather than through connectors. 54 steps, 15 branches, 3 loops or waits: large, and worth reading before you trust it with anything live.

Large

Download free
54 stepsLarge: read it before trusting it with anything live
15Branches: places the flow splits
3Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 2Logic 41Service 11

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

  1. 1When Webhook ReceivedWebhookStarts it
  2. 2Route by Content TypeSwitchLogic
  3. 3Prepare Post ContentCodeLogic
  4. 4Prepare Thread ContentCodeLogic
  5. 5Delete Tweet from XHttp RequestService
  6. 6Fetch User Info from XHttp RequestService
  7. 7Handle Unknown Content TypeSetLogic
  8. 8If Post Is SimpleIfLogic
  9. 9Loop Over Thread ItemsSplit In BatchesLogic
  10. 10If Tweet Deleted SuccessfullyIfLogic
  11. 11If User Info ValidIfLogic
  12. 12Send Response to WebhookRespond To WebhookStarts it
  13. 13Post Simple TweetHttp RequestService
  14. 14If Invalid Post PayloadIfLogic
  15. 15Compile Thread Response DataCodeLogic
  16. 16If First Tweet in ThreadIfLogic
  17. 17Set Delete Error DetailsSetLogic
  18. 18Set Delete Success DetailsSetLogic
  19. 19Set User Info Error DetailsSetLogic
  20. 20Set User Info Success DetailsSetLogic
  21. 21Set Simple Post Success DetailsSetLogic
  22. 22Set Invalid Payload Error DetailsSetLogic
  23. 23If Post Contains PollIfLogic
  24. 24Set Final Thread ResponseSetLogic
  25. 25Post Root Tweet in ThreadHttp RequestService
  26. 26If Previous Tweet ExistsIfLogic
  27. 27Post Tweet with PollHttp RequestService
  28. 28Prepare Media for PostCodeLogic
  29. 29Wait 1 Second Before ReplyWaitLogic
  30. 30Reply to Previous Thread TweetHttp RequestService
  31. 31Set Thread Chain Error DetailsSetLogic
  32. 32If Poll Post SuccessfulIfLogic
  33. 33Init Media UploadHttp RequestService
  34. 34Capture Thread Reply DetailsCodeLogic
  35. 35Set Poll Post Error DetailsSetLogic
  36. 36Set Poll Post Success DetailsSetLogic
  37. 37If Media Upload SuccessIfLogic
  38. 38Track Previous Tweet IDSetLogic
  39. 39Set Media Upload Error DetailsSetLogic
  40. 40Chunk Media for UploadCodeLogic
  41. 41Append to Media UploadHttp RequestService
  42. 42If Media Appended SuccessfullyIfLogic
  43. 43Prepare Media FinalizationCodeLogic
  44. 44Finalize Media UploadHttp RequestService
  45. 45Process Media StatusCodeLogic
  46. 46If Media Processing ErrorIfLogic
  47. 47If Media Processing CompleteIfLogic
  48. 48Generate Media IDsCodeLogic
  49. 49Wait for Media ProcessingWaitLogic
  50. 50If Media IDs ValidIfLogic
  51. 51Check Media StatusHttp RequestService
  52. 52Post Tweet with MediaHttp RequestService
  53. 53If Media Post SuccessfulIfLogic
  54. 54Set Media Post Success DetailsSetLogic

How it's built

Starts on
Another system calling it
Steps
54, with 15 branches, 3 loops or waits
Size
Large: read it before trusting it with anything live
Connects to
Nothing by connector; it calls services over plain HTTP
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

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 54 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 54 steps before you point it at anything that matters.