Automation library · Alerts and monitoring

Respond to missed calls with Twilio SMS

Started by another system calling it, and works across Email and Twilio. 12 steps, 3 branches: a working afternoon to understand properly.

Medium

12 stepsMedium: a working afternoon
3Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 1Logic 9Service 2

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

  1. 1Receive Call EventWebhookStarts it
  2. 2Normalize Call EventCodeLogic
  3. 3Is This a Valid Missed Call?IfLogic
  4. 4Deduplicate Call EventCodeLogic
  5. 5Stop, Not a Missed CallNo OpLogic
  6. 6Is This a New Call Event?IfLogic
  7. 7Check Business HoursCodeLogic
  8. 8Stop, Duplicate EventNo OpLogic
  9. 9Build Missed-Call TextCodeLogic
  10. 10Send SMS via TwilioTwilioService
  11. 11Did Twilio Accept the SMS?IfLogic
  12. 12Email Business AlertEmail SendService

How it's built

Starts on
Another system calling it
Steps
12, with 3 branches
Size
Medium: a working afternoon
Connects to
Email, Twilio
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

Plan an afternoon. 12 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 12 steps before you point it at anything that matters.