Astro

This guide provides detailed, step-by-step instructions on how to use and deploy Upstash Workflow with Astro. You can also explore our Astro example for a detailed, end-to-end example and best practices.

​

Prerequisites

1. An Upstash QStash API key.
2. Node.js and npm (another package manager) installed.

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.

​

Step 1: Installation

First, install the Workflow SDK in your Astro project:

​

Step 2: Configure Environment Variables

Create a .env file in your project root and add your QStash token. This key is used to authenticate your application with the QStash service.

touch .env

Open the environment file and add your QStash token, as well as the environment you’re running in:

QSTASH_TOKEN="***"
QSTASH_URL="***"

# if you are working on local environment
UPSTASH_WORKFLOW_URL=""

You can learn more about UPSTASH_WORKFLOW_URL from our documentation on local development.

Replace *** with your actual QStash token and url found here:

​

Step 3: Create a Workflow Endpoint

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 with Astro, navigate into your entrypoint file (usually src/index.ts) and add the following code:

• Minimal example

import { serve } from "@upstash/workflow/astro";


export const { POST } = serve<string>(async (context) => {
  const result1 = await context.run("initial-step", () => {
    console.log("initial step ran")
    return "hello world!"
  })

  await context.run("second-step", () => {
    console.log(`second step ran with value ${result1}`)
  })
}, {
  // env must be passed in astro.
  // for local dev, we need import.meta.env.
  // For deployment, we need process.env:
  env: {
    ...process.env,
    ...import.meta.env
  }
})

​

Step 4: Run the Workflow Endpoint

To start your Astro app locally, run the following command:

npm run dev

Executing this command prints a local URL to your workflow endpoint. By default, this URL is http://localhost:3001.

Upstash Workflow is powered by QStash, and QStash needs a publicly accessible URL to run your workflows. You can easily forward your localhost URL to a live URL by following our guide about setting up your workflow endpoint for local development.

Once you have a live URL, proceeed with either one of the following steps:

​

Setting an enviroment variable (recommended)

Set your publically accessible URL (without extensions such as /workflow) as an environment variable. This variable is only needed for local development and doesn’t need to be set in production:

UPSTASH_WORKFLOW_URL="https://<YOUR_NGROK_OR_TUNNEL_URL>/"

​

Using the baseUrl option

As an alternative to setting an environment variable, you can also use the baseUrl option in the serve method. This option is only needed for local development and can be omitted in production:

export const { POST } = serve<string>(
  async (context) => { ... }, {
    // just the base URL, no `/api/workflow`
    baseUrl: 'https://<YOUR_NGROK_OR_TUNNEL_URL>/'
  }
)

​

Triggering the workflow

After setting your live URL as the environment variable or baseUrl option, trigger your workflow by sending a POST request. For each workflow run, a unique workflow run ID is returned:

curl -X POST http://localhost:3000/api/workflow \
    -H "Content-Type: application/json" \
    -d '{"message": "Hello from the workflow!"}'

# result: {"workflowRunId":"wfr_xxxxxx"}

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.

​

Step 5: Deploying to Production

When deploying your Hono app with Upstash Workflow to production, there are a few key points to keep in mind:

1. Environment Variables: Make sure that all necessary environment variables from your .env file are set in your Vercel project settings. For example, your QSTASH_TOKEN, and any other configuration variables your workflow might need.

2. Remove Local Development Settings: In your production code, you can remove or conditionally exclude any local development settings. For example, the baseUrl option in the serve function can be omitted in production.

import { serve } from "@upstash/workflow/astro";

export const { POST } = serve<string>(
  async (context) => { ... }, {
    // just the base URL, no `/api/workflow`
    baseUrl: 'https://<YOUR_NGROK_OR_TUNNEL_URL>/'
  }
)

3. Deployment: Deploy your Astro app to production as you normally would, for example to Vercel, Heroku, or AWS.

4. Verify Workflow Endpoint: After deployment, verify that your workflow endpoint is accessible by making a POST request to your production URL:

curl -X POST <DEPLOYMENT_URL>/api/workflow \
    -H "Content-Type: application/json" \
    -d '{"message": "Hello from the workflow!"}'

5. Monitor in QStash Dashboard: Use the QStash dashboard to monitor your production workflows. You can track workflow runs, view step statuses, and access detailed logs.

6. Set Up Alerts: Consider setting up alerts in Sentry or other monitoring tools to be notified of any workflow failures in production.

​

Next Steps

1. Learn how to protect your workflow endpoint from unauthorized access by securing your workflow endpoint.

2. Explore our Astro example for a detailed, end-to-end example and best practices.

3. For setting up and testing your workflows in a local environment, check out our local development guide.