---
title: "AI workflow automation learned from how you work · Projectify"
description: "AI workflow automation built from a video of you doing the job. Projectify writes the steps, Claude runs them for every row, and the checks stop for a person."
url: https://projectify.si/for/ai-workflow-automation
---

# AI workflow automation with a person at every check.

> Show it once: a screen recording, a link or a doc. The AI workflow builder turns it into prompts with blanks, app steps and checks, and Claude runs it when you say go, for one item or a whole list.

Start free: https://app.projectify.si/signup. A month of Premium free, no card. Agents never take a seat.

## Why most automations break by the third week.

- "Building an automation means a week of wiring triggers and testing edge cases." Record yourself doing the job once. Projectify writes the steps, the prompts and their blanks, and you correct a draft instead of building from nothing.
- "When it goes wrong, it goes wrong quietly, a hundred times." Checks are part of the workflow. A run stops at each one in Approvals, and every change is signed and can be undone.
- "The clever tricks only one person knows never make it into the automation." Tricks in the recording become techniques Claude picks when they fit, like the way you crop a product photo or word a size note.

## What the workflow builder actually builds.

- **Learns from a video.** Drop in a recording, a link or a document. You get a summary, a diagram, the steps and a quiz, then a workflow you can edit line by line. For example: New listing: 7 steps and 2 checks, from a 9 minute recording.
- **Runs for many rows.** Point it at a list and Claude works through it when someone runs it. Each row is its own run, with its own result. For example: 6 rows: 2 done, 4 at the dimensions check.
- **Stops where you said.** A check holds the run in Approvals with what Claude did and what it needs from you. You approve it, edit it or send it back. For example: NLP-115: confirm 45 by 38 by 42 cm?
- **Reports back in the channel.** Results land in the project’s chat, and Catch up gives anyone the short version of a day’s runs. For example: Catch up: 11 listings ready, 2 waiting on photos.

## The board it starts with

- Statuses: Queued, Running, At a check, Sent back, Done
- Fields: Workflow, Input, Run by, Started, Result, Check owner
- Views: Table, Board, Tracker, Dashboard
- A workflow, New product listing: Read the product sheet → Write the title and description → Pick and crop the photos → Team checks dimensions and claims (a person checks) → Tag and categorise → Final check before it goes live (a person checks)

## Straight answers about the automation.

### Does it run on triggers, like when a form comes in?

No. Runs happen when someone runs them, in Projectify or from Claude, for one item or a list. There are no background triggers, so a person is behind every run.

### Can I trust AI with the steps that matter?

Put a check after any step you would not let a new hire skip. The run waits there for a person, and every change it made says who it was for and can be undone.

### Which apps can a workflow step work in?

An app step names the app and the settings to use. Claude does it with the tools it has where you run it, or a person does it and ticks it off. Trello, Monday, Azure DevOps and GitHub also sync with Projectify directly.

### Whose AI pays for the runs?

Claude runs on your own Claude plan, and reading files runs on the workspace’s own AI key. Projectify never marks up a model.

Related: [Workflow management](https://projectify.si/for/workflow-management.md), [SOPs](https://projectify.si/for/sops.md), [AI agents](https://projectify.si/for/ai-agents.md), [Content operations](https://projectify.si/for/content-operations.md). Every kind of work: [For your work](https://projectify.si/for.md).