Workflows
Describe the business flow. Review it. Run it. Executable YAML workflows orchestrate modules with retries, branching, and Kafka — after your BRD and schemas exist.
Workspace
Plan workflows with AI
After modules and contracts exist, open Workflows in QuickCode Studio. The workspace is List · Editor · Ask: plan endpoint or Kafka flows from your project catalog, review YAML and diagrams in the editor, then Ask AI about a selected workflow — grounded in that workflow’s definition rather than a blank chat.
List · Editor · Ask
Browse workflows, edit YAML and diagrams in sync, then Ask AI about the selected workflow — grounded in that definition, not a blank chat.
Endpoint and Kafka kinds
Plan HTTP endpoint flows or Kafka-backed event flows against module contracts that already exist after DBML.
Suggested from analysis
Project Analysis can surface workflow ideas on the Workflows tab so planning starts from the same approved product brief.
When workflows are written
Suggestions may appear during analysis; authoring and apply happen after modules and contracts exist. QuickCode does not invent full orchestration from the first prompt alone.
Executable YAML
Business logic you can run and version
Workflows are executable YAML with retries, timeouts, branching, and failure/compensation paths. Modules talk over Kafka-backed events and internal API calls — cross-service consistency is orchestrated, not silent two-phase commit.
Branching & parallel
Conditional paths, parallel steps, and foreach-style iteration where the flow needs them.
Triggers
Before/after triggers and service-request triggers keep side effects explicit in the workflow definition.
Reliability knobs
Retry, timeout, fire-and-forget, and idempotency options so integrations fail loudly and recoverably.
Saga / compensation
Failure and compensation branches model long-running business flows without pretending the database is a distributed transaction manager.
Versioning
Workflow definitions are versioned with the project so you can compare and evolve flows the same way you evolve DBML.
Diagram sync
YAML and diagrams stay aligned as you iterate; Ask AI can explain steps or propose YAML changes you still confirm.
Integrations
Internal calls and external systems
Workflows call QuickCode module APIs and can reach external systems. Auth and API-key configuration stay in your project; reusable integration patterns (payment, ERP/CRM, email/SMS) grow into a catalog you reuse across projects.
Internal QuickCode APIs
Steps invoke your generated module endpoints with the same contracts Studio already knows.
External endpoints
Wire third-party calls into the flow; treat OpenAPI import and endpoint discovery as first-class design inputs as you expand.
Honest roadmap labels
Some discovery/catalog features ship progressively — the workflow runtime and Studio authoring path are the durable core today.