feat: WhatsApp platform wiring (Step 2)#55
Open
zshanhui wants to merge 3 commits into
Open
Conversation
- Add whatsapp_message_log migration and model with idempotent inserts - Mount GET/POST /api/webhooks/whatsapp with raw body for signature verify - Add config, signature, and ingest services behind WHATSAPP_ENABLED - Add .env.example, AGENTS.md and routes.md docs, mocha specs Co-authored-by: zshanhui <zshanhui@users.noreply.github.com>
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| 14986488 | Triggered | Generic Password | e1ff300 | .env.example | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
- Convert webhook route, services, model, and specs from JS to TS - Add shared types in src/shared/whatsapp.ts - Remove duplicate .js implementations; use named export for router Co-authored-by: zshanhui <zshanhui@users.noreply.github.com>
Co-authored-by: zshanhui <zshanhui@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements Step 2 — Platform wiring from the WhatsApp integration plan (Step 1 discoverability deferred).
What's included
GET/POST /api/webhooks/whatsapp— Meta subscription verification and signed event ingestwhatsapp_message_logtable — Idempotent audit log for inbound messages, delivery statuses, and other webhook eventsconfig,signature(HMAC-SHA256),ingest(parse + persist)WHATSAPP_ENABLED+WHATSAPP_APP_SECRETrequired for POST; route mounts whenWHATSAPP_VERIFY_TOKENor enabled.env.example— Documented WhatsApp env varsspecs/whatsapp/*(signature, ingest parsing, DB dedupe)How to test locally
.env.example→.envand setWHATSAPP_VERIFY_TOKEN,WHATSAPP_ENABLED=true,WHATSAPP_APP_SECRETpnpm run db:migrateNODE_ENV=development npx tsx ./bin/wwwwhatsapp_message_logNot in this PR
wa.melinks