Gupshup

​

Install

pnpm add @botmesh/core @botmesh/gupshup

​

Usage

import { GupshupProvider } from '@botmesh/gupshup'

const provider = new GupshupProvider({
  apiKey: process.env.GUPSHUP_API_KEY!,
  appName: 'MyBotApp',
  source: '917834811114',                          // the app's number
  webhookToken: process.env.GUPSHUP_WEBHOOK_TOKEN!, // callback: …/gupshup?token=<it>
})
// POST /gupshup → res.sendStatus(provider.ingestRequest({ url: req.originalUrl, body, headers }))

• Buttons go out as quick replies (up to 3), then as a list (up to 10), then as numbered text; lists are native up to 10 rows. The list button of degraded buttons reads listButtonText (default 'Options', max 20 characters; 'Opciones' for a Spanish bot). Longer labels are cut to WhatsApp’s limits (titles 20/24 characters) instead of being rejected.
• With @botmesh/server, mount the provider as a route: the ingress passes the request URL to ingest(), so the ?token= callback works as is.
• Use a URL-safe webhookToken (openssl rand -hex 32). A base64 secret pasted raw into ?token= also matches (a literal + is not read as a space), and so does its percent-encoded form.
• chatId = the sender’s phone digits (no +), exactly what the send API expects.
• Media only from public URLs. Gupshup also documents IP allow-listing: do both in production.

​

Next steps

• Channels: choosing a channel, the capability matrix and the cross-channel contract.
• 24-hour window and pricing: templates outside the WhatsApp window.
• Webhook server: mount the provider with @botmesh/server.
• Package README