You can find the project source code on GitHub.
This guide provides detailed, step-by-step instructions on how to use Upstash Workflow with FastAPI. You can also explore the source code for a detailed, end-to-end example and best practices.
If you haven’t obtained your QStash API key yet, you can do so by signing up for an Upstash account and navigating to your QStash dashboard.
First, create a new directory and set up a virtual environment:
Then, install the Workflow SDK and FastAPI:
Create a .env
file in your project root and add your QStash token. This token is used to authenticate your application with the QStash service.
Upstash Workflow is powered by QStash, which requires access to your endpoint to execute workflows. When your app is deployed, QStash will use the app’s URL. However, for local development, you have two main options: use a local QStash server or set up a local tunnel.
To start the local QStash server, run:
Once the command runs successfully, you’ll see QSTASH_URL
and QSTASH_TOKEN
values in the console. Add these values to your .env
file:
This approach allows you to test workflows locally without affecting your billing. However, runs won’t be logged in the Upstash Console.
Alternatively, you can set up a local tunnel. For this option:
QSTASH_TOKEN
from the Upstash Console..env
file with the following:***
with your actual QStash token.UPSTASH_WORKFLOW_URL
to the public URL provided by your local tunnel.Here’s where you can find your QStash token:
Using a local tunnel connects your endpoint to the production QStash, enabling you to view workflow logs in the Upstash Console.
A workflow endpoint allows you to define a set of steps that, together, make up a workflow. Each step contains a piece of business logic that is automatically retried on failure, with easy monitoring via our visual workflow dashboard.
To define a workflow endpoint in a FastAPI project, create a main.py
file that contains your workflow:
Don’t forget to source your environment file to set your environment variables:
After setting your live URL as the environment variable or base_url
option, trigger your workflow by first starting your FastAPI app:
and then making a POST request to your workflow endpoint. For each workflow run, a unique workflow run ID is returned:
See the documentation on starting a workflow for other ways you can start your workflow.
If you are using a local tunnel, you can use this ID to track the workflow run and see its status in your QStash workflow dashboard. All steps are listed with their statuses, headers, and body for a detailed overview of your workflow from start to finish. Click on a step to see its detailed logs.
Learn how to protect your workflow endpoint from unauthorized access by securing your workflow endpoint.
Explore the source code for a detailed, end-to-end example and best practices.
For setting up and testing your workflows in a local environment, check out our local development guide.
You can find the project source code on GitHub.
This guide provides detailed, step-by-step instructions on how to use Upstash Workflow with FastAPI. You can also explore the source code for a detailed, end-to-end example and best practices.
If you haven’t obtained your QStash API key yet, you can do so by signing up for an Upstash account and navigating to your QStash dashboard.
First, create a new directory and set up a virtual environment:
Then, install the Workflow SDK and FastAPI:
Create a .env
file in your project root and add your QStash token. This token is used to authenticate your application with the QStash service.
Upstash Workflow is powered by QStash, which requires access to your endpoint to execute workflows. When your app is deployed, QStash will use the app’s URL. However, for local development, you have two main options: use a local QStash server or set up a local tunnel.
To start the local QStash server, run:
Once the command runs successfully, you’ll see QSTASH_URL
and QSTASH_TOKEN
values in the console. Add these values to your .env
file:
This approach allows you to test workflows locally without affecting your billing. However, runs won’t be logged in the Upstash Console.
Alternatively, you can set up a local tunnel. For this option:
QSTASH_TOKEN
from the Upstash Console..env
file with the following:***
with your actual QStash token.UPSTASH_WORKFLOW_URL
to the public URL provided by your local tunnel.Here’s where you can find your QStash token:
Using a local tunnel connects your endpoint to the production QStash, enabling you to view workflow logs in the Upstash Console.
A workflow endpoint allows you to define a set of steps that, together, make up a workflow. Each step contains a piece of business logic that is automatically retried on failure, with easy monitoring via our visual workflow dashboard.
To define a workflow endpoint in a FastAPI project, create a main.py
file that contains your workflow:
Don’t forget to source your environment file to set your environment variables:
After setting your live URL as the environment variable or base_url
option, trigger your workflow by first starting your FastAPI app:
and then making a POST request to your workflow endpoint. For each workflow run, a unique workflow run ID is returned:
See the documentation on starting a workflow for other ways you can start your workflow.
If you are using a local tunnel, you can use this ID to track the workflow run and see its status in your QStash workflow dashboard. All steps are listed with their statuses, headers, and body for a detailed overview of your workflow from start to finish. Click on a step to see its detailed logs.
Learn how to protect your workflow endpoint from unauthorized access by securing your workflow endpoint.
Explore the source code for a detailed, end-to-end example and best practices.
For setting up and testing your workflows in a local environment, check out our local development guide.