---
title: "ezgh workflows"
description: "Workflows: durable workflows that run in your own app."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.ezghcloud.com/llms.txt
> Use this file to discover all available pages before exploring further.

# ezgh workflows

{/* Generated by ezgh-cli's internal/tools/clidocs from the ezgh command tree. Don't edit: change the command's help in ezgh-cli and regenerate. */}

```sh
ezgh workflows <command>
```

EZGH Workflows runs durable workflows written as code in your own application, with the TypeScript, Go or Python SDK: it records every step, retries what failed, and sleeps for minutes or months. Everything is in a project (`--project`, `EZGH_PROJECT` or the profile's).

An app is your code: a push app is an HTTPS endpoint Workflows calls (synced, and signed with the app's signing secret); a pull app's workers poll a task queue. A run is one execution of one of an app's workflows; a schedule starts runs on a cron timetable.

## Flags

This command also takes the [global flags](/cli/reference#global-flags).

## Subcommands

| Command | Description |
| --- | --- |
| [`ezgh workflows apps`](/cli/reference/workflows-apps) | Apps: the code that runs your workflows |
| [`ezgh workflows callbacks`](/cli/reference/workflows-callbacks) | Callbacks: complete what a workflow waits for |
| [`ezgh workflows limits`](/cli/reference/workflows-limits) | Show the project's Workflows limits |
| [`ezgh workflows runs`](/cli/reference/workflows-runs) | Runs: executions of a workflow |
| [`ezgh workflows schedules`](/cli/reference/workflows-schedules) | Schedules: start runs on a cron timetable |

Source: https://docs.ezghcloud.com/cli/reference/workflows/index.mdx