workflows

# Glide Workflows Skill

## Overview

Glide workflows automate actions in response to triggers. There are two categories:

| Category | Runs On | Trigger Source | Example |
|----------|---------|----------------|---------|
| **App Interactions** | User's device | User action in app | Button click → navigate |
| **Server-Side Workflows** | Glide servers | External events or schedule | Webhook → add row |

## Workflow Types

### 1. App Interactions (Client-Side)

**Trigger**: User action (button click, screen open, form submit)
**Location**: Created via Layout Editor → Component → Actions

Key characteristics:
- Execute immediately on user action
- Run on the user's device
- Limited to actions that can happen client-side
- Can trigger server-side workflows via "Trigger Workflow" action

Common App Interaction actions:
- Navigate to screen
- Show/hide component
- Set column value
- Open URL
- Send email (via device)
- Trigger Workflow (bridges to server-side)

### 2. Schedule Workflows (Server-Side)

**Trigger**: Time-based schedule
**Location**: Workflows tab

Schedule options:
| Frequency | Configuration |
|-----------|---------------|
| Every 5/15/30 minutes | Automatic |
| Every hour | Automatic |
| Every day | Select days + time |
| Every week | Select day + time |
| Every month | Select date (1-31) + time |

Use cases:
- Daily report generation
- Periodic data sync
- Scheduled notifications
- Cleanup/maintenance tasks

### 3. Webhook Workflows (Server-Side)

**Trigger**: HTTP POST request to unique URL
**Location**: Workflows tab

Receives:
- **Request body** - JSON payload
- **Request headers** - HTTP headers
- **Query parameters** - URL query string

Use cases:
- External system integration (Shopify, Stripe, Zapier)
- API endpoint for third parties
- IoT device data ingestion

### 4. Manual Workflows (Server-Side)

**Trigger**: App Interaction using "Trigger Workflow" action
**Location**: Workflows tab

Features:
- Define input variables
- Variables passed from