One command
Run one provider setup from an initialized project. Its adapter may handle auth inputs, run its available credential checks, then attempt persistence through Phantom. Supabase, Neon, Turso and Vercel have source resource-creation branches; other adapters attach accounts or supplied credentials. Inspect actual results.
stack add resend
Or retrieve catalog matches for what you're building via stack recommend:
stack recommend "transactional email for my app"Auth flow
Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed.
How-to: Paste an API key from https://resend.com/api-keys.
Secret slots
stack add resend has these 1 catalog secret
slot; verify which values its adapter actually materializes through Phantom:
RESEND_API_KEY
Use stack env export --example for an empty-key skeleton.
Stack does not automatically fill env files or resolve credential placeholders.
stack exec -- <cmd> forwards to installed Phantom exec;
configure and verify the app separately.
Starter templates that include Resend
Selected template init attempts provider setup by default; add --noProvision to inspect config first:
-
stack init --template supabase-posthog-sentry-resend
Related providers in Email
- SendGrid — High-volume transactional mail. API key verified against /v3/scopes on paste.
- Mailgun — API-first email + routing. Key verified against /v3/domains on paste (HTTP Basic).
- Postmark — Deliverability-focused transactional. Account token verified against /servers on paste.
FAQ
Do I need a Resend account to use it with Stack?
Use an existing Resend account and permissions appropriate to the adapter. Creation or attachment behavior is provider-specific. Supply the adapter's API-key inputs. Some checks only validate structure or a limited endpoint; additional credentials and manual setup may be needed. If you don't have a credential yet, create one at https://resend.com and supply the required inputs; inspect verification and persistence results.
Where does Stack store my Resend credentials?
Credential persistence uses the installed Phantom Secrets interface. The catalog declares slot names (RESEND_API_KEY); actual materialized outputs can differ. Stack handles supplied values in memory and records dedicated names in config; manual files and freeform metadata are not generally redacted.
Can I rotate or revoke this integration later?
Use `stack remove resend` for local Resend configuration/MCP cleanup and attempted Phantom cleanup; upstream resources remain. Cleanup can refuse or leave keys stored. Rotate or revoke the underlying Resend credentials through https://resend.com, then update and verify each consumer separately. Doctor does not rotate tokens and can skip already-stored names.