Automation library · Alerts and monitoring

Text back missed callers with Twilio SMS

Started by another system calling it, and works across Twilio. 5 steps, 1 branch: small enough to read in one sitting and change without fear.

Small

5 stepsSmall: readable in one sitting
1Branch: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Logic 3Service 1

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

  1. 1Missed call (webhook)WebhookStarts it
  2. 2Settings (edit me)SetLogic
  3. 3Read the callCodeLogic
  4. 4Actually missed?IfLogic
  5. 5Send the text backTwilioService

How it's built

Starts on
Another system calling it
Steps
5, with 1 branch
Size
Small: readable in one sitting
Connects to
Twilio
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Twilio 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?

Not long. At 5 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 5 steps before you point it at anything that matters.