Hello, i am new here, and I am trying to make a workflow documentation report wherein moderators can submit their reports, gather data, and analyze the data in a daily, weekly, or monthly basis. Where can I find something similar to this?
Grealty appreciate who will answer!
Goodmorning,
Modified it to be in the correct category.
Can you give us a bit more information on what you are trying to build?
Also have you done the courses? learn.n8n.io
try the courses first.
You can use the form nodes for this probably. But making it fancy you will need external tooling and possibly use n8n as a backend.
Thank you for this, i am looking for a template that i can compare with when i create a workflow
Your diagram makes this easier to answer, because it shows two different things that people usually try to squeeze into one workflow.
The incident reports are event driven. A moderator sees botting in Bloody Ice, fills the form, one row gets created.
The Alz and FG rates are a daily time series. They exist whether or not anyone reports an issue. If those fields live in the same form, five reports on Tuesday give you five copies of Tuesday’s economy numbers and your monthly analysis starts double counting. Capture them separately into two tables, then join on date when you build the report.
The pieces themselves:
Capture. The Form Trigger node covers everything in your mockup natively, no external tooling needed. Date, issue category as a dropdown, details, resolution taken. Give every report an ID the moment it is created.
Storage. Sheets works to start, but look at your own step 5. Resolved On and Resolved By mean a report gets updated after it exists, not just appended. Updating a specific row in Sheets means searching for it first and hoping two moderators are not editing at the same second. Postgres or Supabase removes that problem and costs nothing at this size.
Reporting. A second workflow on a Schedule Trigger. Daily, weekly and monthly can be three schedules calling the same sub workflow with a different date range. Pull the period’s rows, group by category, count, join the economy rows by date, and you have the trends panel from your step 4.
One thing about the AI box in the middle. Do the counting in code or SQL first, then give the model the summary numbers and let it write the narrative. If you hand it raw rows it will invent patterns, and in an economy report a made up trend is worse than no report.
Bloody Ice and Alz suggest Cabal. Is that right, and roughly how many reports a day are you expecting? Volume decides whether Sheets is fine or you should start on a database.
i am expecting daily reports from my moderator. trying to figure it out since i do not have any background on this. Reading the tutorial but cannot seem to understand on some parts.
Daily reports from a handful of moderators changes my earlier answer, so ignore the database part. At that size Google Sheets is completely fine and you should not add Postgres to a first version.
Here is the smallest thing that actually works. Two nodes.
Form Trigger. Add your fields: date, issue category as a dropdown, details, resolution taken. n8n gives you a URL you send to your moderators, and they just fill it in.
Google Sheets, Append Row. Map each form field to a column.
That is a working submission system. Activate it, submit a test report yourself, and check the row lands in the sheet. Do not build anything else until that part works, because everything later depends on rows arriving correctly.
Once that runs, the daily summary is a second workflow, also small to start. A Schedule Trigger at whatever time you want it, then Google Sheets Get Rows filtered to yesterday, then send it wherever you actually read things. Counting by category can wait until reports are landing reliably.
The economy numbers still want their own separate form, submitted once a day rather than attached to every report. That part of what I said before still holds.
Which part of the tutorial stopped making sense? If you name the node or the step, I can explain that one piece instead of the whole thing.
