Automations overview
How Grid82 durable TypeScript workflows work, available triggers, built-in approvals and AI steps, and what a workflow cannot call.
A Grid82 workflow is one durable TypeScript file stored in an app’s Automations tab. Workflows run on durable serverless execution, meaning runs can sleep for months or pause for human approvals at zero compute cost while waiting.
Triggers
| Trigger | Fires when | Payload inside trigger |
|---|---|---|
schedule(expr, opts) | A schedule or cron fires (e.g. "weekdays 09:00") | firedAt |
record.created("App.Table", { when? }) | A record is created (and matches when if provided) | record |
record.updated("App.Table", { fields?, when? }) | Specific fields change and match when | record, previous |
record.deleted("App.Table") | A record is removed | previous |
manual({ input }) | Triggered manually by a user, API, or agent | input |
webhook({ input }) | Signed POST to https://{suite}/hooks/{app}/{workflow} | input |
when clauses are evaluated before a workflow run starts, so non-matching changes consume zero workflow steps.
Capabilities and intentional boundaries
Workflows receive six SDK objects (trigger, db, ai, step, approval, http) and cannot use arbitrary npm packages, fetch, timers, or ambient clocks outside step.do:
- Cross-app access. List every app the workflow touches in
apps: ["Sales CRM", "Billing"]. An app workflow runs with Studio-level reach across the apps listed inapps, recording every write under the workflow’s own name. - Outbound HTTP (
egress). List allowed domains inegress: ["hooks.slack.com"]. Secret URLs ("secret:SLACK_WEBHOOK") are configured write-only in suite Automations settings and injected securely by Grid82’s isolated outbound proxy. - No direct email or SMS primitive. Workflows cannot call
notifyor send emails directly. To alert someone, either send ahttp.postto a Slack/Zapier/Make/n8n webhook secret, insert a record into a monitored table, or callapproval.askto place a decision card in a role’s queue. - Human approvals.
approval.ask(label, { role, question, show, timeout })pauses the run until a member with that role approves or rejects in the Runtime (up to 30 days). Only fields placed insideshoware exposed on the approval card. - AI decisions and generation. Call
ai.yes,ai.choose,ai.score,ai.extract, orai.writecleanly as durable steps.
Run lifecycle and testing
- Check (
workflows.check). Compiles TypeScript rules and renders the step diagram without saving a version. - Test (
workflows.test). Runs realdbqueries andaisteps while capturingcreate,update,delete, andhttp.postside effects assimulated, skipping waits, and auto-approvingapproval.ask. Editor tests cost zero monthly workflow steps (capped per day by plan). - Activate. Saving compiles a version; activating switches live triggers onto that version. Runs already paused remain on the version they started on.