PR Custody

fix: skip activation emails for developer platform users

@palash-cchecks n/achecks…fix/skip-developer-activation-emails → main27 files · +2176 −32review: @sarahsimionescuupdated 1mo ago

▸Description · 1 noise

Activation emails now check onboarding_platform metadata instead of relying solely on consumer project existence
Users who chose "developer" during onboarding are skipped entirely from the consumer activation email sequence
This prevents developers from receiving consumer-focused onboarding emails (the hi@composio.dev sequence)

Previously, activation emails were only gated on having a consumer project (type: "CONSUMER"). This was unreliable because:

Consumer projects are auto-provisioned via consumerMiddleware when developers visit any /connect page
So a developer who just browses Connect would start receiving consumer emails

Check users.metadata.onboarding_platform (set during onboarding) and skip the workflow if it equals "developer".

if (onboardingPlatform === "developer") {
  return { ok: false, error: "developer_platform_user" };
}

Slack thread: https://composioworkspace.slack.com/archives/C0574UJUXD2/p1777833068065009
For Loops sequences: Hermes needs to sync onboarding_platform to Loops contacts so sequences can filter there too

🤖 Generated with Claude Code

▸ 1 bot/status comment hidden

@vercel[bot]1mo ago

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
dashboard	Ready	Preview, Comment	May 4, 2026 5:42pm

loading diff…