Automation library · Alerts and monitoring

Validate, deduplicate, and store customers with Supabase

Started by another system calling it, and works across Gmail, Slack, Supabase and Telegram. 12 steps, 2 branches: a working afternoon to understand properly.

Medium

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

The flow

Starts it 4Logic 3Service 5

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

  1. 1Customer API1WebhookStarts it
  2. 2Validate & Clean DataCodeLogic
  3. 3Is Validation Passed?IfLogic
  4. 4Check Existing UserSupabaseService
  5. 5API Validation ErrorRespond To WebhookStarts it
  6. 6User Already Exists?IfLogic
  7. 7Slack NotifySlackService
  8. 8API User ExistsRespond To WebhookStarts it
  9. 9Create UserSupabaseService
  10. 10Telegram NotifyTelegramService
  11. 11API Success ResponseRespond To WebhookStarts it
  12. 12Send Notifiaction to UserGmailService

How it's built

Starts on
Another system calling it
Steps
12, with 2 branches
Size
Medium: a working afternoon
Connects to
Gmail, Slack, Supabase, Telegram
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Gmail, Slack, Supabase and Telegram 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.