Automation library · Content

Dynamic Sitemap Generator with GitHub and Supabase

Started by another system calling it, and works across GitHub, Supabase and n8n data table. 14 steps: a working afternoon to understand properly.

Medium

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

The flow

Starts it 3Logic 7Service 4

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

  1. 1d2group.co_sitemap_generatorWebhookStarts it
  2. 2When clicking ‘Execute workflow’Manual triggerStarts it
  3. 3get_app.tsxGithubService
  4. 4get_blogSupabaseService
  5. 5extract_fileExtract From FileService
  6. 6set_dynamicUrlsSetLogic
  7. 7statics_urlCodeLogic
  8. 8AggregateAggregateLogic
  9. 9MergeMergeLogic
  10. 10Create_SitemapCodeLogic
  11. 11Respond to WebhookRespond To WebhookStarts it
  12. 12convert_sitemap_to_urlXmlLogic
  13. 13split_urlSplit OutLogic
  14. 14Upsert_sitemap_tableData TableService

How it's built

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

Questions

What does it need to run?

An n8n account, plus your own GitHub and Supabase 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. 14 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 14 steps before you point it at anything that matters.