feat(integrations): push Resend domain and email events by webhook
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 22/100
- issue の種類
- 機能追加
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- nextjs, react, typescript
- 領域
- api, backend, documentation
調査の方向性
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".
索引モデルが issue の本文から書いたものです。
説明
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
- Declare Resend's webhook in the #28 contract: automatic setup with no extra scope, provider-generated signing secret, steps for setup by hand.
- Automatic: create the webhook with DevMacro's URL and the chosen events, store the returned signing secret encrypted, delete the webhook on disconnect.
- By hand: the user adds the URL in Resend's dashboard and pastes Resend's signing secret into the panel.
- Verify with the Svix scheme, deduplicate on
svix-id, map deliveries to the connection by the per-connection URL. - Domain deliveries become the existing event types, so polling and webhooks show one entry.
- 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 /webhooksreturns 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
- 主要言語
- TypeScript
- スター
- 1
- フォーク
- 1
- 平均マージ
- 6時間 56分
- マージ済み PR（30日）
- 136
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
eddiejaoude/StackDash のほかの issue
-
area: docs documentation priority: P3 size: S
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
eddiejaoude/StackDash#462 ·
メンテナーはふだん 1 日以内に返信
-
area: web bug priority: P3 size: XS
難易度 1/5 1〜3時間 初心者へのやさしさ 85/100
eddiejaoude/StackDash#432 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
area: database bug priority: P3 size: S
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
eddiejaoude/StackDash#419 ·
メンテナーはふだん 1 日以内に返信
-
area: docs bug priority: P2 size: XS
難易度 1/5 1時間未満 初心者へのやさしさ 88/100
eddiejaoude/StackDash#418 ·
メンテナーはふだん 1 日以内に返信
-
accessibility area: timeline bug priority: P3 size: XS
難易度 2/5 1〜3時間 初心者へのやさしさ 80/100
eddiejaoude/StackDash#389 ·
メンテナーはふだん 1 日以内に返信
eddiejaoude/StackDash の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 74/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
open-webui/tether#52 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
voidzero-dev/void#835 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
AykutSarac/jsoncrack.com#616 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
melgarafael/DeskcommCRM#4679 ·
メンテナーはふだん 1 日以内に返信