Automation library · Data collection

Learn secure webhook APIs with Supabase

Started by another system calling it, and works across Supabase. 15 steps: a working afternoon to understand properly.

Medium

15 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 9Logic 2Service 4

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

  1. 1WebhookWebhookStarts it
  2. 2Webhook1WebhookStarts it
  3. 3Webhook2WebhookStarts it
  4. 4Webhook3WebhookStarts it
  5. 5Webhook4WebhookStarts it
  6. 6Webhook5WebhookStarts it
  7. 7Get a rowSupabaseService
  8. 8Edit FieldsSetLogic
  9. 9Edit Fields1SetLogic
  10. 10Delete a rowSupabaseService
  11. 11Respond to WebhookRespond To WebhookStarts it
  12. 12Create a rowSupabaseService
  13. 13Update a rowSupabaseService
  14. 14Respond to Webhook1Respond To WebhookStarts it
  15. 15Respond to Webhook2Respond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
15
Size
Medium: a working afternoon
Connects to
Supabase
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

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