---
title: "Personal automations"
description: "Build and run personal TypeScript workflows in the Runtime that automate repetitive tasks strictly within your own role permissions."
canonical: "https://grid82.com/docs/use/my-automations"
updated: "2026-11-20"
---

# Personal automations

When allowed in your app, **personal automations** let you automate repetitive tasks on the data you can reach (such as weekly pipeline digests, follow-up checklists, or AI triage on newly assigned leads) without waiting for a builder.

## How personal workflows differ from app workflows

Every personal workflow runs **as you**:

|                         | **Personal automation (Runtime)**                               | **App automation (Studio)**                        |
| ----------------------- | --------------------------------------------------------------- | -------------------------------------------------- |
| Owner                   | Your individual user account                                    | The app itself (managed by builders)               |
| Data permissions        | Strictly limited to your own roles on that app                  | Studio reach across the listed `apps`              |
| Outbound HTTP & secrets | Not available (`http` and `egress` require a builder)           | Supported via `egress` allowlist and suite secrets |
| Webhook trigger         | Not available (manual, schedule, and record triggers supported) | Supported (`webhook({ input })`)                   |
| Managing tools          | `my.workflows.*` in REST, CLI, or assistant                     | `workflows.*` in Studio                            |

## Writing, testing, and activating

Personal workflows use the same `"grid82:workflow"` TypeScript SDK as Studio workflows for `db`, `ai`, `step`, and `approval` calls:

1. Ask the [in-app assistant](/docs/use/in-app-assistant) to draft a personal workflow, or upload code via `my.workflows.create` / `my.workflows.code.set`.
2. Run a simulated test (`my.workflows.test`) first. Testing executes real reads while simulating record creates, updates, and deletes so you can verify the trace safely.
3. Activate the workflow (`my.workflows.activate`) once the test trace looks right.

If a run stops with a permission error because your role cannot write a field, ask a builder in your organisation to either update your role or move the automation into an app-level workflow in the Studio.
