Deployment examples for the infrastructure around a TextConvo integration.
Website · Developer Docs · Support
Planned, not started. This repository is reserved for Terraform examples covering the infrastructure you run alongside TextConvo. Nothing has been published yet.
There is no TextConvo Terraform provider, and this repository will not pretend otherwise. What it will contain is the boring, useful infrastructure that sits around an integration: somewhere to receive webhooks, somewhere to keep secrets, and something to alert you when deliveries fail.
In scope
| Example | What it provisions |
|---|---|
| Webhook receiver on AWS | API Gateway, Lambda, and a queue, with the secret in Secrets Manager |
| Webhook receiver on GCP | Cloud Run, Pub/Sub, and Secret Manager |
| Webhook receiver on Azure | Functions, Service Bus, and Key Vault |
| Secret management | Patterns for storing and rotating API keys, source keys, and webhook secrets |
| Observability | Alerts on delivery failures, 4xx spikes, and receiver latency |
| Queue and retry topology | Dead-letter queues and replay for events your app could not process |
Explicitly out of scope
- TextConvo platform infrastructure, in any form. That is private and always will be.
- Any resource that reveals internal architecture, data stores, or service topology.
- Credentials, key material, account identifiers, or environment-specific values.
- Anything that looks like a production configuration. These will be teaching examples with placeholders.
Least privilege by default. Narrow IAM, no wildcard permissions, no long-lived keys where a role will do.
Secrets from a secret manager. Never in variables files, never in state, never in a repository.
Small and composable. One example per concern, readable in a single sitting, rather than a framework you have to adopt.
Pinned versions. Provider and module versions pinned so an example that worked last year still works.
Documented state handling. Remote state and locking shown explicitly, because that is where teams get hurt.
| You need | Go here |
|---|---|
| A working receiver to deploy | textconvo-webhooks |
| Retry and idempotency design | RETRIES.md |
| Client code | textconvo-api-examples |
| Reference documentation | textconvo.ai/docs |
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.
Tell us which platform you deploy on and what you are trying to stand up — open an issue. Demand decides the order these are written in.
Community Terraform examples are welcome and will be labelled as community-maintained. Read CONTRIBUTING.md first, and never commit a credential, account id, or private hostname.
SECURITY.md — never open a public issue for a vulnerability.
MIT © TextConvo