feat: welcome email with Resend integration by orveth · Pull Request #980 · MakePrisms/agicash

orveth · 2026-04-03T19:59:50Z

Summary

Welcome email sent via Supabase Edge Function when a new user signs up.

Edge Function (supabase/functions/welcome-email/index.ts) — creates Resend contact + sends welcome email via template. Retries up to 2x with exponential backoff. Handles both webhook and manual payloads.
DB trigger (wallet.handle_new_user) — fires on INSERT to wallet.users, calls Edge Function async via pg_net. Skips guests (null email). Only fires for genuine inserts (not upsert-updates).
Hosted assets — logo PNG + 6 section icon PNGs in public/ for email template rendering

Setup required

Deploy Edge Function: supabase functions deploy welcome-email
Set Edge Function secrets: RESEND_API_KEY, RESEND_AUDIENCE_ID, RESEND_WELCOME_TEMPLATE_ID
Set Vault secrets: edge_function_base_url, service_role_key
Apply migration

Manual retry: Invoke from Supabase dashboard with { "email": "user@example.com", "firstName": "Name" }

Test plan

Template live-tested with bob and josip — logo, icons, layout render correctly
TypeScript compiles clean
Deploy Edge Function to staging and test with real user insert
Verify trigger fires only on INSERT (not upsert-update for returning users)

🤖 Generated with Claude Code

Adds email service, API route, and tests for sending welcome emails to new signups via Resend. Blocked on Resend dashboard + DNS config. - email-service.server.ts: ky-based Resend integration (createContact, sendWelcomeEmail, handleNewSignup) - api.welcome-email.ts: POST endpoint with Zod validation - email-service.server.test.ts: 11 tests covering happy path and error cases Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…sets - Fix Resend API: use `template` object with `variables` (not `template_id`) - Use verified domain `emails.agi.cash` (not `email.agi.cash`) - Add full logo and section icon PNGs to public/ for email template - Convert 6 SVG section icons to PNGs (email clients strip SVGs) - Pass `email` variable for unsubscribe link in template footer Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

vercel · 2026-04-03T19:59:58Z

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

Project	Deployment	Actions	Updated (UTC)
agicash	Ready	Preview, Comment	Apr 10, 2026 7:49pm

supabase · 2026-04-03T20:00:01Z

This pull request has been ignored for the connected project hrebgkfhjpkbxpztqqke because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

Move env var validation from module-level (crashes on import) to function-level (crashes only when email features are actually called). Fixes Vercel deploy crash when Resend env vars aren't configured. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

GET /api/unsubscribe?email=<base64> marks the contact as unsubscribed via Resend PATCH API and returns a branded HTML confirmation page. Also passes unsubscribeUrl template variable to the welcome email. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Supabase Edge Function (Deno) that sends welcome emails via Resend API when a new user is inserted into wallet.users. Trigger skips guests (null email). Function retries up to 2x with exponential backoff. Also supports manual invocation with { email, firstName } payload. Migration creates pg_net trigger that calls the Edge Function async. Vault secrets required: edge_function_base_url, service_role_key. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Edge Function replaces the app-level email service. Unsubscribe is out of scope for the transactional welcome email — will be added when marketing emails are introduced. Removed: - app/features/email/email-service.server.ts - app/features/email/email-service.server.test.ts - app/routes/api.welcome-email.ts - app/routes/api.unsubscribe.ts Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

gudnuf · 2026-04-03T22:35:36Z

public/email-icons/dollar.png

@jbojcic1 we needed to have the icons be pngs so they show up in all email clients (see discord here)

wdyt about hosting them here? Seems fine for now.

I see. Yeah seems fine. Can't be uploaded to resend where template is created?

Resend templates reference images by URL — they don't host the files. So the images need to live somewhere publicly accessible. Our public/ dir serves them via Vercel (agi.cash/agicash-logo.png). We could use an external CDN instead, but public/ is simpler for now.

gudnuf · 2026-04-03T22:36:16Z

public/agicash-logo.png

