[thedogwiththedataonit]

What

GetBrew/brew-v2#2071 adds Brew events: triggers Brew starts itself. The first is contact.unsubscribed, a contact unsubscribing with an email's link or their mail app's one-click button. This mirrors it in the SDK.

const trigger = await brew.automations.triggers.ensureBrewEvent({
  event: 'contact.unsubscribed',
  scope: 'domain', // or 'all' (no domainId)
  domainId: 'jd7f0c2a8w1x9m4n6p3q5r8s2t', // a marketing domain from brew.domains.list()
})
trigger.created // true the first time, false afterwards

• triggers.ensureBrewEvent(input, options?) wraps POST /v1/automations/triggers/brew-events. It returns the brand's trigger for one scope, creating it the first time, plus created. Like every POST it carries an auto idempotency key, so a retry replays.
• Exports: EnsureBrewEventTriggerInput, EnsureBrewEventTriggerResponse and BrewEventTriggerConfig.
• Bundled spec and generated types:
  • Trigger provider and trigger-instance source gain brew_event.
  • Trigger rows gain an optional brewEvent.
  • ApiErrorCode gains TRIGGER_NOT_FIREABLE.
• Docs: docs/automations.md gets an "Unsubscribe triggers" section, and the fire JSDoc names the 409 TRIGGER_NOT_FIREABLE refusal.

Spec vendoring

The bundled openapi/public-api-v1.yaml is this repo's main copy plus exactly brew-v2#2071's spec diff, applied with patch. Brew-v2 main also carries the consent-source integration change, which stays with #62 so the two PRs don't overlap. The result is byte-identical to the vendored copies in the CLI and docs PRs.

Merge order and version

• Merge and publish after brew-v2#2071 is deployed. Before then the route 404s.
• Release order: app → docs → this SDK → the CLI PR, which needs ^12.2.0 from npm.
• Version 12.2.0, renumbered from 12.2.0 because this merges before the open feat: brew.send(key, payload) and fire by key (13.5.0) #55 and feat: subpath adapters (Resend, Better Auth, Auth.js, Supabase) and brew.appEmails (13.6.0) #64 (which claimed 12.2.0 and 12.3.0); they renumber when they merge.

Validation

• TDD: tests/resources/automations/triggers/brew-events.test.ts failed first (4/4), then passed. It covers the 201 create, the 200 existing row, a typed DOMAIN_PURPOSE_NOT_ALLOWED and raw: true.
• bun tsc, bun lint, bun run format:check, bun run test (108 files, 649 tests) and bun run build pass.
• node scripts/generate-types.mjs is a no-op on the committed types, which is CI's freshness guard.

🤖 Generated with Claude Code

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

Confidence Score: 5/5

The PR appears safe to merge; removing the unused spec backup is a non-blocking cleanup.

Summary

Adds triggers.ensureBrewEvent for unsubscribe triggers, with exported types, generated API types, and tests.

• Automation builders can set up triggers for contact unsubscribes.

Diagram

sequenceDiagram
  participant Caller
  participant SDK
  participant Brew API
  Caller->>SDK: triggers.ensureBrewEvent(input, options?)
  SDK->>Brew API: POST /v1/automations/triggers/brew-events
  alt Trigger created
    Brew API-->>SDK: 201, row with created=true
  else Trigger already exists
    Brew API-->>SDK: 200, row with created=false
  end
  SDK-->>Caller: Trigger row or raw response

Loading

_{Reviews (2) · Last reviewed commit: "Release as 12.2.0; spec delta for Brew-e..." · Reviewed by Greptile}

[greptile-apps]

Comments Outside Diff

These findings could not be posted inline.

•  Backup keeps a stale spec openapi/public-api-v1.yaml.orig:4 ▶

  openapi/public-api-v1.yaml.orig adds a 67,829-line copy of the old spec. Its examples still mark reasons as optional, while the corrected spec marks it as required. Nothing reads this backup, so it leaves contributors with two conflicting copies to sort through. Remove the unused backup.

  Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!