Render Workflows is in public beta.

During the beta, bugs or changes in API/SDK behavior are possible as we continue refining the product. We welcome any and all feedback at workflows-feedback@render.com.

Use Render Workflows to rapidly distribute computational work across multiple independent instances:

Workflows are perfect for use cases that benefit from high-performance, distributed execution, such as AI agents, ETL pipelines, and data processing.

1. Using the Render SDK, you can mark functions in your code as tasks.

   Here's minimal TypeScript for defining a task named calculateSquare. First import task from the SDK, then call it with an options object and your task function:

   Here's minimal Python for defining a task named calculate_square. First initialize a Workflows app, then apply the @app.task decorator:

2. In the Render Dashboard, you create a workflow service and link the repo containing your task definitions. Render automatically registers your defined tasks:

   

3. You can now trigger runs of your registered tasks from anywhere (web apps, agents, etc.) using the Render SDK or API.

   Here's minimal TypeScript for triggering a run of calculateSquare and passing the argument 2:

   Here's minimal async Python for triggering a run of calculate_square and passing the argument 2:

   Here's minimal synchronous Python for triggering a run of calculate_square and passing the argument 2:

4. Render spins up each triggered run in its own instance.

   • This usually takes less than a second.

5. A run can trigger additional runs simply by calling the corresponding task function. This is called run chaining.

   Below, the sumSquares task chains two parallel runs of calculateSquare:

   Below, the sum_squares task chains two parallel runs of calculate_square:

Runs execute alongside other Render service types, enabling fast and safe communication over your private network.

We'll address these limitations in future releases following beta:

• Workflows currently only support TypeScript and Python for defining tasks.
  • SDKs for other languages are planned for future releases.
• Workflows do not provide built-in support for automatically triggering runs on a schedule.
  • To schedule runs, you can create a cron job that runs your tasks on the desired schedule.
• If a workflow belongs to a network-isolated environment, its runs cannot communicate with other services in that environment over its private network.
• Workflows do not yet support running tasks on HIPAA-compliant hosts.
  • To prevent accidental PHI exposure, it is not currently possible to create new workflows in a HIPAA-enabled workspace.
  • If you enable HIPAA compliance for a workspace that already has workflows, do not process PHI in your workflows.

Now that you know the basics, you're ready to create your first workflow!

See Limits and Pricing for Render Workflows.