Integrations
Temporal Cloud
Setting up and configuring Temporal Cloud for durable workflow execution.
Temporal Cloud Integration
Temporal Cloud is the backbone of Steadybase's workflow execution. All durable workflows — from client onboarding to Drew Coordinator — run on Temporal Cloud.
What Temporal Cloud Provides
- Durable Execution — Workflows survive crashes, retries, and restarts
- State Persistence — Workflow state is maintained across long-running operations
- Signal/Query Model — Human-in-the-loop via signals, state inspection via queries
- Full Observability — Every workflow execution has a complete event history
- SOC 2 Type II — Temporal Cloud is SOC 2 certified
Setup
1. Create a Temporal Cloud Account
Sign up at cloud.temporal.io and create a namespace.
2. Generate mTLS Certificates
Temporal Cloud uses mutual TLS for authentication:
Upload the CA certificate to your Temporal Cloud namespace.
3. Configure Environment Variables
4. Start the Worker
The Temporal worker process polls the task queue and executes workflow/activity code:
Connection Code
Registered Workflows
| Workflow | Task Queue | Description |
|---|---|---|
clientOnboarding | steadybase-gtm | 5-step client onboarding |
leadQualification | steadybase-gtm | Lead scoring and routing |
contentGeneration | steadybase-gtm | Content creation with memory |
ticketResolution | steadybase-gtm | Ticket analysis + SLA tracking |
memoryStore | steadybase-gtm | Long-running durable KV store |
drewCoordinator | steadybase-gtm | 9-step multi-agent orchestration |
Namespace Details
| Setting | Value |
|---|---|
| Namespace | quickstart-steadybase |
| Region | us-west-2 |
| Authentication | mTLS (client certificate) |
| Task Queue | steadybase-gtm |
| Retention | Configured per namespace in Temporal Cloud |
Demo Mode
If Temporal Cloud is not configured (missing TEMPORAL_ADDRESS), Steadybase falls back to demo mode with simulated workers and workflows. This allows exploring the UI and API without a Temporal Cloud connection.