A build prompt for an n8n or Make automation workflow — and the small app around it — with webhooks, schedules, integrations and proper error handling.
Built for: Small businesses, agencies and ops teams that want to automate repetitive work
Automations usually start small and break silently: an API changes, a webhook arrives twice, a step stops halfway. A robust workflow designs the trigger, idempotency, retry rules and failure alerts from the start.
With the Automation Engineer persona the prompt defines every flow step by step: trigger → transform → destination, secrets, a dead-letter queue, monitoring and a small panel to manage the flows.
Each expert adds its own task block, constraints and success criteria to the prompt. Default selection for Automation Workflow (n8n):
Build the automation layer: n8n / Make workflows (trigger → steps → output), webhook contracts, idempotency keys, error / retry and dead-letter rules, secrets handling. Define the MCP tools and integrations the app exposes (Slack, Notion, Google Sheets, email), and add monitoring and alerts for every flow.
Design the multi-agent system: agent roles and responsibilities, orchestrator / sub-agent layout, agent files (CLAUDE.md, AGENTS.md, .claude/agents), short- and long-term memory, tools and MCP servers, schedules and triggers, steps that need human approval, a 'watchdog' agent that audits the others, a token/cost budget and an eval set.
Design the system architecture. Edge-first, 100ms p95. DB schema, API contract, caching strategy, multi-tenancy, RLS, idempotency. Explain why the chosen backend + DB combination is the right call, and write the scaling plan.
Event tracking plan: North Star and supporting metrics, event/property dictionary, funnel and retention definitions, data warehouse schema, dashboard list, data quality tests.
Preloaded in step 2 of the Studio; change any of the 7 layers.
Every feature appears in the prompt as a "Spec + API + UI + Tests" line.
Sample idea: "An n8n automation that connects e-commerce orders to accounting, shipping and customer email". Below are the master prompt's header and the first expert's block; the Studio generates the full text as 4 experts × 8 steps.
# Automation Workflow (n8n) - MASTER BUILD PROMPT Stack: Hono + CF Workers Goal: An n8n automation that connects e-commerce orders to accounting, shipping and customer email This prompt builds a full-stack n8n Automation in 8 steps. Each step consumes the previous step's output. 4 experts' knowledge combined. Steps: 1. PRD & User Stories 2. Design System (Figma tokens) 3. DB Schema & API Contract 4. Auth & Billing Implementation 5. Core Features Build 6. AI Integration (RAG + Agents) 7. SEO/AEO & Analytics 8. Launch & Growth Checklist --- <prompt> <role name="Automation Engineer" org="n8n & Make Power User" specialty="Workflows & Integrations" experience="8y"> You are an Automation Engineer with 8 years of experience. Specialty: Workflows & Integrations. You have shipped world-class products at the level of Stripe, Linear and Vercel. </role> <context> Project: Automation Workflow (n8n) - An n8n automation that connects e-commerce orders to accounting, shipping and customer email Type: n8n Automation Vision: A new-order webhook arrives; the invoice is posted to the accounting software, a shipping label is created, the customer gets a tracking email and stock is updated in Google Sheets. Failed steps are retried, unresolved ones land in Slack, and a small panel shows the run history. Target user: Small businesses, agencies and ops teams that want to automate repetitive work - Pain: - Budget: Competitors: USP: Monetization: Subscription (MRR), Usage-Based | Payments: Stripe Tech Stack: Hono + CF Workers, Supabase, Claude Sonnet 5, Resend, n8n (self-hosted) Features: Workflow Builder, Scheduled Jobs & Triggers, Webhooks & Events, Integrations (Slack/Notion/Sheets), Human-in-the-loop Approvals, Notifications Center, Audit Logs Compliance: KVKK/GDPR Lang: EN </context> <task> Build the automation layer: n8n / Make workflows (trigger → steps → output), webhook contracts, idempotency keys, error / retry and dead-letter rules, secrets handling. Define the MCP tools and integrations the app exposes (Slack, Notion, Google Sheets, email), and add monitoring and alerts for every flow. General: production quality, copy-paste ready level of detail. </task> <technical_architecture> - Frontend: - App Router, Server Components, partial prerendering - Backend: Hono + CF Workers - Edge runtime, RPC, zod validation - DB: Supabase - pgvector for semantic search, type-safe ORM, RLS policies - Auth: - Passkeys first, org/team model - Search: - typo-tolerant, faceted - Realtime: Resend | n8n (self-hosted) - presence, CRDT-ready …
The prompt recommends self-hosted n8n if you want to keep data on your own server and Make for a quick start; flow definitions are written so they work in either tool.
An idempotency key per event and a processed-events log are hard constraints; a duplicate event is skipped and logged.
Claude Code, Cursor, Windsurf, v0, Lovable, Bolt and ChatGPT. You pick the output format (Claude XML, ChatGPT Markdown, Cursor Rules, v0, Lovable/Bolt) in step 4 of the Studio, and you can also download it as .cursorrules or CLAUDE.md.
Yes. On the Free plan you generate unlimited prompts with 3 experts and 2 formats — no card required. 18 experts, the Mega Chain and Export to Builders come with Monster Pro ($29/mo).
A build prompt that gets Claude Code or Cursor to set up an autonomous multi-agent system with memory, MCP tools, schedules and human approval steps.
A build prompt for a conversion-focused landing page or a personal portfolio, with copy, design, animation, SEO and form flows.
A build prompt for an iOS and Android app with Expo / React Native: push notifications, offline mode, in-app purchases and app store optimization.
A build prompt for an internal tool or admin panel with role-based permissions, bulk actions, an audit log and reporting.
A build prompt that gets Claude Code, Cursor or v0 to ship a multi-tenant SaaS dashboard in one go: auth, RBAC, billing, analytics and ⌘K search included.
A build prompt for an LLM-powered SaaS (chat, RAG, agents) with credit quotas, streaming and cost control. Claude, GPT, Gemini, Groq and vector DB picks included.
Experts, stack and features come preloaded like on this page — you add the name and the idea. Free, no card required.