8.9 KiB
Automation Platforms — Global Fix Map
🏥 Quick Return to Emergency Room
You are in a specialist desk.
For full triage and doctors on duty, return here:
- WFGY Global Fix Map — main Emergency Room, 300+ structured fixes
- WFGY Problem Map 1.0 — 16 reproducible failure modes
Think of this page as a sub-room.
If you want full consultation and prescriptions, go back to the Emergency Room lobby.
Stabilize automations across Zapier, n8n, Make, Retool, Power Automate, and more.
Most “platform bugs” are not bugs at all — they are ordering, retries, dedupe, or time drift. This hub routes you to exact structural fixes with measurable acceptance targets.
Orientation: pick your tool
| Platform | What it is | Typical use | Link |
|---|---|---|---|
| Zapier | Mainstream no-code automation | Broad connectors, fast start | zapier.md |
| n8n | Open-source workflow engine | Self-hosted, extensible | n8n.md |
| Make (Integromat) | Visual workflow builder | SMB and RAG pipelines | make.md |
| Retool | Internal-tool builder + workflows | Backoffice jobs, cron | retool.md |
| IFTTT | Consumer-grade triggers | Personal automations | ifttt.md |
| Pipedream | Event platform + code steps | Webhooks, SaaS APIs | pipedream.md |
| Power Automate | Microsoft ecosystem automation | O365, SharePoint, Dynamics | power-automate.md |
| GitHub Actions | CI/CD + repo event runner | Build, test, deploy | github-actions.md |
| Airflow | Code-first workflow scheduler | Data/ETL DAGs | airflow.md |
| Airtable Automations | Table-driven automations | CRUD triggers | airtable.md |
| Asana Rules | Project management rules | PM events to actions | asana.md |
| GoHighLevel (GHL) | CRM automation platform | Marketing + sales flows | ghl.md |
| Parabola | Dataflow-based automation | Transform + schedule | parabola.md |
| LangChain (automation mode) | Agent orchestration | LLM-based workflows | langchain.md |
| LlamaIndex (automation mode) | Knowledge orchestration | RAG pipelines | llamaindex.md |
Common failure classes
-
Bootstrap race conditions
Trigger fires before vector/index is ready.
→ bootstrap-ordering.md -
Deployment deadlocks
Infinite waits between worker, retriever, or webhook callbacks.
→ deployment-deadlock.md -
Pre-deploy collapse
Wrong version triggered on first call after shipping.
→ predeploy-collapse.md -
Embedding vs semantic drift
High similarity but wrong meaning.
→ embedding-vs-semantic.md -
Traceability breaks
Citations do not match the source.
→ retrieval-traceability.md, data-contracts.md
Minimal contract for any workflow
- Check readiness
VerifyVECTOR_READYandINDEX_HASHbefore RAG/LLM calls. - Idempotency
Always compute a dedupe key and block duplicates. - Boundary contract
Require{snippet_id, section_id, source_url, offsets, tokens}. - Observability
Log ΔS and λ across steps, alert if ΔS ≥ 0.60.
FAQ for newcomers
Why does my Zap/Flow run twice?
Because triggers are at-least-once. Add idempotency keys to dedupe.
Why did my webhook return 200 but no data was processed?
You acknowledged before persisting. Always store → then process.
Why do my cron jobs drift?
Local timezone drift. Always store schedules in UTC.
Why do retries overload my API?
You used immediate retries. Add exponential backoff with jitter.
Why does everything work in dev but break in prod?
Because of boot order. Index not warmed, wrong analyzer, or cache empty.
🔗 Quick-Start Downloads
| Tool | Link | 3-Step Setup |
|---|---|---|
| WFGY 1.0 PDF | Engine Paper | 1) Download · 2) Upload to LLM · 3) Ask “Use WFGY to fix my automation bug” |
| TXT OS | TXTOS.txt | 1) Download · 2) Paste into LLM · 3) Type “hello world” |
Explore More
| Module | Description | Link |
|---|---|---|
| WFGY Core | Canonical framework entry point | View |
| Problem Map | Diagnostic map and navigation hub | View |
| Tension Universe Experiments | MVP experiment field | View |
| Recognition | Where WFGY is referenced or adopted | View |
| AI Guide | Anti-hallucination reading protocol for tools | View |
If this repository helps, starring it improves discovery for other builders.
