Prefect is a workflow orchestration tool that helps you build, deploy, run, and monitor data pipelines. It makes complex workflows reliable by tracking dependencies and handling failures gracefully.

In this tutorial, you’ll deploy your first workflow to Prefect — by specifying what code should run, where it should run, and when it should run. We’ll save this metadata to a Prefect Server.

1

Create and login to your Prefect Cloud account.

Prefect uses a database to store workflow metadata. For the ease of getting started, we’ll use one hosted on Prefect Cloud. To create an account, we need to install prefect-cloud. We’ll leverage uv, a modern Python package manager, to do this. Run the following commands in your terminal, after which you’ll be prompted in your browser to create or login to your free Prefect Cloud account.

curl -LsSf https://astral.sh/uv/install.sh | sh # Install `uv`.
uvx prefect-cloud login # Installs `prefect-cloud` into a temporary virtual env.
2

What code should run?

Let’s start with a boring Python script that fetches a list of customer ids and processes them all in parallel. You can find this code and other examples hosted in our quickstart repository.

01_getting_started.py
from prefect import flow, task
import random

@task
def get_customer_ids() -> list[str]:
    # Fetch customer IDs from a database or API
    return [f"customer{n}" for n in random.choices(range(100), k=10)]

@task
def process_customer(customer_id: str) -> str:
    # Process a single customer
    return f"Processed {customer_id}"

@flow
def main() -> list[str]:
    customer_ids = get_customer_ids()
    # Map the process_customer task across all customer IDs
    results = process_customer.map(customer_ids)
    return results


if __name__ == "__main__":
    main()

This looks like the ordinary Python you’d write, except there is:

  • a @flow decorator on the script’s entrypoint.
  • a @task decorator on each function called within the flow.

When you run this flow, Prefect dynamically creates a graph of each task and the state of their upstream dependencies. This allows Prefect to execute each task in the right order and, in the case of failure, to recover the state of your workflow and resume from its point of failure.

Let’s run this code locally on your computer. To do that, run the following command in your terminal.

git clone https://github.com/PrefectHQ/quickstart && cd quickstart
uv run 01_getting_started.py

If all went well, you’ll see a link to see its execution graph in the Prefect UI followed by a flurry of state changes and logs as Prefect dynamically discovers and executes your workflow.

00:30:53.633 | INFO    | Flow run 'airborne-ringtail' - Beginning flow run 'airborne-ringtail' for flow 'main'
00:30:53.638 | INFO    | Flow run 'airborne-ringtail' - View at https://app.prefect.cloud/account/...
00:30:53.685 | INFO    | Task run 'get_customer_ids-136' - Finished in state Completed()
00:30:54.512 | INFO    | Task run 'process_customer-d9b' - Finished in state Completed()
00:30:54.518 | INFO    | Task run 'process_customer-113' - Finished in state Completed()
00:30:54.519 | INFO    | Task run 'process_customer-1c6' - Finished in state Completed()
00:30:54.519 | INFO    | Task run 'process_customer-30d' - Finished in state Completed()
00:30:54.520 | INFO    | Task run 'process_customer-eaa' - Finished in state Completed()
00:30:54.523 | INFO    | Task run 'process_customer-b2b' - Finished in state Completed()
00:30:54.523 | INFO    | Task run 'process_customer-90a' - Finished in state Completed()
00:30:54.524 | INFO    | Task run 'process_customer-4af' - Finished in state Completed()
00:30:54.524 | INFO    | Task run 'process_customer-e66' - Finished in state Completed()
00:30:54.526 | INFO    | Task run 'process_customer-e7e' - Finished in state Completed()
00:30:54.527 | INFO    | Flow run 'airborne-ringtail' - Finished in state Completed('All states completed.')
3

Where should it run?

At this point, you’ve successfully run a Prefect flow locally. Let’s get it running off of your machine! Again, for simplicity, we’ll deploy this workflow to Prefect’s Serverless Compute (so we don’t have to wrangle any infrastructure). We’ll tell Prefect to clone https://github.com/PrefectHQ/quickstart and invoke 01_getting_started.py:main.

uvx prefect-cloud deploy 01_getting_started.py:main \
--name my_first_deployment \
--from https://github.com/PrefectHQ/quickstart

If all went well, you’ve created your first deployed workflow.

Since we now know what code to run and where to run it, this can now be invoked remotely. To do that, run the following command and visit the returned link to see the run’s status in the Prefect UI:

uvx prefect-cloud run main/my_first_deployment

Congrats! You’ve just run your first Prefect workflow remotely.

4

When should it run?

Now that you’ve deployed and run your workflow remotely, you might want to schedule it to run automatically at specific times. Prefect makes this easy with the prefect-cloud schedule command.

Let’s schedule our workflow to run every day at 8:00 AM with cron syntax.

uvx prefect-cloud schedule main/my_first_deployment "0 8 * * *"

After running the command, your workflow will automatically execute remotely according to the schedule you’ve set.

You can view and manage all your scheduled runs in the Prefect UI.

Was this page helpful?