this is needed so we can render the logo in the welcome email

Contact/audience management is not needed for a single transactional welcome email. Edge Function now makes one API call (send email) instead of two. RESEND_AUDIENCE_ID env var no longer required. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

supabase/migrations/20260403220000_welcome_email_webhook.sql

supabase/functions/welcome-email/index.ts

public/email-icons/dollar.png

- Use ky (npm:ky@1.7.5) with built-in retry instead of custom withRetry - Validate payload with zod (npm:zod@3.24.3) - Remove WebhookPayload type — trigger sends simple { id, email, firstName } - Include user ID in trigger payload and Edge Function response Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

jbojcic1 · 2026-04-03T22:42:15Z

supabase/migrations/20260403220000_welcome_email_webhook.sql

+  end if;
+
+  -- fire async HTTP request to the welcome-email edge function via pg_net
+  select net.http_post(


what happens if this call fails? will Supabase retry?

pg_net does not retry. The HTTP request fires once asynchronously. If it fails, the response is logged to net._http_response (unlogged table, cleared after 6h) but there's no automatic retry. The DB transaction is not affected — the user insert always succeeds regardless.

For now this is acceptable (welcome email is best-effort). If we need retries later, we'd add pgmq as discussed.

jbojcic1 · 2026-04-03T22:43:31Z

supabase/functions/welcome-email/index.ts

+      },
+    );
+  } catch (error) {
+    console.error("Welcome email function error:", error);


we need to see how to send this to Sentry

Agreed. Supabase Edge Functions support @sentry/deno (npm:@sentry/deno). We'd need to:

Add Sentry DSN as an Edge Function secret

Initialize Sentry in the function

Capture exceptions

I'll note this as a follow-up — want me to add it now or keep it separate?

jbojcic1 · 2026-04-03T22:44:18Z

supabase/functions/welcome-email/index.ts

+  email: string,
+  firstName: string | undefined,
+): Promise<void> {
+  await resend.post("emails", {


there should be some timeout so that this can't take too long because edge function can cost more if it takes too long (correct me if I am wrong)

Good point. Adding a timeout to the ky client config. ky's default timeout is 10s which is reasonable, but I'll set it explicitly to 10s to be clear. The Edge Function itself has a 150s wall clock limit (free) / 400s (paid), but 2s CPU limit — our async HTTP calls don't count against CPU, only wall clock.

jbojcic1 · 2026-04-03T22:44:56Z

supabase/functions/welcome-email/index.ts

+      Authorization: `Bearer ${apiKey}`,
+    },
+    retry: {
+      limit: 2,


does this mean initial attempt plus 2 retries meaning 3 total or 2 total?

ky's retry.limit means number of retries AFTER the initial attempt. So limit: 2 = 1 initial + 2 retries = 3 total attempts. Adding a comment to clarify.

jbojcic1 · 2026-04-03T22:45:35Z

supabase/functions/welcome-email/index.ts

+    "authorization, x-client-info, apikey, content-type",
+};
+
+Deno.serve(async (req) => {


how does one invoke this function manually from the Supabase dashboard now?

From the Supabase Dashboard: Edge Functions → welcome-email → "Test" button. You can send a POST request with the payload:

{ "id": "user-uuid", "email": "user@example.com", "firstName": "Name" }

Or via CLI:

curl -X POST https://<project>.supabase.co/functions/v1/welcome-email \ -H "Authorization: Bearer <service_role_key>" \ -H "Content-Type: application/json" \ -d '{"id":"user-uuid","email":"user@example.com","firstName":"Name"}'

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Captures exceptions and flushes to Sentry before returning error responses. Uses Sentry Deno SDK with defaultIntegrations disabled (no Deno.serve instrumentation). Tags with SB_REGION and SB_EXECUTION_ID for observability. New secrets needed: SENTRY_DSN, SENTRY_ENVIRONMENT (optional, defaults to production). Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

gudnuf · 2026-04-10T06:52:16Z

@jbojcic1 orveth added the 10s timeout with retry and sentry to this PR. I still need to test it, but code lgtm

gudnuf · 2026-04-10T19:10:41Z

supabase/functions/welcome-email/index.ts

+
+    const { id, email, firstName } = result.data;
+
+    const apiKey = getRequiredEnv("RESEND_API_KEY");


@jbojcic1 any updated thoughts on this thread?

I still think we should keep the api keys seperate per capability to keep them isolated, resend logs also allows you to filter by api key so we can see logs for the emails triggered by our code vs. the emails that open secret is sending. If we ever need to revoke a key we don't have to remember to rotate all the places using the same key.

gudnuf · 2026-04-10T19:11:52Z

supabase/functions/welcome-email/index.ts

+
+    await sendWelcomeEmail(resend, templateId, email, firstName);
+
+    console.log("Welcome email sent", { id, email });


should we also send this log to sentry?

Uses `welcome-email/<user-id>` as the idempotency key on POST /emails to prevent duplicate sends. Makes user ID required in the payload schema. Resend deduplicates within a 24h window. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

deno.land/x/sentry stopped at 8.55.0 — 9.6.0 was never published there. The SDK migrated to npm as @sentry/deno. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

gudnuf · 2026-04-10T20:13:12Z

supabase/functions/welcome-email/index.ts

+): Promise<void> {
+  await resend.post("emails", {
+    headers: {
+      "Idempotency-Key": `welcome-email/${id}`,


I added this. The key expires after 24 hours so we could then send again after that. This seems like a good safeguard to not accidentally spam our users like what happened with Maple

orveth and others added 2 commits April 3, 2026 12:59

vercel bot had a problem deploying to Preview April 3, 2026 20:00 Failure

orveth self-assigned this Apr 3, 2026

vercel bot deployed to Preview April 3, 2026 20:12 View deployment

vercel bot deployed to Preview April 3, 2026 21:11 View deployment

vercel bot deployed to Preview April 3, 2026 22:10 View deployment

vercel bot deployed to Preview April 3, 2026 22:28 View deployment

gudnuf reviewed Apr 3, 2026

View reviewed changes

public/agicash-logo.png

Copy link
Copy Markdown

Contributor

gudnuf Apr 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is needed so we can render the logo in the welcome email

jbojcic1 reviewed Apr 3, 2026

View reviewed changes

vercel bot deployed to Preview April 3, 2026 22:38 View deployment

vercel bot deployed to Preview April 3, 2026 22:40 View deployment

jbojcic1 reviewed Apr 3, 2026

View reviewed changes

fix: add explicit 10s timeout, clarify retry count

c9572bf

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

vercel bot deployed to Preview April 3, 2026 22:47 View deployment

vercel bot deployed to Preview April 3, 2026 23:34 View deployment

gudnuf marked this pull request as ready for review April 10, 2026 06:52

orveth assigned gudnuf Apr 10, 2026

gudnuf reviewed Apr 10, 2026

View reviewed changes

orveth and others added 2 commits April 10, 2026 12:28

fix: use npm import for Sentry Deno SDK

bf2c3c9

deno.land/x/sentry stopped at 8.55.0 — 9.6.0 was never published there. The SDK migrated to npm as @sentry/deno. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

vercel bot deployed to Preview April 10, 2026 19:49 View deployment

gudnuf reviewed Apr 10, 2026

View reviewed changes

orveth mentioned this pull request Apr 10, 2026

feat: welcome email via Vercel API route + DB trigger #990

Open


		const { id, email, firstName } = result.data;

		const apiKey = getRequiredEnv("RESEND_API_KEY");


		await sendWelcomeEmail(resend, templateId, email, firstName);

		console.log("Welcome email sent", { id, email });

Conversation

orveth commented Apr 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Setup required

Test plan

Uh oh!

vercel bot commented Apr 3, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

supabase bot commented Apr 3, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

gudnuf commented Apr 10, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

orveth commented Apr 3, 2026 •

edited

Loading

vercel bot commented Apr 3, 2026 •

edited

Loading