Individual skill

automation-flows

Use when building or fixing a no-code automation on n8n, Make, or Zapier — trigger to multi-app steps with data mapping, dedup, retries and an error path — or picking the platform by billing unit (task vs credit vs execution). NOT a typed API client in code (that is api-connector-builder), NOT a webhook receiver in your own app (that is webhooks).

skills/automation-flows/SKILL.md

Read pinned source

Source commit d9d6bb338f66cc1e23998585e580a0ea45bbcb82

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: No
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 560
Repository last updated: Nov 4, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-skills Repository topic
agentic-ai Repository topic
ai-agents Repository topic
ai-coding Repository topic
claude-code Repository topic
cli Repository topic
cline Repository topic
codex Repository topic
coding-assistant Repository topic
cursor Repository topic
automation Declared skill tag
n8n Declared skill tag
make Declared skill tag
zapier Declared skill tag
no-code Declared skill tag
workflows Declared skill tag
error-handling Declared skill tag
integrations Declared skill tag
data Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 11,563 bytes
SKILL.mdcore · 11,563 bytes
SKILL.mdcore · 11,563 bytes
SKILL.mdcore · 11,563 bytes
SKILL.mdcore · 11,563 bytes
SKILL.mdcore · 11,563 bytes
SKILL.mdcore · 11,563 bytes
evals/README.mddoc · 1,180 bytes
evals/cases.yamlasset · 3,352 bytes
references/error-handling.mddoc · 4,460 bytes
references/n8n-workflow-json.mddoc · 3,199 bytes
scripts/verify.shruns · 2,270 bytes

Read excerpt


# Automation flows — glue many SaaS apps on a visual platform, with an error path that actually fires

You are building a working automation on a hosted visual platform: a trigger, a chain of app actions with branching and explicit data mapping, and an error-handling and retry strategy without which the flow is not done.

Your job is two things at once: **platform judgement** (pick n8n vs Make vs Zapier by the constraints) and a **buildable artifact** (an importable n8n workflow JSON, or a precise numbered build sheet for Make/Zapier, which have no portable export).

This skill stops the moment the right answer is real code. Writing a typed API client → `../api-connector-builder/SKILL.md`. Building the endpoint that *receives* a webhook in your own app → `../webhooks/SKILL.md`. Scripting one vendor directly → `../stripe/SKILL.md`, `../notion-connector/SKILL.md`, `../google-workspace/SKILL.md`, `../whatsapp-telegram/SKILL.md`.

## 1. Pick the platform

The single most expensive mistake is choosing on familiarity instead of cost model. The three platforms bill on fundamentally different units, and at volume that gap is 10×.

| Constraint | Zapier | Make | n8n |
| --- | --- | --- | --- |