Automation library · Alerts and monitoring

Text back missed callers with Twilio and CallRail

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. 1When Call Missed WebhookWebhookStarts it
  2. 2Normalize Call DetailsCodeLogic
  3. 3Check If Call MissedIfLogic
  4. 4Check After Hours StatusCodeLogic
  5. 5No Action - Not Missed CallNo OpLogic
  6. 6Build Text-Back MessageCodeLogic
  7. 7Run Compliance WorkflowExecute WorkflowLogic
  8. 8Check Approval to Send SMSIfLogic
  9. 9Send SMS via TwilioTwilioService
  10. 10No Action - Contact Opted OutNo OpLogic
  11. 11Verify Text DeliveryIfLogic
  12. 12Email Firm NotificationEmail 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.