> ## Documentation Index
> Fetch the complete documentation index at: https://docs.vybe.build/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflows Overview

> Run background jobs and scheduled tasks in your Vybe app with Inngest-powered workflows

Workflows let your app run background jobs and scheduled tasks. They are powered by [Inngest](https://www.inngest.com/) and run server-side with full access to your app's database and integrations.

***

## What are workflows

Workflows are functions that run in the background, either on a schedule or in response to events in your app. Common uses include:

* Syncing data from external services on a recurring schedule
* Sending automated email or Slack notifications
* Processing batch data operations
* Cleaning up old records or stale data
* Polling external APIs for updates

***

## Types of workflows

Vybe supports two types of workflows:

| Type                       | Trigger                         | Example                                          |
| -------------------------- | ------------------------------- | ------------------------------------------------ |
| **Scheduled jobs (Cron)**  | Run on a fixed schedule         | Sync Salesforce contacts every hour              |
| **Event-driven functions** | Triggered by events in your app | Send a notification when a new record is created |

**Scheduled jobs** use cron expressions to define when they run — every few minutes, hourly, daily, weekly, or on any custom schedule.

**Event-driven functions** listen for events your app emits and run automatically when the event fires.

<Note>
  Vybe does not currently support inbound webhooks. To react to changes in an external system, use a scheduled job to poll the API at regular intervals.
</Note>

***

## How workflows run

Workflows are deployed alongside your app. When you click **Deploy**, Vybe registers your workflow functions with Inngest, which handles scheduling, execution, and retries.

During development, workflows are synced to your sandbox so you can test them before deploying to production.

***

## Use cases

Common patterns for workflows:

<CardGroup cols={2}>
  <Card title="Data sync" icon="arrows-rotate">
    Pull data from external services on a schedule. Sync contacts from Salesforce, tickets from Jira, or transactions from Stripe.
  </Card>

  <Card title="Automated notifications" icon="bell">
    Send Slack messages, emails, or other notifications when conditions are met — overdue tasks, new signups, or threshold breaches.
  </Card>

  <Card title="Batch processing" icon="layer-group">
    Process large datasets in the background. Generate reports, aggregate metrics, or transform data on a schedule.
  </Card>

  <Card title="Cleanup jobs" icon="broom">
    Remove stale records, archive old data, or reset temporary states on a recurring schedule.
  </Card>
</CardGroup>

***

## What's next

* [Creating Workflows](/workflows/creating-workflows)
* [Managing Workflows](/workflows/managing-workflows)