Workflows
The workflow catalogue and the state of each last run. Each workflow writes to ingest_log when it finishes — whether it was fired from here, run by hand in n8n, or started by its own schedule — so “Last run” is the truth for all three. Running a job here POSTs to its n8n production webhook; the URLs are stored in settings.n8n_webhooks and are editable below.
sql/ad4_20_schedules.sql to set each workflow's cadence from here instead of editing nine Schedule Triggers by hand.Which cities each job covers
Default is every active city. Narrowing it does not reduce your n8n execution count — n8n bills per execution — it reduces how long a run takes and how hard it leans on the upstream API. That matters where a job makes one request per item, and not at all where it batches; each row says which it is.
City readiness
Current evidence needed to evaluate each city-day. A fresh evaluation with no tradeable edge is valid; missing or stale inputs are shown as blockers.
Why a Run button can fail even when the workflow is fine: an inactive n8n workflow only answers its /webhook-test/ URL, and only for one call after you press “Listen for test event”. The /webhook/ URL used here needs the workflow Active. The browser also needs the Webhook Trigger’s allowedOrigins to include this site — the shipped workflows set it to *, which you can narrow to your own domain once it is settled.