Skip to main content
Workflows let your app run background jobs and scheduled tasks. They are powered by Inngest 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:
TypeTriggerExample
Scheduled jobs (Cron)Run on a fixed scheduleSync Salesforce contacts every hour
Event-driven functionsTriggered by events in your appSend 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.
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.

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:

Data sync

Pull data from external services on a schedule. Sync contacts from Salesforce, tickets from Jira, or transactions from Stripe.

Automated notifications

Send Slack messages, emails, or other notifications when conditions are met — overdue tasks, new signups, or threshold breaches.

Batch processing

Process large datasets in the background. Generate reports, aggregate metrics, or transform data on a schedule.

Cleanup jobs

Remove stale records, archive old data, or reset temporary states on a recurring schedule.

What’s next