Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kazzle.com/llms.txt

Use this file to discover all available pages before exploring further.

Automations let your app do work for you in the background. You use them when something should happen automatically instead of waiting for someone to open the app and click a button.

​
Two kinds

AutomationTriggerGood for
ScheduledA time you setDigests, cleanup jobs, reports, sync jobs
WebhookAn incoming HTTP requestStripe events, GitHub events, form submissions
Both live inside an app.

​
How automations fit into apps

An automation is usually a background part of an app. 
App
├── UI
│   └── What people see
└── Process
    └── What runs in the background

​
Scheduled automations

Run on a schedule. Examples:
  • Send a daily sales digest at 9am
  • Clean up old records every night
  • Sync data from another system every 15 minutes

​
Webhook automations

Run when another service sends an event. Examples:
  • Run when Stripe sends a payment event
  • Run when GitHub sends a push event
  • Run when a form provider sends a submission

​
What happens on each run

When an automation triggers:
  1. The app receives the trigger
  2. Kazzle runs the job
  3. The run is recorded
  4. You can check whether it worked

​
Automations vs always-on servers

Process typeRuns whenExample
AutomationSchedule or webhook triggerNightly digest, Stripe webhook
ServerContinuouslyAPI backend, auth service
Use an automation when work should happen only when triggered. Use a server when the app needs something running all the time.

​
Adding automations later

A simple app can start without automations and gain them later - add a daily summary email, connect Stripe events, or run cleanup jobs. See Apps for the full app model.