User manual | AutoBlocks.ai

AutoBlocks helps you automate routine personal tasks with guided AutoBlocks — not a blank canvas. Learn on autoblocks.pro; run your automations on autoblocks.run.

Surface	Production URL	Monorepo path
Marketing	autoblocks.pro	`apps/marketing-web`
Product app	autoblocks.run	`apps/product-web`
API	api.autoblocks.run	`apps/api`
Background worker	Internal (Render worker)	`apps/worker`
Help corpus	Grounds chat + marketing docs	`packages/user-docs`

Documentation map

#	Document	What you will learn
01	Product overview	What AutoBlocks is, Phase 1 scope, who it is for, design principles
02	Architecture (simplified)	How marketing, product, API, worker, and Postgres fit together
03	Routes and navigation	Every URL on `.pro` and `.run`, nav sets, cross-site links
04	AutoBlocks and wizard	Create, edit, activate, and pause your automation units
05	Triggers and execution	Manual, schedule, inbound webhook triggers; how runs execute
06	Templates and onboarding	Template library, first-run onboarding, template-first setup
07	AI assist	Bounded draft, refine, repair, and explain — you stay in control
08	Billing and plans	Free trial, Starter/Plus limits, Stripe checkout, usage
09	Notifications and activity	Email alerts, in-app inbox, execution history
10	Marketing site and help chat	Public docs, pricing, legal, floating help widget
11	Getting started journeys	Step-by-step paths from curious visitor to active user
12	Troubleshooting	Common symptoms, causes, and fixes
13	Account and settings	Profile, theme, notification preferences, sign out
14	Glossary and brand	AutoBlock vs workflow, naming hierarchy, Phase 1 terms

Quick links

Production URLs you use every day:

# Marketing — learn, compare plans, read docs, ask help chat
open https://autoblocks.pro
open https://autoblocks.pro/pricing
open https://autoblocks.pro/docs

# Product — sign up, build AutoBlocks, manage billing
open https://autoblocks.run/signup
open https://autoblocks.run/login
open https://autoblocks.run/routines
open https://autoblocks.run/billing

Local development (from repo root after pnpm install and pnpm dev:quick):

open http://localhost:3000          # marketing-web
open http://localhost:3002          # product-web
open http://localhost:4000/health   # api

Deploy topology is defined in render.yaml at the monorepo root.

At a glance

How the public marketing site, authenticated product app, API, and worker relate in Phase 1.

flowchart TB
  subgraph public [Public — no login]
    MKT["autoblocks.pro<br/>apps/marketing-web"]
    HelpChat["Help chat widget"]
    Docs["/docs articles"]
  end

  subgraph authed [Authenticated product]
    RUN["autoblocks.run<br/>apps/product-web"]
    Dash["/routines · /templates<br/>/activity · /billing · /settings"]
  end

  subgraph server [Server layer]
    API["api.autoblocks.run<br/>apps/api"]
    Worker["autoblocks-worker<br/>apps/worker"]
    DB[(Postgres)]
  end

  MKT --> HelpChat
  MKT --> Docs
  HelpChat -->|"POST /help/chat"| API
  RUN --> Dash
  Dash -->|"session cookie"| API
  API --> DB
  Worker --> DB
  Worker -->|"schedule + pending runs"| DB
  API -->|"Stripe webhooks"| DB

Visitors compare plans and read docs on autoblocks.pro, then sign up on autoblocks.run. The product app talks to api.autoblocks.run with your session. Scheduled runs and pending executions are processed by the worker against shared Postgres — not via browser calls.

AutoBlocks.ai — User Guide

Documentation map

Quick links

At a glance

Related reading