Yes. Zigflow is a Temporal DSL. It is the fastest way to get started with Temporal without writing SDK code.
Write a workflow in YAML. Zigflow validates it and runs it on your Temporal cluster. It is production-ready and open source.
Before and after
Without Zigflow
- Write retry logic, timeout handling and failure recovery in code
- Register workers, activities and task queues before running anything
- Redeploy your application to change a retry count or add a step
- Debug failures by reading SDK stack traces and execution state
- Teach new engineers the Temporal SDK before they can touch workflows
With Zigflow
- Write a YAML file describing the steps
- Validate it with a single command
- Run it on Temporal with no SDK code
- Change behaviour by editing the file
- Share and version workflows like any other configuration
See how it works
Two steps. Fetch a user profile, then send a welcome email. The email step retries up to three times if it fails. Temporal handles retries automatically based on the retry policy defined in the YAML.
Your workflow is a single file. Validate it, run it and share it.
Run your first workflowdocument:
dsl: 1.0.0
namespace: acme
name: onboard-user
version: 1.0.0
do:
- fetchProfile:
call: http
with:
method: get
endpoint: ${ "https://api.acme.com/users/" + ($input.userId | tostring) }
output:
as:
profile: ${ . }
- sendWelcome:
call: http
metadata:
activityOptions:
retryPolicy:
maximumAttempts: 3
with:
method: post
endpoint: https://api.acme.com/emails
body:
to: ${ .profile.email }
template: welcome
Why use Zigflow with Temporal
Readable
A workflow is a single file, not logic scattered across activity handlers and worker registrations. Anyone can read it and understand what it does.
Consistent
Every workflow follows the same structure. Teams stop arguing about how to organise workflow code and start shipping.
Reusable
Workflow files are plain YAML. Version them, share them, review them in pull requests and deploy them independently of your application code.
Faster onboarding
New team members can read and understand a Zigflow workflow without knowing the Temporal SDK. The file explains itself.
Built on Temporal
Every Zigflow workflow runs on Temporal, a battle-tested engine for durable execution. Temporal provides automatic retries, crash recovery and full execution history. Zigflow gives you a declarative interface to that engine, without starting with the SDK.
Ready to try it?
The quickstart takes five minutes. Run your first workflow locally or against your Temporal cluster.