[DOCS-REQUEST] - Workload.json file examples

[velociwabbit]

A decent explanation of how to do the basics in your json workload specification?

Splitting out and running individual elements and so so much more

Additional context
As much as I would like to use this product there is no easy explanations for simple things like

1 get a url from a list
2 http get
3 save that but use the original url and modify it to be a file name.

This is a very basic function that requires passing a filename or url from the first to the third element.

I have been trying to find a way to do this for the last 3 days and there is NO docs.

[StarfallProjects]

Hi @velociwabbit I'm not totally clear what you're asking here, but it sounds like the following might be relevant:

For our data structure (is this what you meant by 'json workload'?) there's a docs section here which contains pages on how data is passed between nodes, how to refer to it, and how to transform it.

For HTTP requests, use the HTTP node.

You can ask for help on the forum, or see if there are workflow templates that do what you're trying to do.

If you have specific docs you want to suggest changes to, feel free to reopen this issue.

[velociwabbit]

thanks for the reply but honestly n8n is really not ready for our use cases. It needs much better conditional logic and clearer ui for the same. It also needs boilerplate for use cases not just complex examples as they are hard to parse Bottom line is that for a developer using node is cleaner and faster for now. I hope this changes but it will take a great deal of effort on your part

…

On Thu, Aug 14, 2025 at 6:44 AM Deborah Barnard ***@***.***> wrote: *StarfallProjects* left a comment (n8n-io/n8n-docs#3075) <#3075 (comment)> Hi @velociwabbit <https://github.com/velociwabbit> I'm not totally clear what you're asking here, but it sounds like the following might be relevant: For our data structure (is this what you meant by 'json workload'?) there's a docs section here <https://docs.n8n.io/data/data-structure/> which contains pages on how data is passed between nodes, how to refer to it, and how to transform it. For HTTP requests, use the HTTP node <https://docs.n8n.io/integrations/builtin/core-nodes/n8n-nodes-base.httprequest/> . You can ask for help on the forum <https://community.n8n.io/c/questions/12>, or see if there are workflow templates <https://n8n.io/workflows/> that do what you're trying to do. If you have specific docs you want to suggest changes to, feel free to reopen this issue. — Reply to this email directly, view it on GitHub <#3075 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACHMT3LR7JZJNFYI4ZQQSB33NSADTAVCNFSM6AAAAAB3BLYU72VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCOBYGMZDIOBTGM> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[StarfallProjects]

@velociwabbit thanks for the feedback. "boilerplate for use cases not just complex examples" is something I will note.