# Added Blueprint support for Render Workflows

- Date: 2026-09-16
- Change type: New
- URL: https://render.com/changelog/added-blueprint-support-for-render-workflows

You can now manage your workflow services using [Blueprints](https://render.com/docs/infrastructure-as-code), Render's infrastructure-as-code model.

Define workflows alongside other service types in your Blueprint YAML. Here's an example:

```yaml
services:
  - type: workflow
    name: my-workflow
    runtime: python
    region: oregon
    repo: https://github.com/render-examples/render-workflows-examples-python
    branch: main
    rootDir: hello-world
    buildCommand: pip install -r requirements.txt
    startCommand: python main.py
```

Workflows support _most_ of the same configuration fields as other service types, with exceptions noted in the [Blueprint YAML Reference](https://render.com/docs/blueprint-spec#service-fields). Notably, you don't provide a `plan` field for workflows, because you instead specify compute plans per task [directly in your code](https://render.com/docs/workflows-defining#compute-plan).

*Note the following:*

- Workflows do not yet support [preview environments](https://render.com/docs/preview-environments), which _skip_ replicating any workflows present in your Blueprint (other services are replicated as usual).
- Render rejects a Blueprint that would create a workflow with the same name as an existing Blueprint-managed workflow in your workspace.

Learn more about Render Workflows in the [documentation](https://render.com/docs/workflows).