Short answer: keep the report template with the team that owns the report, and treat email events as an evidence stream rather than as the delivery operation itself. The Node.js service should create one immutable report version, submit one message with a stable idempotency key, and record provider-neutral events against that message. This keeps a template edit from becoming a routing change, and it makes a missing attachment diagnosable.
The useful mental model is a small pipeline. This is the first step in a practical integration:
report version -> message intent -> email submission -> event evidence
Before, one request often does all four jobs. A timeout then leaves an awkward question: did the API reject the email, or did it accept it before the response disappeared? After, the report job owns the artifact, the notification job owns delivery state, and an event consumer closes the loop.…