Content-type: email-template (for automation emails)

[derrickmehaffy]

Tracking issue for the email-template content-type that n8n automations (#12, #13, #14, #15, #33) will read from. Not blocking sign-off — posting so we have a single URL to reference.

Why a content-type

• Non-engineers can edit email copy without touching n8n workflows.
• Strapi is the source of truth for editable content; n8n stays focused on orchestration.
• Style wrapper (header/footer/branding — Automation: Email template #33 concern) lives once in an n8n sub-workflow, not per-template.

Proposed shape

Collection type email-template:

Field	Type	Notes
key	UID, required, unique	Stable slug n8n looks up: plugin-submission-received, plugin-approved, plugin-declined, plugin-changes-requested
subject	string, required	Supports {{ variable }} placeholders
body	richtext (blocks) or markdown	Supports {{ variable }} placeholders
description	text, admin-only	Docs: when this template fires, which variables are available
from_name	string, optional	Per-template override
reply_to	email, optional	Per-template override

Seed entries (one per automation email)

1. plugin-submission-received — Automation: Email to developer: Plugin submission received #12
2. plugin-changes-requested — Automation: Email to developer: Changes requested for your plugin #13 — needs {{ reviewer_feedback }}
3. plugin-approved — Automation: Email to developer: Plugin approved #14
4. plugin-declined — Automation: Email to developer: Plugin declined #15 — needs {{ decline_reason }}

n8n consumption pattern

Strapi lifecycle webhook
  → HTTP GET /api/email-templates?filters[key][$eq]=<slug>
  → Render subject + body with payload variables
  → Shared 'render-email' sub-workflow wraps in branded shell (#33)
  → Send via SMTP/provider

Related

• Architecture: Automations #11 (tracker), Review workflow #8, Business review #9, Security review #10, Automation: Email to developer: Plugin submission received #12, Automation: Email to developer: Changes requested for your plugin #13, Automation: Email to developer: Plugin approved #14, Automation: Email to developer: Plugin declined #15, Automation: Email template #33
• n8n stack + tooling: feat(automation): n8n-mcp local stack, workflow version control, Claude skills #52