Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
DeepSeek
Muse+22 moreClaude CodeCursorCodex CLIDeepSeekMuse
Dots
Manus
Grok
Grok Bot+18 agentsn8n/Make Workflow Builder Debugger
Design, debug, and convert production-ready automation workflows for n8n and Make.
$20
n8n/Make Workflow Builder Debugger
Example session with this skill installed
My n8n workflow is failing at the HTTP Request node. It says '400 Bad Request' but the JSON looks right to me. I'm trying to send data to the Stripe API. How do I fix this?
- Read your context and instructions
- Compiled the n8n make workflow
I will diagnose the Stripe API 400 error in your n8n workflow.
Debug Report: Stripe HTTP Request Failure
Symptom: HTTP Request node returns a 400 Bad Request during a POST to Stripe.
Ranked Hypotheses:
1.
Data Type Mismatch: Stripe expects application/x-www-form-urlencoded for most endpoints, but n8n defaults to JSON for body content.
2. Missing Required Field: A mandatory parameter (like amount or currency) is missing from the mapped input.
3.
Integer vs String: Amounts in Stripe must be integers (in cents); sending "10.00" as a string or float will trigger a 400.
Recommended Fix:
- Open the HTTP Request node.
- Change Authentication to
Header AuthorSecret(ensureBearer {{YOUR_KEY}}). - Set Body Content Type to
Form-Dataorn8n-nodes-base.httpRequestequivalent for URL-encoded. - Ensure the amount expression uses
Math.round()to send an integer:
// Example expression for a $10.00 charge
{{ Math.round($json.amount * 100) }}
Verification Table:
| Case | Input | Expected Result | How to Verify |
|---|---|---|---|
| Valid Charge | amount: 10.00 | 200 OK | Check Stripe Dashboard for $10.00 payment |
| Missing Amount | amount: null | 400 Error | Node should catch error via Error Trigger |
| Zero Amount | amount: 0 | 400 Error | Confirm Stripe error message: 'amount must be > 0' |
Next steps:
Check your "Body Content Type" setting in the failing node. If it is set to JSON, switch to Form-Data and re-test.
Connects securely to your tools. The creator never sees your data.
About this skill
Build, debug and harden n8n and Make automations in minutes, not hours.
Stop losing time to broken automations. This skill turns your AI agent into a senior automation engineer for n8n and Make (Integromat).
Describe what you want to automate, or paste a failing workflow with its error. The skill follows a fixed process: spec first, evidence before fixes, and a test plan every time.
Make: guided builds, not one-click blueprints. For Make, you get step-by-step module guides with mapping, filters, routers and error handlers that you build in your own account. For n8n, simple to medium flows can come as importable JSON.
What you can do with it
Build: turn a business goal into a workflow spec, a node-by-node (n8n) or module-by-module (Make) build guide, and a test plan. Debug: get a classified root cause (auth, data shape, mapping, rate limit, timing, config, platform), an exact fix, verification steps and prevention tips. Review: score a workflow against a production-readiness checklist and get findings by severity. Convert: move a workflow between Make and n8n with a concept mapping and a list of gaps. Explain: get a plain-language walkthrough and data-flow table for any workflow.
Why it is different
Evidence before fixes: a fixed debugging protocol instead of random suggestions. Honest about uncertainty: unknown parameters are flagged ⚠ VERIFY, never invented. Production mindset: error handling, idempotency, retries and rate limits are part of every build. Secret-safe: it never asks for API keys and works with placeholders. Platform-aware: it respects real differences between n8n items and Make bundles, error handling and cost models.
What’s included
SKILL.md: the main skill README.md with installation and quick-start prompts EXAMPLES.md with 5 worked examples (build, debug ×2, review, convert) n8n and Make cheatsheets Error catalog (symptom → cause → fix) for both platforms Production hardening checklist n8n ↔ Make translation guide Templates: workflow spec, debug report, and an importable n8n global error-handler workflow
Good to know
Attach your own credentials after importing any n8n JSON. The skill cannot access your n8n or Make account. It gives you verification steps to run yourself. Works with agents that support the SKILL.md format (e.g. Claude Code). Screenshots show illustrative sample outputs, not live n8n or Make captures. n8n and Make are trademarks of their respective owners. This product is independent and not affiliated with them.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Workflow Automation.
Cannot execute workflows or access live platform accounts. Hand-written Make blueprints are fragile; step-by-step guides are the default for Make. Requires manual credential attachment.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 1 month ago