Shoud I create a workflow for every trigger, or can I concentrate everything inside one workflow?

Hello, I would like to know the best practice for different triggers. Create a workflow for each, or can I keep them all within one?

The workflow in question is the sale of an infoproduct, the problem is that on the platform I use, I have to create 1 trigger for each product.

Is there any problem placing all the flows within a workflow, or should I separate each one by workflow?

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Hi @mcdonnel ,

Welcome to the community! :tada:

The implementation you have at the moment should be fine. The only caveat could be, if your workflows consume a lot of memory or data, and get triggered simultaneously, you might run into some slower executions or even OOM events - depending on how you’re running n8n and your memory capacity. But this can also happen in large “single” workflows.

If this is the case I would suggest dividing the workload of each workflow into smaller chunks, like sub workflows, but you can still keep them all in one “workflow”. You can check out this docs to get a better idea of the best practices we hold regarding this: Cloud data management | n8n Docs; Execution data | n8n Docs; Memory-related errors | n8n Docs

It might also be easier to debug, test and track performance when the workflows are separate since they’ll get individual ids and it’s easier to map out errors. The execution count is the same either way. But performance-wise you should be good :slight_smile:

1 Like

Your design can be simplified to that one:

As it consists of 3 equal in design parts