Summary

• Registers orum as a meeting provider so POST /webhooks/meeting-notes/orum accepts Orum webhooks. Orum documents only the envelope ({ event, payload, test? }) and a prose list of call properties, so the driver logs each delivery and processes nothing. verify() returns unhandled_event_type, which the route answers with a 200 and no Slack page. Nothing is mapped, stored or executed.
• The logs are meant to be the source for writing the real parser, including matching prospect phone numbers to Salesforce contacts (checked against Warp's SF: all 67 stored Orum-via-Gong contacts had a phone and 66 had an Account).
• Lists Orum in the frontend AVAILABLE_INTEGRATIONS and the connector-card icon switches, plus the capabilities registry and docs row.

Known limits, deliberately out of scope for this driver-only PR (raised with the requester over Slack):

• The endpoint is unauthenticated, because the customer's signing key isn't available. Anyone can post forged bodies. When writing the parser, select real deliveries by the x-orum-signature header.
• Every delivery is recorded as auth.status=invalid / "Verification failed", because it rides unhandled_event_type. A monitor keyed on those will count Orum calls.
• Logs hold prospect phone numbers and call transcripts on purpose. There is no retention limit or expiry yet.
• No user can create an Orum connection: connect and initiateOAuth throw for manual providers, so the card can't self-serve.
• The third review round's fixes (budget sharing across nesting, the trimmed-line size bound) were verified with tests and typecheck, not a fourth fresh review.

Test plan

• TZ=UTC pnpm run autofix:local: brand check, oxlint, deps:check, mail jest, mail tz tests and server vitest (1161 files, 14486 tests) all pass. Without TZ=UTC one unrelated mail test (chatHistoryList.test.ts) fails locally in PDT. It hardcodes 12:00 UTC as "now" and is not touched by this PR.
• pnpm --filter @zero/server run types and pnpm --filter @zero/mail run types: clean.
• New __tests__/orum-webhook.test.ts covers:
  • registry lookup and header redaction by pattern, with the signature header kept and mixed-case headers lowercased
  • the raw-body cap, the 1M-char parse skip, and non-JSON bodies
  • key, array, depth, node and char budgets, including a nested phone surviving a huge sibling subtree
  • __proto__ keys and a 300KB transcript still keeping the phone
  • an adversarial worst-case body staying under the trimmed-line bound
• capabilities.test.ts provider count bumped 13 to 14.

Verify in prod

• Axiom dataset cedar-prod (or cedar-staging):

  ['cedar-prod'] | where _time > ago(1h) and message in ("[orum] webhook received", "[orum] webhook trimmed_payload")
  | project _time, message, event, body_length, body_truncated, trimmed_skipped, headers, trimmed_payload
  

• CloudWatch log group /aws/ecs/aws-prod-api/api-service: filter on the same message strings.
• Working: after the customer adds the webhook in Orum (Settings > System > Webhooks, "Call Disposition Added"), each call yields one [orum] webhook received line and one [orum] webhook trimmed_payload line. The route returns 200 with skipped: true, reason: unhandled_event_type. trimmed_payload should show the real field names, and headers should include x-orum-signature.
• Regression: no lines after the customer configures the webhook (route or driver not reached), 4xx/5xx on /webhooks/meeting-notes/orum, json_parse_error set on every delivery (Orum is not sending JSON), or trimmed_skipped: 'body_too_large' on real calls (payloads over 1M chars).

Customer: Warp

🤖 Generated with Claude Code