[mayteio]

Problem

• #122019 routes a transactional email through Workflows only when its template is in WORKFLOWS_TEMPLATE_ID_MAP, and it maps password_reset alone.
• The other 35 templates now exist as transactional Workflows templates in the US project, but the flag cannot move them until the map names them.

Changes

• Every template in CUSTOMER_IO_TEMPLATE_ID_MAP now has its Workflows template id, so any of them can move with a flag rule and no deploy.
• Nothing changes for recipients on merge: a template still sends through Customer.io until a rule on transactional-emails-via-workflows matches it.
• The map keeps the order of the Customer.io map, so the two read side by side.
• The registration test in test_email.py gains one assertion: every Workflows key must name a Customer.io template. A mistyped key would otherwise never match a send and leave that template on Customer.io without any error.

Note

The templates read variables.* and the recipient address from the send. They rely on the HTML unescaping that #122019 adds, so this PR needs to land after it.

How did you test this code?

Test rationale: the new assertion catches a key in WORKFLOWS_TEMPLATE_ID_MAP that names no template, which routes nothing and fails silently. It extends test_all_http_templates_are_registered_in_customer_io_map, the existing guard for the same map-registration invariant, rather than adding a test.

• Ran posthog/test/test_email.py in a cloud sandbox against the base branch plus this commit.
• Each id came from the template list in the US project and was checked to be transactional with a live sending workflow.
• Not checked: an end-to-end send for the 35 new entries. The first flag rule for each template is that check.

Release status

• This change is behind a feature flag and is not available to users

Docs update

None.

🤖 Agent context

Autonomy: Human-driven (agent-assisted)

Agent: PostHog Desktop (Claude Code), claude-opus-5-5

• Stacked on feat(email): send transactional emails through workflows behind a flag #122019 by base branch, not gh stack, as requested.
• The same session imported the Customer.io designs as Workflows templates through the PostHog MCP, then built this map from the resulting ids.
• Skills invoked: /designing-email-templates, /writing-tests, /writing-pr-descriptions.
• Duplicate search: gh pr list --search "WORKFLOWS_TEMPLATE_ID_MAP" found only feat(email): send transactional emails through workflows behind a flag #122019.

---

Created with PostHog Desktop

🤖 Generated with Claude Code

[github-actions]

🤖 CI report

⚠️ Trunk lane — backend Python lane

This PR is assigned to the backend Python lane. It runs backend Python tests and may merge in parallel with PRs in other lanes.

⚠️ Duplication (Python) — 1 new duplicated block (worst 82 tokens)

New Python code duplication introduced by this branch. Fails at 70+ tokens in app code, or 150+ tokens when both copies live in test files. Advisory while the gate proves itself: extract a shared helper instead of copying.

First copy	Second copy	Lines	Tokens
posthog/tasks/alerts/detectors/statistical/mad.py:104	posthog/tasks/alerts/detectors/statistical/zscore.py:138	18	82

⚠️ Duplication (TypeScript) — 2 new duplicated blocks (worst 138 tokens)

New TypeScript code duplication introduced by this branch. Fails at 70+ tokens in app code, or 150+ tokens when both copies live in test files. Advisory while the gate proves itself: extract a shared helper instead of copying.

First copy	Second copy	Lines	Tokens
products/warehouse_suggestions/frontend/components/MaterializeSuggestionRow.tsx:31	products/warehouse_suggestions/frontend/components/UnmaterializeSuggestionRow.tsx:36	32	138
products/replay_vision/frontend/replay_scanners/replayScannersLogic.ts:630	products/replay_vision/frontend/replay_scanners/watchFeedLogic.ts:505	11	102

✅ Comment density — 3% of added code lines are comments (1 of 38)

This section warns when comments are more than 3% of the code lines a PR adds, and alerts above 6%. Before agent-assisted PRs, the typical share was about 2%. Only full-line comments count. Docstrings, generated files, snapshots, migrations, and workflow files are left out.

Comments that restate the code, record how the change came about, or narrate the next line add noise for the next reader. Keep the comments that explain a reason the code cannot show, and remove the rest. See .agents/skills/writing-code-comments/SKILL.md for the house rules.

Files with the most added comment lines:

File	Comment lines	Added lines
posthog/test/test_email.py	1	3

This check does not block merging. It updates on every push and clears when the share drops.

✅ Playwright — all passed

All tests passed.

View test results →

[parameterai]

Risk: No findings

This increment routes the Workflows template pin through the settings checks in get_workflows_template_id instead of bypassing them, so a pinned retry only skips the feature flag. The change tightens behavior; the only new edge (Customer.io fallback when the Workflows API key is removed between attempts) is operator-triggered, documented, and tested as intended.

_{Sentinel reviewed 6af879b · Review settings}

[trunk-io]

   

Failed Test	Failure Summary	Logs
test_filter_permission	The test setup failed because the PostgreSQL database connection was closed while querying an instance setting.	Logs ↗︎
test_new_passthrough_field_writes_through_to_team	The test setup failed because the PostgreSQL database connection was closed while querying an instance setting.	Logs ↗︎
test_experiments_config_confidence_level_must_be_between_zero_and_one_4_ninety_percent	The test setup failed because the PostgreSQL database connection was closed while querying an instance setting.	Logs ↗︎
test_project_creation_with_limited_feature	The test setup failed because the PostgreSQL database connection was closed while querying an instance setting.	Logs ↗︎

... and 227 more

View Full Report ↗︎ ⋅ Docs

[a-lider]

All these templates are identical to cio, right?
I checked only the invite and password reset ones

[trunk-io]

😎 Merged successfully - details.

[mayteio]

/depot retry

[mayteio]

/trunk merge

[deployment-status-posthog]

Deploy status

Environment	Status	Deployed At	Workflow
dev	✅ Deployed	2026-10-26 11:23 UTC	Run
prod-us	✅ Deployed	2026-10-26 11:34 UTC	Run
prod-eu	✅ Deployed	2026-10-26 11:36 UTC	Run