Repository navigation
graphx v0.7.0 — it runs itself, and runs anywhere
graphx crosses from "a tool you operate" to "automation that runs itself" — and any workflow is now portable to any machine.
✨ New in v0.7.0
Triggers — workflows that run themselves
triggers:
- { type: schedule, cron: "0 7 * * *" } # daily at 7am
- { type: interval, every: 15m } # every 15 minutes
- { type: webhook, path: "orders", input_from: body } # POST /hooks/orders → body = inputgraphx serveis now a daemon — an async scheduler fires schedule/interval triggers,POST /hooks/{path}runs a workflow with the request body as input, andGET /scheduleslists everything with next-fire times.- Or hand it to the OS —
graphx schedule wf.yaml --cron "0 7 * * *" --installwrites + enables a systemd user timer (cron →OnCalendar), or--crontabprints a crontab line. No daemon needed for schedule-only jobs.
Export — runs on any machine
graphx export myflow.yaml --docker → a self-contained folder: the workflow + a bundled graphx wheel + requirements.txt (auto-detected [mcp]/[postgres]/[s3] extras) + .env.example (secret names only) + run.py + optional Dockerfile. Installs graphx offline from the wheel, deps from PyPI, credentials from your .env. Verified: runs to completion in a clean venv with no graphx present.
From v0.6
Pregel engine (loops, checkpointing, resume) · natural-language builder (both engines) + point-at-any-endpoint · 12 node types · resilience · secret:// credentials that never leak · 12 connectors · discovery · OpenAPI scaffolding · Textual TUI · FastAPI + SSE.
250 tests, ruff-clean, Python 3.12+.
Install
pip install -e ".[tui,mcp,server]"
graphx tui