Email handling as apps grow – how are you structuring it?

RE: Email handling as apps grow – how are you structuring it?

Arunkumar Arumugam — Tue, 10 Feb 2026 03:28:41 GMT

Thanks everyone, this is helpful.

We’re moving toward a centralized async email utility subprocess so the core models stay focused on business flow.

We’ll standardize sender/template config there and contain retries + failure logging within that layer.

Appreciate the insights.

RE: Email handling as apps grow – how are you structuring it?

Shubham Aware — Tue, 10 Feb 2026 01:40:47 GMT

Keep email logic in a reusable utility subprocess with standard inputs/outputs, and keep main process models focused on core business flow.
Main process triggers email subprocess asynchronously, subprocess handles retries and logs failures separately.

RE: Email handling as apps grow – how are you structuring it?

Stefan Helzle — Mon, 09 Feb 2026 06:52:34 GMT

I would also opt for a reusable model. It makes it easy to enforce using certain templates or other settings like sender email.

RE: Email handling as apps grow – how are you structuring it?

Harsha Sharma — Mon, 09 Feb 2026 06:07:17 GMT

[quote userid="328186" url="~/discussions/f/best-practices/40173/email-handling-as-apps-grow-how-are-you-structuring-it"]do you keep email logic in the main process, or move it to a reusable subprocess[/quote]

A reusable process having send email node with parameters like to,cc,attachmnets, body,subject etc. Only if there is a specific email template is there not inline with generic emails we send then that node is put directly in respective process model. Otherwise we use the reusable sub process.