Demo applications built on the TextConvo API.
Website · Developer Docs · API Reference · Support
Seven small applications, each one showing a complete pattern end to end: a lead goes in, TextConvo orchestrates the conversation across SMS, RCS, Voice AI, Email, or WhatsApp, and events come back to your app.
These are demos. They are written to be read and copied from, not deployed as-is. There is no platform code here, no orchestration logic, and no infrastructure — only the integration surface you would write yourself.
Status: each folder currently holds its specification: what the app does, the stack, the event flow, and what you learn from it. Code lands app by app. Watch the repository, or tell us which one you want first.
| App | Shows you | Stack |
|---|---|---|
| Lead capture | A web form that ingests a lead and starts a journey, with server-side key handling | Next.js |
| Appointment scheduling | Turning a reply into a booked slot, and reacting to confirm and cancel events | Express + SQLite |
| Voice AI callback | Handling callback requests and voice outcomes from a journey | FastAPI |
| SMS campaign | Bulk ingestion done properly: batching, rate limits, retries, opt-out suppression | Node.js CLI |
| Journey trigger | Ingesting from different sources so different journeys run, and tracking outcomes | Express |
| Unified inbox | One conversation view across every channel, updated live from webhooks | Next.js + WebSocket |
| CRM integration | Bi-directional sync with HubSpot, GoHighLevel, or Zoho, including field mapping | Express |
Keys stay on the server. No app puts an API key in browser code. Browser talks to your backend; your backend talks to TextConvo.
Idempotent ingestion. A request id per logical lead, reused on retry, so a double-submitted form does not create two leads.
Verified webhooks. Raw body, constant-time comparison, timestamp check, then a fast 2xx and asynchronous processing. See textconvo-webhooks.
Deliberate error handling. Retry 429 and 5xx with backoff; surface 400 and 401 to a human.
Consent taken seriously. Every form captures consent explicitly, and every app honours opt-out immediately. Compliance overview.
- A TextConvo account with API access — contact us
- An API key and source key (Authentication)
- A webhook secret for the apps that receive events
- A phone number you own for testing. Never test against a real customer.
Each app documents its own runtime. Configuration always comes from environment variables, and every folder ships an .env.example when its code lands.
textconvo-sample-apps/
├─ apps/
│ ├─ lead-capture/
│ ├─ appointment-scheduling/
│ ├─ voice-ai-callback/
│ ├─ sms-campaign/
│ ├─ journey-trigger/
│ ├─ unified-inbox/
│ └─ crm-integration/
└─ shared/ # helpers reused across apps, once code lands
Submit the contact form and you get a direct line to Ria, the TextConvo AI orchestrator — call her for a live voice demo, or text her and watch the SMS AI reply in real time. A human follows up within one business day, and the same form is how API credentials, a source key, and a webhook secret are issued.
Handed a TextConvo QR code at an event or in a demo? Scanning it opens the same conversation. The form is simply the path that works for everyone.
| Repository | Purpose |
|---|---|
| textconvo-api-examples | Single-file examples in nine languages |
| textconvo-webhooks | Verification and receivers |
| textconvo-openapi | Generate a typed client |
| awesome-textconvo | Community projects and tutorials |
Built something with TextConvo? A demo app in a framework we have not covered is one of the most useful contributions there is. Read CONTRIBUTING.md, keep it small, and never commit a credential.
SECURITY.md — never open a public issue for a vulnerability.
MIT © TextConvo