Automation library · Data collection

Generate and store Supabase images with Claude

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

Medium

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

The flow

Starts it 4Logic 6Service 5

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

  1. 1New Image Job (Insert)WebhookStarts it
  2. 2⚙️ ConfigSetLogic
  3. 3Parse JobCodeLogic
  4. 4Has a prompt?IfLogic
  5. 5🧠 Claude: Enhance PromptHttp RequestService
  6. 6Skip (no prompt)Respond To WebhookStarts it
  7. 7Extract PromptCodeLogic
  8. 8Update Job → errorSupabaseService
  9. 9🎨cloudflare ImageHttp RequestService
  10. 10500 ErrorRespond To WebhookStarts it
  11. 11Image → BinaryCodeLogic
  12. 12☁️ Upload to Supabase StorageHttp RequestService
  13. 13Build Public URLSetLogic
  14. 14Update Job → doneSupabaseService
  15. 15200 DoneRespond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
15, with 1 branch
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.