Automation library · Alerts and monitoring

Recover missed calls with Twilio and Slack

Started by another system calling it, and works across Google Sheets, Slack and Twilio. 9 steps, 2 branches: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 4Service 4

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

  1. 1Receive Missed Call WebhookWebhookStarts it
  2. 2Check Call Failed/Busy/No-AnswerIfLogic
  3. 3Check Business HoursCodeLogic
  4. 4Skip - Call Was AnsweredNo OpLogic
  5. 5Log Missed Call to Google SheetsGoogle SheetsService
  6. 6Is It Business Hours?IfLogic
  7. 7SMS - Call Back in 5 MinutesTwilioService
  8. 8SMS - Will Contact in Business HoursTwilioService
  9. 9Notify Team on SlackSlackService

How it's built

Starts on
Another system calling it
Steps
9, with 2 branches
Size
Medium: a working afternoon
Connects to
Google Sheets, Slack, Twilio
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Google Sheets, Slack 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. 9 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 9 steps before you point it at anything that matters.