Automation library · Scheduling

Scheduled auto-replies to targeted tweets

Started by a clock. It calls services over plain HTTP rather than through connectors. 15 steps, 4 branches: a working afternoon to understand properly.

Medium

Download free
15 stepsMedium: a working afternoon
4Branches: places the flow splits
0Loops or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Logic 12Service 2

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

  1. 1Reply ErrorSetLogic
  2. 2Schedule Trigger (15分ごと)Schedule triggerStarts it
  3. 3Search Tweets (HTTP)Http RequestService
  4. 4Get Latest Tweet Per AccountCodeLogic
  5. 5Is Success?IfLogic
  6. 6Prepare ReplyCodeLogic
  7. 7Is Rate Limit?IfLogic
  8. 8Send Reply (HTTP)Http RequestService
  9. 9Rate Limit ErrorSetLogic
  10. 10Is No Tweets?IfLogic
  11. 11Is Duplicate?IfLogic
  12. 12No Tweet FoundSetLogic
  13. 13Other ErrorSetLogic
  14. 14Already Replied (Skip)SetLogic
  15. 15Reply SuccessSetLogic

How it's built

Starts on
A clock
Steps
15, with 4 branches
Size
Medium: a working afternoon
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 a clock.

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?

Plan an afternoon. 15 steps is enough that you should read each one before running it.

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