whatspro-gateway

KO | EN

gitlite — search

#android #devops #kubernetes #artificial-intelligence #javascript #graphql #vue #claude #cli #chatbot

whatspro-gateway

(★ 10)

No description available.

파일 탐색기

ZIP 다운로드

- CODESIGHT.md
- config.md
- graph.md
- middleware.md
- routes.md
- backup.sh
- Dockerfile
- healthcheck.sh
- README.md
- restore.sh
- redis.js
- onboarding.md
- chromiumSessionPersistence.integration.js
- callwatcher.html
- callwatcher.js
- chat-core.js
- chat.html
- chat.js
- connect.css
- connect.html
- connect.js
- tenants.css
- tenants.html
- tenants.js
- whatspro.html
- browser-qa.js
- tenants-browser-qa.js
- verify-rollback.js
- baileysClient.js
- callWatcher.js
- chatEvents.js
- chatMedia.js
- chatStore.js
- incomingWal.js
- incomingWebhook.js
- operatorLock.js
- phoneUtils.js
- redisReply.js
- sosStore.js
- tenantAdmin.js
- tenantMemoryStore.js
- tenantPurge.js
- tenantReadiness.js
- tenantSnapshot.js
- tenantStore.js
- tenantWorkbook.js
- testModePolicy.js
- whatsappManager.js
- server.js
- alemiSecret.test.js
- backendDefects.test.js
- backup.test.js
- baileysClient.test.js
- callWatcher.test.js
- callWatcherRelink.test.js
- chat-core.test.js
- chatEvents.test.js
- chatMedia.test.js
- chatStore.test.js
- frontendIsolation.test.js
- incomingCall.test.js
- incomingNoiseFilter.test.js
- pdfReceiptFlow.test.js
- realtimeSync.test.js
- resilienceFlow.test.js
- routing.test.js
- sendWalRecovery.test.js
- sosStore.test.js
- tenantAdmin.test.js
- tenantDeleteCascade.test.js
- tenantPurge.test.js
- tenantReadiness.test.js
- tenantStore.test.js
- tenantToken.test.js
- tenantWorkbook.test.js
- testModeChat.test.js
- transportSelection.test.js
- whatsappReconnectPolicy.test.js
- whatsappSessionResilience.test.js
.dockerignore
.env.example
.gitignore
check.stderr.log
check.stdout.log
docker-compose.yml
Dockerfile
package-lock.json
package.json
README.md
WHATSPro-CHAT-FIXES.md

# CDN으로 사용하기

jsDelivr

jsDelivr는 공개 GitHub 리포지토리를 별도 설정 없이 CDN으로 즉시 서빙합니다. 버전과 파일을 고르면 웹페이지에 바로 붙일 수 있는 링크와 예시 코드가 만들어집니다.

버전

파일

링크

예시

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

Standalone WhatsApp Web API Gateway.

## Transport

Messages and calls both ride a single `@whiskeysockets/baileys` socket
(`services/baileysClient.js`), so **one QR scan per tenant** registers everything —
there is no separate call-watcher QR. The client reimplements the `whatsapp-web.js`
`Client` surface, which keeps `services/whatsappManager.js` transport-agnostic.

`WHATSPRO_TRANSPORT` (default `baileys`) and `WHATSPRO_WWEBJS_INSTANCES` switch a tenant
back to the old `whatsapp-web.js`/Chromium path — a restart, no rebuild. That is why
puppeteer and Chromium are still present in the image.

For connecting a website/platform to the bot, see the contract in the companion repo:
[Openbot-fastfood → docs/integration/site-integration.md](https://github.com/xanzada/Openbot-fastfood/blob/main/docs/integration/site-integration.md)

## Deploy

1. Push this folder as a separate GitHub repo.
2. Easypanel app type: Dockerfile.
3. Add env from `.env.example`.
4. Add persistent volume:
   - `/app/whatsapp_auth`

Production requires `WHATSPRO_SESSION_SECRET` and `WHATSPRO_API_TOKEN` of at
least 32 characters plus a non-default `WHATSPRO_PASSWORD` of at least 12
characters. Set `TRUST_PROXY_HOPS` only when the service is behind that exact
number of trusted reverse proxies.

The operator chat pages require an authenticated WhatsPro session. Chats use
an exclusive `new` / `all` / `operator` / `archive` state, synchronize through
authenticated server-sent events, expire after 24 hours, and are retained for
72 hours while archived. Operator replies reset the AI handoff lock to 60
seconds.

## HTTP contract

Send message/media:

```http
POST /api/send
Authorization: Bearer ${WHATSPRO_API_TOKEN}
Content-Type: application/json
```

```json
{
  "instanceId": "prestige",
  "phone": "7776884956",
  "text": "Сәлем"
}
```

Media:

```json
{
  "instanceId": "prestige",
  "phone": "7776884956",
  "text": "Чек",
  "media": {
    "base64": "data:image/jpeg;base64,...",
    "fileName": "receipt.jpg",
    "caption": "Чек"
  }
}
```

## Existing `whatsappManager.js` adaptation

Core logic stays unchanged. Only replace the internal `handleWebhook(mockReq, mockRes)` call inside `client.on('message')` with:

```js
const { forwardIncomingWhatsAppMessage } = require('./incomingWebhook');

await forwardIncomingWhatsAppMessage({
  event: 'messages.upsert',
  source: 'whatspro',
  instance: instanceId,
  instanceId,
  sender: realSender,
  normalizedPhone: cleanNumber,
  senderPhone: cleanNumber,
  messageId: msg.id.id,
  fromMe: msg.fromMe,
  type: msg.type,
  hasMedia: msg.hasMedia,
  body: msg.body || '',
  pushName: msg._data?.notifyName || contactInfo.pushName || contactInfo.name || 'Client',
  contact: contactInfo,
  data: {
    normalizedPhone: cleanNumber,
    senderPhone: cleanNumber,
    key: { remoteJid: realSender, fromMe: msg.fromMe, id: msg.id.id },
    message: messagePayload,
    pushName: msg._data?.notifyName || contactInfo.pushName || contactInfo.name || 'Client',
    contact: contactInfo
  }
});
```

This repo already contains a copied `services/whatsappManager.js`; only the transport bridge should be different from the monolith.

whatspro-gateway

오너의 다른 레포

파일 탐색기

# CDN으로 사용하기

Was this content helpful?

Recent Feedback

whatspro-gateway

오너의 다른 레포

파일 탐색기

# CDN으로 사용하기

Was this content helpful?

Recent Feedback

Download README