Automation library · Integrations

SMS & WhatsApp queue processor: message delivery with Twilio

Started by a clock. It calls services over plain HTTP rather than through connectors. 8 steps, 1 branch, 1 loop or waits: small enough to read in one sitting and change without fear.

Small

8 stepsSmall: readable in one sitting
1Branch: places the flow splits
1Loop or waits
0Services by connector: it calls them over plain HTTP

The flow

Starts it 1Logic 3Service 4

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

  1. 1Check Every HourSchedule triggerStarts it
  2. 2Get SMS QueueHttp RequestService
  3. 3Split MessagesFunctionLogic
  4. 4Channel Type?SwitchLogic
  5. 5Send SMS via TwilioHttp RequestService
  6. 6Send WhatsApp via TwilioHttp RequestService
  7. 7Log Message SentHttp RequestService
  8. 8Rate Limit DelayWaitLogic

How it's built

Starts on
A clock
Steps
8, with 1 branch, 1 loop or waits
Size
Small: readable in one sitting
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?

Not long. At 8 steps it can be read in one sitting and changed without fear.

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