🔧 How to Ask for Help (Rules & Best Practices) 1) 🔎 Check Existing ResourcesSearch the community, n8n docs, and forums first—your issue might already be solved. 2) 🏷️ Title Your Post ClearlyUse specific, descriptive titles and the right category (e.g., “Support Needed”).Example: “Webhook not triggering on form submit” > “Help please!” 3) 🎥 Include Screenshots or a LoomVisuals are critical. Without them, the first reply will be “Can you share a screenshot?”—which slows things down. 4) 💬 Reply or @Mention DirectlyUse “Reply” or tag people with ‎`@username` to notify them when you respond. 5) ✅ Mark as [SOLVED]When resolved, update your title with [SOLVED] so others can find working solutions quickly. 6) 👍 Like Helpful ResponsesIf someone helps you, give their reply a like. It shows appreciation and strengthens the community. 📋 Recommended Post Format - Context: What you’re building and the end goal - Stack: Tools involved (e.g., n8n, GPT‑4o, Google Sheets, APIs) - What You Tried: Steps, nodes, logs/errors - Minimal Repro: Small screenshot or snippet showing the issue - Desired Output: Example payload/result you expect Let’s keep help requests clear, visual, and solution‑focused. The more context you share, the faster you’ll get useful answers. 🚀