Skip to main content
Workflows let you automate tasks in your project using a Trigger -> Condition -> Action pattern. When an event occurs, your workflow checks the conditions and runs the actions automatically.

​
Creating a workflow

1

Open workflows

Go to the Workflows section from your project sidebar or ask the AI assistant to create a workflow.
2

Choose a trigger

Select what starts the workflow.
3

Add conditions (optional)

Filter which trigger events should proceed to the action step.
4

Define actions

Choose what happens when the workflow runs.

​
Trigger types

TriggerDescription
WebhookFires when an external service sends a POST request to your workflow URL
Schedule / CronFires on a recurring schedule using cron expressions
DatabaseFires when a row is inserted, updated, or deleted in your project database
New visitorFires when a new unique visitor lands on your site

​
Common use cases

  • Auto-deploy — deploy your site automatically when changes are pushed to GitHub
  • Notifications — send a Slack message or email when a form submission arrives
  • Scheduled tasks — generate a weekly analytics report every Monday
  • React to database changes — send a welcome email when a new user row is created

​
Run history

Every workflow execution is logged in the Run History tab. Each entry shows:
  • Trigger event details
  • Whether conditions were met
  • Action results (success or failure)
  • Execution time

​
Debugging failed runs

Click a failed run in the history to see the full error trace. Common issues include:
  • Invalid webhook payload
  • Network timeouts on external API calls
  • Missing environment variables

​
Dead letter queue

When a workflow fails repeatedly, the event moves to the Dead Letter Queue. From there you can:
  • Replay — retry the failed event with the same payload
  • Dismiss — remove the event from the queue
Check the dead letter queue periodically to catch recurring failures before they affect your users.

​
Workflow credentials

If your workflow calls external APIs, store API keys and tokens in Workflow Credentials rather than hardcoding them. Credentials are encrypted and injected at runtime.