feat(integrations): push Resend domain and email events by webhook

Abierto
  • ¿Algo no está bien?
#427 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
22/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
nextjs, react, typescript
Área
api, backend, documentation

Línea de trabajo

Start with the existing provider adapter in src/lib/adapters/resend/ and the webhook-ingest contract from #28, since the create/verify/dedupe steps must fit the pattern already established there; the setup panel from #426 supplies the by-hand path. Read docs/providers/resend.md for the documented event names and Svix header scheme, and confirm the open question about whether POST /webhooks returns the signing secret before writing the automatic path. Done looks like the acceptance criteria met: unit tests over recorded sanitized payloads, both setup paths covered in a Playwright spec against the simulated provider, and the doc section renamed to "Webhooks".

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area: integrations blocked enhancement impact: medium priority: P1 size: S

Context

Decision on #424 (2026-11-14): Resend offers both automatic setup and setup by hand. Automatic setup needs no new access: DevMacro already holds full_access (Resend has no read-only scope), which allows POST /webhooks. It does add a webhook the user can see in their Resend team, which the panel copy in #426 says.

From docs/providers/resend.md, "Webhooks (Post-MVP)":

Item Value
Create POST /webhooks with full_access
Signing Svix: svix-id, svix-timestamp, svix-signature (v1,<base64>), verified against the raw body with the per-webhook signing secret. Reject stale timestamps
Events for the timeline domain.updated (the adapter's resend.domain.verified and resend.domain.failed), plus email.bounced, email.complained, and email.failed if they become timeline events
Not pushed Quota and usage. Polling stays

Plan

  1. Declare Resend's webhook in the #28 contract: automatic setup with no extra scope, provider-generated signing secret, steps for setup by hand.
  2. Automatic: create the webhook with DevMacro's URL and the chosen events, store the returned signing secret encrypted, delete the webhook on disconnect.
  3. By hand: the user adds the URL in Resend's dashboard and pastes Resend's signing secret into the panel.
  4. Verify with the Svix scheme, deduplicate on svix-id, map deliveries to the connection by the per-connection URL.
  5. Domain deliveries become the existing event types, so polling and webhooks show one entry.
  6. Docs: docs/providers/resend.md (rename the section to "Webhooks", both setup paths).

Acceptance criteria

  • Automatic setup creates the webhook and a domain change reaches the timeline within a minute.
  • Setup by hand works with a pasted signing secret.
  • Disconnect deletes an automatic webhook.
  • Unsigned, wrongly signed, stale, or repeated deliveries are rejected or ignored, and logged without their body.
  • An event seen by webhook and by polling shows once.
  • Unit tests on recorded, sanitized payloads from Resend's documented samples. No live calls in CI.
  • Playwright e2e: both setup paths for the simulated Resend provider.

Unverified

  • Whether POST /webhooks returns the signing secret in its response.

Files and areas

  • src/lib/adapters/resend/, docs/providers/resend.md.
  • Non-goals: new scopes, pushing quota (no webhook exists for it).

Verification

  • npm run lint, npm run typecheck, npm test
  • Playwright spec for both setup paths.

Depends on

  • #28 Ingest provider webhooks
  • #426 Webhook setup panel

Branch: <issue-number>-resend-webhooks
Closes with a Closes #<issue-number> footer on the commit or pull request.

Model: anthropic/claude-opus-5-5 | Reasoning effort: unknown

Lenguaje dominante
TypeScript
Estrellas
1
Forks
1
Merge medio
6 h 56 min
PR fusionados (30 d)
136

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de eddiejaoude/StackDash

Todos los issues de eddiejaoude/StackDash

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.