Vibecode Zapier
track this build5 phases, 15 steps, beginner friendly0%KINDA · weekend project
A few personal automations are easy; Zapier's moat is the 9,000+ app integration catalog, auth handling, retries, task history, UI, and reliability.
the project pack5 files · written for this build, step by step
You are building a lean indie version of Zapier. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Zapier · indie build Build a small code-defined automation runner with durable run history. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Zapier acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. - Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. - [ ] **Confirm the bounded replacement** · No paid service required for this local step. - Why: The full commercial product is larger than this guide. - Get it: The deliverable is a small code-defined automation runner with durable run history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. - Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` Then copy `.env.example` to `.env` and fill in the values it documents. ## Honest limits This build deliberately does not replace: - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - This is a small code-defined automation runner with durable run history; full Zapier feature parity, vendor hosting and support are not included. - integration catalog - OAuth maintenance - retries/history - nontechnical builder - app triggers/actions - uptime If one of those is essential to you, that is the reason to keep paying for Zapier, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · Zapier The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a small code-defined automation runner with durable run history as a bounded replacement for Zapier. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - pipelines(id,name,trigger,enabled) - runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until) - steps(id,run_id,step_key,state,result_ref) - audit(id,run_id,event,at) - pipelines/*.py are trusted owner code - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: One signed webhook writing a row to a local CSV and one scheduled daily local summary. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Zapier acceptance sample: Create synthetic sample data before implementation: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a small code-defined automation runner with durable run history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a small code-defined automation runner with durable run history, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: pipelines(id,name,trigger,enabled); runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until); steps(id,run_id,step_key,state,result_ref); audit(id,run_id,event,at); pipelines/*.py are trusted owner code. Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start triggers and contracts until these checks pass. ### Phase 2 · Triggers and contracts Build: Triggers and contracts for Zapier: Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. - Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. - Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: A forged signature returns 401 and creates no run. Then check: Replaying the same event queues one run. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Never allow webhook payloads to choose Python module paths or execute code. Done when: A forged signature returns 401 and creates no run. Replaying the same event queues one run. Do not build yet: Do not start durable execution until these checks pass. ### Phase 3 · Durable execution Build: Durable execution for Zapier: Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. - Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. - Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Crashing after the CSV step resumes without appending a duplicate row. Then check: A simulated ambiguous external timeout appears as unknown and stops automatic replay. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. Done when: Crashing after the CSV step resumes without appending a duplicate row. A simulated ambiguous external timeout appears as unknown and stops automatic replay. Do not build yet: Do not start run console and schedules until these checks pass. ### Phase 4 · Run console and schedules Build: Run console and schedules for Zapier: Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. - Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. - Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Restarting after a missed scheduled time runs at most one catch-up according to policy. Then check: A payload secret is absent from the console and logs. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. Done when: Restarting after a missed scheduled time runs at most one catch-up according to policy. A payload secret is absent from the console and logs. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Zapier replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Triggers and contracts; Durable execution; Run console and schedules. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a small code-defined automation runner with durable run history operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - This is a small code-defined automation runner with durable run history; full Zapier feature parity, vendor hosting and support are not included. - integration catalog: retain the paid product if this capability is essential; it is outside this bounded build. - OAuth maintenance: retain the paid product if this capability is essential; it is outside this bounded build. - retries/history: retain the paid product if this capability is essential; it is outside this bounded build. - nontechnical builder: retain the paid product if this capability is essential; it is outside this bounded build. - app triggers/actions: retain the paid product if this capability is essential; it is outside this bounded build. - uptime: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html. Recheck before upgrading; freeze the versions actually tested. ===== AGENTS.md ===== # Agent instructions · Zapier indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Never allow webhook payloads to choose Python module paths or execute code. - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · Zapier Build a small code-defined automation runner with durable run history. Phases are in dependency order. Each ends in a "Done when" list; treat an unticked item as a blocker, not a note. ## Phase 1 · Local foundation and data contract Create the runnable local foundation for a small code-defined automation runner with durable run history, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: pipelines(id,name,trigger,enabled); runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until); steps(id,run_id,step_key,state,result_ref); audit(id,run_id,event,at); pipelines/*.py are trusted owner code. Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## Phase 2 · Triggers and contracts Triggers and contracts for Zapier: Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. ### Steps 1. Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. Files: `features/triggers_and_contracts.py`, `templates/triggers_and_contracts.html` 2. Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. Files: `features/triggers_and_contracts.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: A forged signature returns 401 and creates no run. Then check: Replaying the same event queues one run. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_triggers_and_contracts.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A forged signature returns 401 and creates no run. - [ ] Replaying the same event queues one run. ### Watch out - Never allow webhook payloads to choose Python module paths or execute code. ## Phase 3 · Durable execution Durable execution for Zapier: Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. ### Steps 1. Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. Files: `features/durable_execution.py`, `templates/durable_execution.html` 2. Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. Files: `features/durable_execution.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Crashing after the CSV step resumes without appending a duplicate row. Then check: A simulated ambiguous external timeout appears as unknown and stops automatic replay. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_durable_execution.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Crashing after the CSV step resumes without appending a duplicate row. - [ ] A simulated ambiguous external timeout appears as unknown and stops automatic replay. ### Watch out - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. ## Phase 4 · Run console and schedules Run console and schedules for Zapier: Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. ### Steps 1. Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. Files: `features/run_console_and_schedules.py`, `templates/run_console_and_schedules.html` 2. Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. Files: `features/run_console_and_schedules.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Restarting after a missed scheduled time runs at most one catch-up according to policy. Then check: A payload secret is absent from the console and logs. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_run_console_and_schedules.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Restarting after a missed scheduled time runs at most one catch-up according to policy. - [ ] A payload secret is absent from the console and logs. ### Watch out - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. ## Phase 5 · Portable delivery and clean-start proof Finish the Zapier replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Triggers and contracts; Durable execution; Run console and schedules. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## Not in this build - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - This is a small code-defined automation runner with durable run history; full Zapier feature parity, vendor hosting and support are not included. - integration catalog - OAuth maintenance - retries/history - nontechnical builder - app triggers/actions - uptime ## After v1, if you want it - Extend run console and schedules only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/zapier # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000
You are building a lean indie version of Zapier. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Zapier · indie build Build a small code-defined automation runner with durable run history. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Zapier acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. - Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. - [ ] **Confirm the bounded replacement** · No paid service required for this local step. - Why: The full commercial product is larger than this guide. - Get it: The deliverable is a small code-defined automation runner with durable run history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. - Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` Then copy `.env.example` to `.env` and fill in the values it documents. ## Honest limits This build deliberately does not replace: - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - This is a small code-defined automation runner with durable run history; full Zapier feature parity, vendor hosting and support are not included. - integration catalog - OAuth maintenance - retries/history - nontechnical builder - app triggers/actions - uptime If one of those is essential to you, that is the reason to keep paying for Zapier, and the README should say so rather than pretend. ===== BRIEF.md ===== # Build brief · Zapier The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a small code-defined automation runner with durable run history as a bounded replacement for Zapier. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - pipelines(id,name,trigger,enabled) - runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until) - steps(id,run_id,step_key,state,result_ref) - audit(id,run_id,event,at) - pipelines/*.py are trusted owner code - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: One signed webhook writing a row to a local CSV and one scheduled daily local summary. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Zapier acceptance sample: Create synthetic sample data before implementation: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a small code-defined automation runner with durable run history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a small code-defined automation runner with durable run history, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: pipelines(id,name,trigger,enabled); runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until); steps(id,run_id,step_key,state,result_ref); audit(id,run_id,event,at); pipelines/*.py are trusted owner code. Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start triggers and contracts until these checks pass. ### Phase 2 · Triggers and contracts Build: Triggers and contracts for Zapier: Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. - Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. - Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: A forged signature returns 401 and creates no run. Then check: Replaying the same event queues one run. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Never allow webhook payloads to choose Python module paths or execute code. Done when: A forged signature returns 401 and creates no run. Replaying the same event queues one run. Do not build yet: Do not start durable execution until these checks pass. ### Phase 3 · Durable execution Build: Durable execution for Zapier: Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. - Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. - Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Crashing after the CSV step resumes without appending a duplicate row. Then check: A simulated ambiguous external timeout appears as unknown and stops automatic replay. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. Done when: Crashing after the CSV step resumes without appending a duplicate row. A simulated ambiguous external timeout appears as unknown and stops automatic replay. Do not build yet: Do not start run console and schedules until these checks pass. ### Phase 4 · Run console and schedules Build: Run console and schedules for Zapier: Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. - Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. - Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Restarting after a missed scheduled time runs at most one catch-up according to policy. Then check: A payload secret is absent from the console and logs. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. Done when: Restarting after a missed scheduled time runs at most one catch-up according to policy. A payload secret is absent from the console and logs. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Zapier replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Triggers and contracts; Durable execution; Run console and schedules. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a small code-defined automation runner with durable run history operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - This is a small code-defined automation runner with durable run history; full Zapier feature parity, vendor hosting and support are not included. - integration catalog: retain the paid product if this capability is essential; it is outside this bounded build. - OAuth maintenance: retain the paid product if this capability is essential; it is outside this bounded build. - retries/history: retain the paid product if this capability is essential; it is outside this bounded build. - nontechnical builder: retain the paid product if this capability is essential; it is outside this bounded build. - app triggers/actions: retain the paid product if this capability is essential; it is outside this bounded build. - uptime: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html. Recheck before upgrading; freeze the versions actually tested. ===== AGENTS.md ===== # Agent instructions · Zapier indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Never allow webhook payloads to choose Python module paths or execute code. - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - Export without an import or restore rehearsal is not verified portability. ===== BUILD_PLAN.md ===== # Build plan · Zapier Build a small code-defined automation runner with durable run history. Phases are in dependency order. Each ends in a "Done when" list; treat an unticked item as a blocker, not a note. ## Phase 1 · Local foundation and data contract Create the runnable local foundation for a small code-defined automation runner with durable run history, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: pipelines(id,name,trigger,enabled); runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until); steps(id,run_id,step_key,state,result_ref); audit(id,run_id,event,at); pipelines/*.py are trusted owner code. Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## Phase 2 · Triggers and contracts Triggers and contracts for Zapier: Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. ### Steps 1. Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. Files: `features/triggers_and_contracts.py`, `templates/triggers_and_contracts.html` 2. Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. Files: `features/triggers_and_contracts.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: A forged signature returns 401 and creates no run. Then check: Replaying the same event queues one run. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_triggers_and_contracts.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A forged signature returns 401 and creates no run. - [ ] Replaying the same event queues one run. ### Watch out - Never allow webhook payloads to choose Python module paths or execute code. ## Phase 3 · Durable execution Durable execution for Zapier: Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. ### Steps 1. Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. Files: `features/durable_execution.py`, `templates/durable_execution.html` 2. Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. Files: `features/durable_execution.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Crashing after the CSV step resumes without appending a duplicate row. Then check: A simulated ambiguous external timeout appears as unknown and stops automatic replay. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_durable_execution.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Crashing after the CSV step resumes without appending a duplicate row. - [ ] A simulated ambiguous external timeout appears as unknown and stops automatic replay. ### Watch out - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. ## Phase 4 · Run console and schedules Run console and schedules for Zapier: Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. ### Steps 1. Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. Files: `features/run_console_and_schedules.py`, `templates/run_console_and_schedules.html` 2. Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. Files: `features/run_console_and_schedules.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Restarting after a missed scheduled time runs at most one catch-up according to policy. Then check: A payload secret is absent from the console and logs. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_run_console_and_schedules.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Restarting after a missed scheduled time runs at most one catch-up according to policy. - [ ] A payload secret is absent from the console and logs. ### Watch out - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. ## Phase 5 · Portable delivery and clean-start proof Finish the Zapier replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Triggers and contracts; Durable execution; Run console and schedules. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## Not in this build - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - This is a small code-defined automation runner with durable run history; full Zapier feature parity, vendor hosting and support are not included. - integration catalog - OAuth maintenance - retries/history - nontechnical builder - app triggers/actions - uptime ## After v1, if you want it - Extend run console and schedules only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/zapier # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000
You are building a production product version of Zapier. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Zapier · product brief ## Problem A few personal automations are easy; Zapier's moat is the 9,000+ app integration catalog, auth handling, retries, task history, UI, and reliability. ## Product outcome An operated version of a small code-defined automation runner with durable run history, with authorized access, restore evidence and honest scope limits. ## Target user A builder who needs a maintainable product foundation, not a one-off demo. ## Required capabilities - API keys/OAuth for each service - hosted runner - queue/retry system - logs - secrets storage ## Explicit non-goals for v1 - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - This is a small code-defined automation runner with durable run history; full Zapier feature parity, vendor hosting and support are not included. - integration catalog - OAuth maintenance - retries/history - nontechnical builder - app triggers/actions - uptime ## Success criteria - A forged signature returns 401 and creates no run. - Crashing after the CSV step resumes without appending a duplicate row. - Restarting after a missed scheduled time runs at most one catch-up according to policy. - A private-data authorization check passes using a second identity. - An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - README names the excluded vendor capabilities and actual provider/hosting costs. ===== BRIEF.md ===== # Build brief · Zapier The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a small code-defined automation runner with durable run history as a bounded replacement for Zapier. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - pipelines(id,name,trigger,enabled) - runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until) - steps(id,run_id,step_key,state,result_ref) - audit(id,run_id,event,at) - pipelines/*.py are trusted owner code - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: One signed webhook writing a row to a local CSV and one scheduled daily local summary. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Zapier acceptance sample: Create synthetic sample data before implementation: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a small code-defined automation runner with durable run history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a small code-defined automation runner with durable run history, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: pipelines(id,name,trigger,enabled); runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until); steps(id,run_id,step_key,state,result_ref); audit(id,run_id,event,at); pipelines/*.py are trusted owner code. Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start triggers and contracts until these checks pass. ### Phase 2 · Triggers and contracts Build: Triggers and contracts for Zapier: Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. - Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. - Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: A forged signature returns 401 and creates no run. Then check: Replaying the same event queues one run. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Never allow webhook payloads to choose Python module paths or execute code. Done when: A forged signature returns 401 and creates no run. Replaying the same event queues one run. Do not build yet: Do not start durable execution until these checks pass. ### Phase 3 · Durable execution Build: Durable execution for Zapier: Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. - Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. - Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Crashing after the CSV step resumes without appending a duplicate row. Then check: A simulated ambiguous external timeout appears as unknown and stops automatic replay. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. Done when: Crashing after the CSV step resumes without appending a duplicate row. A simulated ambiguous external timeout appears as unknown and stops automatic replay. Do not build yet: Do not start run console and schedules until these checks pass. ### Phase 4 · Run console and schedules Build: Run console and schedules for Zapier: Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. - Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. - Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Restarting after a missed scheduled time runs at most one catch-up according to policy. Then check: A payload secret is absent from the console and logs. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. Done when: Restarting after a missed scheduled time runs at most one catch-up according to policy. A payload secret is absent from the console and logs. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Zapier replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Triggers and contracts; Durable execution; Run console and schedules. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a small code-defined automation runner with durable run history operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - This is a small code-defined automation runner with durable run history; full Zapier feature parity, vendor hosting and support are not included. - integration catalog: retain the paid product if this capability is essential; it is outside this bounded build. - OAuth maintenance: retain the paid product if this capability is essential; it is outside this bounded build. - retries/history: retain the paid product if this capability is essential; it is outside this bounded build. - nontechnical builder: retain the paid product if this capability is essential; it is outside this bounded build. - app triggers/actions: retain the paid product if this capability is essential; it is outside this bounded build. - uptime: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html. Recheck before upgrading; freeze the versions actually tested. ===== ARCHITECTURE.md ===== # Architecture · Zapier ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | pipelines(id,name,trigger,enabled); runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until); steps(id,run_id,step_key,state,result_ref); audit(id,run_id,event,at); pipelines/*.py are trusted owner code | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Triggers and contracts | Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. | Keep the acceptance contract: A forged signature returns 401 and creates no run. Replace only this module after replaying its fixture; preserve ids and existing records. | | Durable execution | Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. | Keep the acceptance contract: Crashing after the CSV step resumes without appending a duplicate row. Replace only this module after replaying its fixture; preserve ids and existing records. | | Run console and schedules | Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. | Keep the acceptance contract: Restarting after a missed scheduled time runs at most one catch-up according to policy. Replace only this module after replaying its fixture; preserve ids and existing records. | | Operations | Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. | Change host or backup destination only after an isolated restore and authorization check. | ## Configuration Every runtime setting is an environment variable documented in `.env.example`, validated at startup, with a safe local default wherever one exists. - `DATA_DIR` · required · A new private folder this application creates on first run; never serve it as static files. - `SECRET_KEY` · required, secret · Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. - `APP_MODE` · required · Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. - `SITE_URL` · required · The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. ## Production baseline - Security: least privilege, input validation at every boundary, secret redaction in logs, rate limits on abuse-prone paths, no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore procedures that have been exercised. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, timeouts. - Observability: structured logs with request or operation ids, an error-tracking hook, and health and readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, one end-to-end test of the critical path. ## Decision records For each dependency in the stack table, keep a short note: why it was chosen, its failure mode, and how it is replaced. Do not add infrastructure until a requirement in `PRODUCT.md` justifies it. ===== AGENTS.md ===== # Agent instructions · Zapier product build - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. - Implement milestone by milestone from `MILESTONES.md`; keep each change reviewable and leave the application runnable at every commit. - Treat authentication, payments, encryption, imports, webhooks and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a check pass. - Put every external service behind an interface with a deterministic fake for tests. - Add migrations and rollback or recovery notes for every persistent data change. - Log useful operational context without credentials, tokens, passwords or personal data. - Update documentation and run every check before completing a milestone. ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Never allow webhook payloads to choose Python module paths or execute code. - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - Export without an import or restore rehearsal is not verified portability. - Product mode is additional engineering, not a switch that makes a local prototype production-ready. ===== MILESTONES.md ===== # Delivery milestones · Zapier Estimated effort: **multi-day** for the indie phases; the production-only milestones add the trust and operability layer. ## M1 · Local foundation and data contract Create the runnable local foundation for a small code-defined automation runner with durable run history, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: pipelines(id,name,trigger,enabled); runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until); steps(id,run_id,step_key,state,result_ref); audit(id,run_id,event,at); pipelines/*.py are trusted owner code. Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## M2 · Triggers and contracts Triggers and contracts for Zapier: Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. ### Steps 1. Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. Files: `features/triggers_and_contracts.py`, `templates/triggers_and_contracts.html` 2. Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. Files: `features/triggers_and_contracts.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: A forged signature returns 401 and creates no run. Then check: Replaying the same event queues one run. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_triggers_and_contracts.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A forged signature returns 401 and creates no run. - [ ] Replaying the same event queues one run. ### Watch out - Never allow webhook payloads to choose Python module paths or execute code. ## M3 · Durable execution Durable execution for Zapier: Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. ### Steps 1. Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. Files: `features/durable_execution.py`, `templates/durable_execution.html` 2. Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. Files: `features/durable_execution.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Crashing after the CSV step resumes without appending a duplicate row. Then check: A simulated ambiguous external timeout appears as unknown and stops automatic replay. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_durable_execution.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Crashing after the CSV step resumes without appending a duplicate row. - [ ] A simulated ambiguous external timeout appears as unknown and stops automatic replay. ### Watch out - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. ## M4 · Run console and schedules Run console and schedules for Zapier: Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. ### Steps 1. Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. Files: `features/run_console_and_schedules.py`, `templates/run_console_and_schedules.html` 2. Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. Files: `features/run_console_and_schedules.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Restarting after a missed scheduled time runs at most one catch-up according to policy. Then check: A payload secret is absent from the console and logs. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_run_console_and_schedules.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Restarting after a missed scheduled time runs at most one catch-up according to policy. - [ ] A payload secret is absent from the console and logs. ### Watch out - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. ## M5 · Portable delivery and clean-start proof Finish the Zapier replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Triggers and contracts; Durable execution; Run console and schedules. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## M6 · Operate and share with access controls (production only) Product-builder only: make a small code-defined automation runner with durable run history operable for its stated audience before allowing remote access. ### Steps 1. Establish owner access before exposure Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. Files: `ARCHITECTURE.md`, `OPERATIONS.md` 2. Deploy a monitored service Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Files: `Caddyfile`, `OPERATIONS.md` ```sh waitress-serve --listen=127.0.0.1:5000 app:app ``` 3. Rehearse loss and recovery Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. Files: `OPERATIONS.md`, `release-checklist.md` ### Done when - [ ] An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. - [ ] A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. - [ ] Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. ### Watch out - Product mode is additional engineering, not a switch that makes a local prototype production-ready. ===== OPERATIONS.md ===== # Operations · Zapier ## Backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Do a restore drill before the first real user, and write the date here when it passes. ## Monitoring Check HTTP availability, free disk, backup age and domain failures for Triggers and contracts, Durable execution, Run console and schedules. Alert without logging private payloads. ## Incident checklist Pause outbound jobs and public intake as appropriate, preserve redacted diagnostics, restore an isolated verified backup, rotate affected credentials and reconcile uncertain effects before reopening. 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified backup when needed. 5. Document the root cause, the remediation and the regression test. ## Release gate - [ ] A forged signature returns 401 and creates no run. - [ ] Crashing after the CSV step resumes without appending a duplicate row. - [ ] Restarting after a missed scheduled time runs at most one catch-up according to policy. - [ ] A private-data authorization check passes using a second identity. - [ ] An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - [ ] README names the excluded vendor capabilities and actual provider/hosting costs. ## Launch constraint Do not market omitted Zapier capabilities as implemented. The non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered. ===== .env.example ===== # Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/zapier # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000
README.md
# Zapier · indie build Build a small code-defined automation runner with durable run history. Estimated effort: **multi-day**. Work `BUILD_PLAN.md` top to bottom · every phase ends in a check that has to pass before the next one starts. ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Before you start Have every one of these ready. The plan assumes them from step one. - [ ] **Python 3.12 or newer and a terminal** · Python is free; this local prototype requires no hosting subscription. - Why: The local backend, tests and storage use Python. - Get it: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. - Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. - [ ] **A current desktop browser and text editor** · No paid service required for this local step. - Why: You need to view the local interface and edit generated project files. - Get it: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. - Verify: You can create a text file in the project folder and open browser developer tools. - [ ] **Zapier acceptance sample** · No paid service required for this local step. - Why: This fixture makes the first end-to-end check reproducible. - Get it: Create synthetic sample data before implementation: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. - Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. - [ ] **Confirm the bounded replacement** · No paid service required for this local step. - Why: The full commercial product is larger than this guide. - Get it: The deliverable is a small code-defined automation runner with durable run history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. - Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. ## Quick start ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` Then copy `.env.example` to `.env` and fill in the values it documents. ## Honest limits This build deliberately does not replace: - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - This is a small code-defined automation runner with durable run history; full Zapier feature parity, vendor hosting and support are not included. - integration catalog - OAuth maintenance - retries/history - nontechnical builder - app triggers/actions - uptime If one of those is essential to you, that is the reason to keep paying for Zapier, and the README should say so rather than pretend.
BRIEF.md
# Build brief · Zapier The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a small code-defined automation runner with durable run history as a bounded replacement for Zapier. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - pipelines(id,name,trigger,enabled) - runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until) - steps(id,run_id,step_key,state,result_ref) - audit(id,run_id,event,at) - pipelines/*.py are trusted owner code - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: One signed webhook writing a row to a local CSV and one scheduled daily local summary. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Zapier acceptance sample: Create synthetic sample data before implementation: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a small code-defined automation runner with durable run history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a small code-defined automation runner with durable run history, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: pipelines(id,name,trigger,enabled); runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until); steps(id,run_id,step_key,state,result_ref); audit(id,run_id,event,at); pipelines/*.py are trusted owner code. Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start triggers and contracts until these checks pass. ### Phase 2 · Triggers and contracts Build: Triggers and contracts for Zapier: Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. - Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. - Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: A forged signature returns 401 and creates no run. Then check: Replaying the same event queues one run. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Never allow webhook payloads to choose Python module paths or execute code. Done when: A forged signature returns 401 and creates no run. Replaying the same event queues one run. Do not build yet: Do not start durable execution until these checks pass. ### Phase 3 · Durable execution Build: Durable execution for Zapier: Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. - Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. - Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Crashing after the CSV step resumes without appending a duplicate row. Then check: A simulated ambiguous external timeout appears as unknown and stops automatic replay. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. Done when: Crashing after the CSV step resumes without appending a duplicate row. A simulated ambiguous external timeout appears as unknown and stops automatic replay. Do not build yet: Do not start run console and schedules until these checks pass. ### Phase 4 · Run console and schedules Build: Run console and schedules for Zapier: Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. - Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. - Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Restarting after a missed scheduled time runs at most one catch-up according to policy. Then check: A payload secret is absent from the console and logs. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. Done when: Restarting after a missed scheduled time runs at most one catch-up according to policy. A payload secret is absent from the console and logs. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Zapier replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Triggers and contracts; Durable execution; Run console and schedules. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a small code-defined automation runner with durable run history operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - This is a small code-defined automation runner with durable run history; full Zapier feature parity, vendor hosting and support are not included. - integration catalog: retain the paid product if this capability is essential; it is outside this bounded build. - OAuth maintenance: retain the paid product if this capability is essential; it is outside this bounded build. - retries/history: retain the paid product if this capability is essential; it is outside this bounded build. - nontechnical builder: retain the paid product if this capability is essential; it is outside this bounded build. - app triggers/actions: retain the paid product if this capability is essential; it is outside this bounded build. - uptime: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html. Recheck before upgrading; freeze the versions actually tested.
AGENTS.md
# Agent instructions · Zapier indie build - Read `README.md` and `BUILD_PLAN.md` before writing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. Do not substitute. - Work one phase at a time, in order. Do not start a phase until every "Done when" item of the previous one passes. - Prefer the fewest moving parts that satisfy the step. No frameworks, services or dependencies the plan does not name. - Secrets live in `.env`, never in source or logs. Keep `.env.example` current when a variable is introduced. - Do not invent cryptography, security guarantees, APIs or compliance claims. - Add a focused test for every destructive, security-sensitive or data-loss path the plan names. - Run the project checks before declaring a phase complete, and record any deliberate shortcut in the README under "Tradeoffs". ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Never allow webhook payloads to choose Python module paths or execute code. - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - Export without an import or restore rehearsal is not verified portability.
BUILD_PLAN.md
# Build plan · Zapier Build a small code-defined automation runner with durable run history. Phases are in dependency order. Each ends in a "Done when" list; treat an unticked item as a blocker, not a note. ## Phase 1 · Local foundation and data contract Create the runnable local foundation for a small code-defined automation runner with durable run history, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: pipelines(id,name,trigger,enabled); runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until); steps(id,run_id,step_key,state,result_ref); audit(id,run_id,event,at); pipelines/*.py are trusted owner code. Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## Phase 2 · Triggers and contracts Triggers and contracts for Zapier: Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. ### Steps 1. Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. Files: `features/triggers_and_contracts.py`, `templates/triggers_and_contracts.html` 2. Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. Files: `features/triggers_and_contracts.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: A forged signature returns 401 and creates no run. Then check: Replaying the same event queues one run. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_triggers_and_contracts.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A forged signature returns 401 and creates no run. - [ ] Replaying the same event queues one run. ### Watch out - Never allow webhook payloads to choose Python module paths or execute code. ## Phase 3 · Durable execution Durable execution for Zapier: Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. ### Steps 1. Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. Files: `features/durable_execution.py`, `templates/durable_execution.html` 2. Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. Files: `features/durable_execution.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Crashing after the CSV step resumes without appending a duplicate row. Then check: A simulated ambiguous external timeout appears as unknown and stops automatic replay. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_durable_execution.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Crashing after the CSV step resumes without appending a duplicate row. - [ ] A simulated ambiguous external timeout appears as unknown and stops automatic replay. ### Watch out - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. ## Phase 4 · Run console and schedules Run console and schedules for Zapier: Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. ### Steps 1. Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. Files: `features/run_console_and_schedules.py`, `templates/run_console_and_schedules.html` 2. Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. Files: `features/run_console_and_schedules.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Restarting after a missed scheduled time runs at most one catch-up according to policy. Then check: A payload secret is absent from the console and logs. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_run_console_and_schedules.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Restarting after a missed scheduled time runs at most one catch-up according to policy. - [ ] A payload secret is absent from the console and logs. ### Watch out - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. ## Phase 5 · Portable delivery and clean-start proof Finish the Zapier replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Triggers and contracts; Durable execution; Run console and schedules. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## Not in this build - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - This is a small code-defined automation runner with durable run history; full Zapier feature parity, vendor hosting and support are not included. - integration catalog - OAuth maintenance - retries/history - nontechnical builder - app triggers/actions - uptime ## After v1, if you want it - Extend run console and schedules only after the fixture and recovery checks pass. - Before adding another integration, document its credentials, limits, cost and failure behavior with primary-source links.
.env.example
# Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/zapier # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000
PRODUCT.md
# Zapier · product brief ## Problem A few personal automations are easy; Zapier's moat is the 9,000+ app integration catalog, auth handling, retries, task history, UI, and reliability. ## Product outcome An operated version of a small code-defined automation runner with durable run history, with authorized access, restore evidence and honest scope limits. ## Target user A builder who needs a maintainable product foundation, not a one-off demo. ## Required capabilities - API keys/OAuth for each service - hosted runner - queue/retry system - logs - secrets storage ## Explicit non-goals for v1 - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - This is a small code-defined automation runner with durable run history; full Zapier feature parity, vendor hosting and support are not included. - integration catalog - OAuth maintenance - retries/history - nontechnical builder - app triggers/actions - uptime ## Success criteria - A forged signature returns 401 and creates no run. - Crashing after the CSV step resumes without appending a duplicate row. - Restarting after a missed scheduled time runs at most one catch-up according to policy. - A private-data authorization check passes using a second identity. - An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - README names the excluded vendor capabilities and actual provider/hosting costs.
BRIEF.md
# Build brief · Zapier The one-shot brief this plan expands. `BUILD_PLAN.md` (or `MILESTONES.md`) is the same sequence broken into steps and checks; where the two disagree, the plan wins. Build me a small code-defined automation runner with durable run history as a bounded replacement for Zapier. Build it in phases in the order below. Do not write the whole product in one pass. Finish the current phase, run its Done when checks, fix failures, then continue. Indie mode completes Phases 1-5. Phase 6 is required before shared or public deployment. ### Stack (fixed, do not substitute) - Runtime: Python 3.12+ and Flask. A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. - Storage: SQLite through Python sqlite3. Local ownership with explicit transactions and a portable backup path. - Interface: Jinja HTML templates, CSS and vanilla JavaScript. Implement the specified screens directly with labelled controls and progressive enhancement. - Verification: Python unittest and browser acceptance fixtures. Check invariants and the actual user workflow before the next phase. ### Data model (create this before Phase 1) - pipelines(id,name,trigger,enabled) - runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until) - steps(id,run_id,step_key,state,result_ref) - audit(id,run_id,event,at) - pipelines/*.py are trusted owner code - Use stable ids and explicit relationships; add auxiliary tables named by the phases before those phases use them. - Acceptance fixture: One signed webhook writing a row to a local CSV and one scheduled daily local summary. ### Prerequisites and configuration - Python 3.12 or newer and a terminal: Install Python from python.org. Open a terminal in a new empty project folder. On Windows, use py -3 where this guide says python if python is not on PATH; on macOS/Linux use python3 if needed. Create .venv and activate it before installing packages. Verify: python --version reports 3.12+ and python -c "import sqlite3" succeeds. Cost: Python is free; this local prototype requires no hosting subscription. - A current desktop browser and text editor: Use an installed Chrome, Firefox or Edge browser. Open the empty project folder in your editor; open the terminal there, not in this catalog repository. Verify: You can create a text file in the project folder and open browser developer tools. Cost: No paid service required for this local step. - Zapier acceptance sample: Create synthetic sample data before implementation: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Save it under fixtures/ with the expected results in fixtures/README.md; use no real credentials or customer records. Verify: The fixture files and expected outcomes exist and can be inspected without a vendor account. Cost: No paid service required for this local step. - Confirm the bounded replacement: The deliverable is a small code-defined automation runner with durable run history. Read every exclusion below. Indie mode runs locally; any public or shared use requires the product access and deployment gates first. Verify: You can name the primary workflow and the vendor features this version deliberately leaves out. Cost: No paid service required for this local step. - Configuration: DATA_DIR, SECRET_KEY, APP_MODE, SITE_URL. Ship .env.example, replace placeholders and exclude secrets from git. ### Phase 1 · Local foundation and data contract Build: Create the runnable local foundation for a small code-defined automation runner with durable run history, including the real schema and acceptance fixture. - Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Commands, after creating the named files: `python -m venv .venv`; `python -m pip install Flask Flask-WTF python-dotenv waitress tzdata`; `python -m pip freeze > requirements.txt`; `python -m flask --app app run --host 127.0.0.1`. - For database-backed state create schema.sql and db.py using this model: pipelines(id,name,trigger,enabled); runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until); steps(id,run_id,step_key,state,result_ref); audit(id,run_id,event,at); pipelines/*.py are trusted owner code. Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Re-running init must not erase data. Commands, after creating the named files: `python manage.py init`; `python manage.py seed`. - Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. - Trap: The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. Done when: The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. Restarting preserves the seeded records or canonical files; running init again deletes nothing. A cross-origin state-changing request to an admin route is refused. Do not build yet: Do not start triggers and contracts until these checks pass. ### Phase 2 · Triggers and contracts Build: Triggers and contracts for Zapier: Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. - Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. - Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: A forged signature returns 401 and creates no run. Then check: Replaying the same event queues one run. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Never allow webhook payloads to choose Python module paths or execute code. Done when: A forged signature returns 401 and creates no run. Replaying the same event queues one run. Do not build yet: Do not start durable execution until these checks pass. ### Phase 3 · Durable execution Build: Durable execution for Zapier: Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. - Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. - Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Crashing after the CSV step resumes without appending a duplicate row. Then check: A simulated ambiguous external timeout appears as unknown and stops automatic replay. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. Done when: Crashing after the CSV step resumes without appending a duplicate row. A simulated ambiguous external timeout appears as unknown and stops automatic replay. Do not build yet: Do not start run console and schedules until these checks pass. ### Phase 4 · Run console and schedules Build: Run console and schedules for Zapier: Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. - Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. - Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. - Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Restarting after a missed scheduled time runs at most one catch-up according to policy. Then check: A payload secret is absent from the console and logs. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Commands, after creating the named files: `python -m unittest discover -s test`. - Trap: OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. Done when: Restarting after a missed scheduled time runs at most one catch-up according to policy. A payload secret is absent from the console and logs. Do not build yet: Do not start portable delivery and clean-start proof until these checks pass. ### Phase 5 · Portable delivery and clean-start proof Build: Finish the Zapier replacement with a documented first-run path and a recoverable export. - Document prerequisites, every configuration variable, data locations and the three domain workflows: Triggers and contracts; Durable execution; Run console and schedules. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. - Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. - Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Commands, after creating the named files: `python -m pip install -r requirements.txt`; `python -m unittest discover -s test`. - Trap: Export without an import or restore rehearsal is not verified portability. Done when: A new folder reaches the documented fixture outcome using only README instructions. A backup restored in isolation preserves the proof data and can be opened. Do not build yet: Do not start operate and share with access controls until these checks pass. ### Phase 6 · Operate and share with access controls (product-builder only) Build: Product-builder only: make a small code-defined automation runner with durable run history operable for its stated audience before allowing remote access. - Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. - Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Commands, after creating the named files: `waitress-serve --listen=127.0.0.1:5000 app:app`. - Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. - Trap: Product mode is additional engineering, not a switch that makes a local prototype production-ready. Done when: An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. Do not build yet: Do not add new providers or vendor-scale features until the release gates are recorded. ### Out of scope (and why) - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - This is a small code-defined automation runner with durable run history; full Zapier feature parity, vendor hosting and support are not included. - integration catalog: retain the paid product if this capability is essential; it is outside this bounded build. - OAuth maintenance: retain the paid product if this capability is essential; it is outside this bounded build. - retries/history: retain the paid product if this capability is essential; it is outside this bounded build. - nontechnical builder: retain the paid product if this capability is essential; it is outside this bounded build. - app triggers/actions: retain the paid product if this capability is essential; it is outside this bounded build. - uptime: retain the paid product if this capability is essential; it is outside this bounded build. ### README must contain - Exact install, configure, initialize, start, test and recovery commands for a clean folder. - The schema, fixture, acceptance results, private data locations and export format. - Every prerequisite and secret source, actual running costs and deliberately excluded capabilities. - An honest distinction between tests actually run and checks still awaiting real credentials or deployment. - Dependency documentation reviewed 2026-09-05: https://flask.palletsprojects.com/en/stable/installation/ ; https://docs.python.org/3/library/sqlite3.html ; https://flask-wtf.readthedocs.io/en/1.2.x/csrf/ ; https://docs.pylonsproject.org/projects/waitress/en/stable/usage.html. Recheck before upgrading; freeze the versions actually tested.
ARCHITECTURE.md
# Architecture · Zapier ## Stack | Part | Choice | Why | | --- | --- | --- | | Runtime | Python 3.12+ and Flask | A small local HTTP application with readable server-side handlers and no JavaScript build pipeline. | | Storage | SQLite through Python sqlite3 | Local ownership with explicit transactions and a portable backup path. | | Interface | Jinja HTML templates, CSS and vanilla JavaScript | Implement the specified screens directly with labelled controls and progressive enhancement. | | Verification | Python unittest and browser acceptance fixtures | Check invariants and the actual user workflow before the next phase. | ## Modules Each module has one owner concern and a documented way to replace it. | Module | Owns | How to replace it | | --- | --- | --- | | Data and identity | pipelines(id,name,trigger,enabled); runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until); steps(id,run_id,step_key,state,result_ref); audit(id,run_id,event,at); pipelines/*.py are trusted owner code | Keep stable ids and a versioned repository interface; migrate storage behind it with a fixture round-trip. | | Triggers and contracts | Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. | Keep the acceptance contract: A forged signature returns 401 and creates no run. Replace only this module after replaying its fixture; preserve ids and existing records. | | Durable execution | Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. | Keep the acceptance contract: Crashing after the CSV step resumes without appending a duplicate row. Replace only this module after replaying its fixture; preserve ids and existing records. | | Run console and schedules | Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. | Keep the acceptance contract: Restarting after a missed scheduled time runs at most one catch-up according to policy. Replace only this module after replaying its fixture; preserve ids and existing records. | | Operations | Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. | Change host or backup destination only after an isolated restore and authorization check. | ## Configuration Every runtime setting is an environment variable documented in `.env.example`, validated at startup, with a safe local default wherever one exists. - `DATA_DIR` · required · A new private folder this application creates on first run; never serve it as static files. - `SECRET_KEY` · required, secret · Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. - `APP_MODE` · required · Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. - `SITE_URL` · required · The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. ## Production baseline - Security: least privilege, input validation at every boundary, secret redaction in logs, rate limits on abuse-prone paths, no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore procedures that have been exercised. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, timeouts. - Observability: structured logs with request or operation ids, an error-tracking hook, and health and readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, one end-to-end test of the critical path. ## Decision records For each dependency in the stack table, keep a short note: why it was chosen, its failure mode, and how it is replaced. Do not add infrastructure until a requirement in `PRODUCT.md` justifies it.
AGENTS.md
# Agent instructions · Zapier product build - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. The stack is fixed: Python 3.12+ and Flask, SQLite through Python sqlite3, Jinja HTML templates, CSS and vanilla JavaScript, Python unittest and browser acceptance fixtures. - Implement milestone by milestone from `MILESTONES.md`; keep each change reviewable and leave the application runnable at every commit. - Treat authentication, payments, encryption, imports, webhooks and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a check pass. - Put every external service behind an interface with a deterministic fake for tests. - Add migrations and rollback or recovery notes for every persistent data change. - Log useful operational context without credentials, tokens, passwords or personal data. - Update documentation and run every check before completing a milestone. ## Known traps - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. - Never allow webhook payloads to choose Python module paths or execute code. - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. - Export without an import or restore rehearsal is not verified portability. - Product mode is additional engineering, not a switch that makes a local prototype production-ready.
MILESTONES.md
# Delivery milestones · Zapier Estimated effort: **multi-day** for the indie phases; the production-only milestones add the trust and operability layer. ## M1 · Local foundation and data contract Create the runnable local foundation for a small code-defined automation runner with durable run history, including the real schema and acceptance fixture. ### Steps 1. Create and start the local application Run the venv command first, then stop and activate it before running the remaining commands. Use your OS instructions: Windows .venv\Scripts\activate.bat in cmd, or .venv\Scripts\Activate.ps1 in PowerShell; macOS/Linux source .venv/bin/activate. Then install the listed packages. Create app.py exposing app, load .env with python-dotenv, and add a /healthz route. Freeze tested dependency versions to requirements.txt. Create .env manually from .env.example; replace SECRET_KEY before launch. Files: `app.py`, `requirements.txt`, `.env.example`, `.gitignore` ```sh python -m venv .venv python -m pip install Flask Flask-WTF python-dotenv waitress tzdata python -m pip freeze > requirements.txt python -m flask --app app run --host 127.0.0.1 ``` 2. Implement storage and seed the named fixture For database-backed state create schema.sql and db.py using this model: pipelines(id,name,trigger,enabled); runs(id,pipeline_id,event_key,state,attempts,next_attempt_at,lease_until); steps(id,run_id,step_key,state,result_ref); audit(id,run_id,event,at); pipelines/*.py are trusted owner code. Add the auxiliary relationships explicitly used in later phases; use stable ids, foreign keys, parameterized values and transactions. For canonical files use atomic replacement and hashes instead. Implement python manage.py init and python manage.py seed to create only synthetic data: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Re-running init must not erase data. Files: `schema.sql`, `db.py`, `manage.py`, `fixtures/README.md` ```sh python manage.py init python manage.py seed ``` 3. Protect the local request boundary Install Flask-WTF CSRF protection for forms and same-origin fetches, validate Host and Origin against SITE_URL, bound inputs and escape output. Deliberately public intake endpoints get bounded validation and rate limits; signed provider webhooks use signature checks instead of browser CSRF tokens. All other admin routes stay local until product authentication exists. When a later phase tests viewer/member permissions, implement the users, hashed passwords, expiring server sessions and role checks in this foundation first; product mode must never use a fabricated identity from request input. Add error, empty, keyboard-focus and retry states now. Files: `app.py`, `templates/base.html`, `test/test_foundation.py` ### Done when - [ ] The documented start command serves /healthz and the initial screen at http://127.0.0.1:5000. - [ ] Restarting preserves the seeded records or canonical files; running init again deletes nothing. - [ ] A cross-origin state-changing request to an admin route is refused. ### Watch out - The Flask development server is for local development only. Loopback binding alone does not replace CSRF and origin validation. ## M2 · Triggers and contracts Triggers and contracts for Zapier: Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. ### Steps 1. Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. Load only owner-written pipeline modules from a fixed directory; accept bounded webhook JSON with HMAC signature and timestamp checks. Files: `features/triggers_and_contracts.py`, `templates/triggers_and_contracts.html` 2. Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. Persist a unique pipeline/event key before queueing and provide a manual dry-run with a fake clock and local output. Files: `features/triggers_and_contracts.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: A forged signature returns 401 and creates no run. Then check: Replaying the same event queues one run. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_triggers_and_contracts.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] A forged signature returns 401 and creates no run. - [ ] Replaying the same event queues one run. ### Watch out - Never allow webhook payloads to choose Python module paths or execute code. ## M3 · Durable execution Durable execution for Zapier: Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. ### Steps 1. Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. Implement a worker lease and per-step idempotency keys; retry only failures that are known safe with bounded backoff. Files: `features/durable_execution.py`, `templates/durable_execution.html` 2. Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. Mark timed-out external effects as unknown and require reconciliation instead of claiming an automatic retry is harmless. Files: `features/durable_execution.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Crashing after the CSV step resumes without appending a duplicate row. Then check: A simulated ambiguous external timeout appears as unknown and stops automatic replay. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_durable_execution.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Crashing after the CSV step resumes without appending a duplicate row. - [ ] A simulated ambiguous external timeout appears as unknown and stops automatic replay. ### Watch out - Marking a run complete before the action loses work; marking it after does not alone prevent duplicates. ## M4 · Run console and schedules Run console and schedules for Zapier: Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. ### Steps 1. Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. Show redacted history, attempts and step results; require a reason when rerunning and retain the original event identity. Files: `features/run_console_and_schedules.py`, `templates/run_console_and_schedules.html` 2. Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. Use UTC due instants plus an explicit missed-run policy; write owner notifications to a local inbox in v1. Files: `features/run_console_and_schedules.py` 3. Exercise the acceptance fixture Use One signed webhook writing a row to a local CSV and one scheduled daily local summary. Check: Restarting after a missed scheduled time runs at most one catch-up according to policy. Then check: A payload secret is absent from the console and logs. Add a focused regression for the failure case under test/ using a temporary database or folder and fake external services; also perform the visible workflow in a browser. Files: `test/test_run_console_and_schedules.py` ```sh python -m unittest discover -s test ``` ### Done when - [ ] Restarting after a missed scheduled time runs at most one catch-up according to policy. - [ ] A payload secret is absent from the console and logs. ### Watch out - OAuth connectors, visual editing and arbitrary hosted integrations remain outside this two-pipeline runner. ## M5 · Portable delivery and clean-start proof Finish the Zapier replacement with a documented first-run path and a recoverable export. ### Steps 1. Write the user-facing runbook Document prerequisites, every configuration variable, data locations and the three domain workflows: Triggers and contracts; Durable execution; Run console and schedules. Include the exclusions, actual costs and source check date 2026-09-05. Commands shown earlier that reference project files are files the builder must implement before running them. Files: `README.md`, `.env.example` 2. Create and rehearse a recoverable backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Files: `OPERATIONS.md`, `scripts/backup.py` 3. Reproduce the first-run experience Use a new folder and only README instructions to reach the fixture outcome. Install from requirements.txt, initialize storage, run the tests and exercise the UI at 375px and 1280px; use keyboard-only controls and inspect browser errors. Record exactly what passed; do not mark unrun checks complete. Files: `README.md`, `verification.md` ```sh python -m pip install -r requirements.txt python -m unittest discover -s test ``` ### Done when - [ ] A new folder reaches the documented fixture outcome using only README instructions. - [ ] A backup restored in isolation preserves the proof data and can be opened. ### Watch out - Export without an import or restore rehearsal is not verified portability. ## M6 · Operate and share with access controls (production only) Product-builder only: make a small code-defined automation runner with durable run history operable for its stated audience before allowing remote access. ### Steps 1. Establish owner access before exposure Add owner/member/viewer authorization as appropriate, password hashes through Werkzeug, expiring server-side sessions, CSRF and login rate limits. Add users, sessions and audit schema migrations plus an owner-init command prompting securely for its password. Enforce ownership on every private read/write/download and fail closed when product setup is incomplete. Existing learner or admin identities must use this same boundary. Files: `ARCHITECTURE.md`, `OPERATIONS.md` 2. Deploy a monitored service Serve app:app with Waitress on loopback behind Caddy HTTPS. Configure trusted proxy headers narrowly, Secure/HttpOnly/SameSite cookies, upload limits, request ids and structured logs without private content. Run background jobs as a separate supervised process when the domain workflow requires them. Files: `Caddyfile`, `OPERATIONS.md` ```sh waitress-serve --listen=127.0.0.1:5000 app:app ``` 3. Rehearse loss and recovery Add a scheduled encrypted off-host backup using this procedure: Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. Monitor health, disk space, failed jobs and backup age. Stop the service to test an alert; rehearse recovery with outbound effects disabled and record recovery time. Rotate any exposed credentials and require reconciliation before resuming queues. Files: `OPERATIONS.md`, `release-checklist.md` ### Done when - [ ] An unauthenticated visitor cannot read private records, download private files or mutate the admin surface. - [ ] A viewer cannot mutate data by making a direct request, and guessed ids cannot cross ownership boundaries. - [ ] Stopping the service triggers the configured alert and the latest off-host backup restores the fixture in isolation. ### Watch out - Product mode is additional engineering, not a switch that makes a local prototype production-ready.
OPERATIONS.md
# Operations · Zapier ## Backup Use sqlite3.Connection.backup for the database in DATA_DIR and pause writers while taking the matching attachment snapshot. Keep schema version, hashes and a manifest for zapier. ## Restore Restore into a separate empty directory or isolated deployment, with all outbound actions and schedules disabled. Recreate this proof: One signed webhook writing a row to a local CSV and one scheduled daily local summary. Compare ids/counts and open the result before recording the restore date. Never test a restore over the only live copy. Do a restore drill before the first real user, and write the date here when it passes. ## Monitoring Check HTTP availability, free disk, backup age and domain failures for Triggers and contracts, Durable execution, Run console and schedules. Alert without logging private payloads. ## Incident checklist Pause outbound jobs and public intake as appropriate, preserve redacted diagnostics, restore an isolated verified backup, rotate affected credentials and reconcile uncertain effects before reopening. 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified backup when needed. 5. Document the root cause, the remediation and the regression test. ## Release gate - [ ] A forged signature returns 401 and creates no run. - [ ] Crashing after the CSV step resumes without appending a duplicate row. - [ ] Restarting after a missed scheduled time runs at most one catch-up according to policy. - [ ] A private-data authorization check passes using a second identity. - [ ] An off-host restore drill has a date, observed result and recovery time in OPERATIONS.md. - [ ] README names the excluded vendor capabilities and actual provider/hosting costs. ## Launch constraint Do not market omitted Zapier capabilities as implemented. The non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
.env.example
# Copy to .env and fill in. Never commit .env; this file documents it. # Required. A new private folder this application creates on first run; never serve it as static files. DATA_DIR=./data/zapier # Required · secret. Generate with python -c "import secrets; print(secrets.token_hex(32))" and save only in .env. SECRET_KEY=replace-with-a-random-secret # Required. Use indie for loopback-only personal work. Product mode must refuse to start until owner login and the deployment gates are configured. APP_MODE=indie # Required. The origin used for local forms and links; replace with the chosen HTTPS origin in product mode. SITE_URL=http://127.0.0.1:5000
$ choose a build depth, inspect the files, then open the complete pack in your agent
They pay because every new app connection is already packaged and maintained.
xintegration catalog
xOAuth maintenance
xretries/history
xnontechnical builder
xapp triggers/actions
xuptime
share on X ↗"I just replaced Zapier ($29.99/mo) with one prompt"
Don't feel like building it? These folks already made it free.
Activepieces Community EditionZapier with a Docker bill and no task meter.open source↗
AutomatischA smaller AGPL Zapier clone for ordinary trigger-action flows.open source↗
n8n Community EditionThe standard self-hosted answer: broad, durable, and fair-code rather than open source.free↗all 3 free alternatives to Zapier →· no votes, no pay-to-list · just what's real
Zapier pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| free | $0/workspace | $0/workspace | 100 tasks/month; unlimited Zaps, Tables and Forms; 2-step Zaps; 1 seat; 15-minute polling; 2,500 table records/account. |
| professional | $29.99/workspace | $19.99/workspace | Starts at 750 tasks/month; 1 seat; multi-step Zaps; premium apps; 2-minute polling; 100,000 table records/account. |
| team | $103.50/workspace | $69/workspace | Starts at 2,000 tasks/month; up to 25 users; 1-minute polling; 500,000 table records/account. |
| enterprise | custom | — | Custom annual task allowance; unlimited users; enterprise administration and security. |
free tier100 tasks/month, 2-step Zaps, 1 seat, 15-minute polling, 2,500 table records/account, 3 views/table, 10 form pages and 5 MB maximum form upload
billingmonthly + annual; annual prices are effective monthly rates and plans scale by task volume
hidden costsPay-per-task overage is enabled by default on eligible paid plans. Some newer units cost multiple tasks: MCP calls use 2, Lead Router steps 5, AI actions can use 1/3/5 by model tier, and extended code uses 1 task per 30 seconds. Agents and Chatbots are separate products or add-ons.
verified 2026-08-11 · source ↗
Vibecode Zapier
Kinda. The core of Zapier is buildable in a weekend with the prompt on this page, but there are real gaps: integration catalog, OAuth maintenance. Read the honest list above before committing.
How much does Zapier cost?
Zapier costs about $29.99/month (Professional/Starter, checked 2026-07-30), which is $359.88 per year.
What do I lose by replacing Zapier?
Honestly: integration catalog; OAuth maintenance; retries/history; nontechnical builder; app triggers/actions; uptime. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Zapier?
Yes: Activepieces Community Edition (Zapier with a Docker bill and no task meter.) Automatisch (A smaller AGPL Zapier clone for ordinary trigger-action flows.) n8n Community Edition (The standard self-hosted answer: broad, durable, and fair-code rather than open source.) All 3 curated free alternatives are at vibecodeit.com/zapier/alternatives. The prompt is for when you want it exactly your way.