@awesomate/hosting-mcp 0.19.0 → 0.19.1

package/dist/index.js

@@ -39906,6 +39906,10 @@ async function hubRequest(config3, method, path, jsonBody, opts = {}) {
       hint = " Payment/allowance required \u2014 NOTHING was purchased. State the cost plainly and let the user decide in the hub; this tool never spends money.";
     } else if (res.status === 404) {
       hint = " Not found \u2014 usually the resource does not exist for THIS account. Re-check the id/domain before retrying; do not invent one.";
+    } else if (code === "n8n_credential_invalid") {
+      const settingsUrl = body && typeof body === "object" && typeof body.settingsUrl === "string" ? body.settingsUrl : "https://hub.awesomate.ai/n8n/settings";
+      const instanceUrl = body && typeof body === "object" && typeof body.instanceUrl === "string" ? body.instanceUrl : null;
+      hint = ` THIS IS NOT A HUB OUTAGE and not your workflow \u2014 the user's own n8n rejected the API key Awesomate has stored. Tell the user to fix it in two steps: (1) in their n8n${instanceUrl ? ` at ${instanceUrl}` : ""}, open Settings \u2192 n8n API and create a new API key; (2) paste it into their Awesomate account at ${settingsUrl} under "New n8n API Key" and save. Then retry. Do not retry before they confirm, and do not investigate hub/Cloudflare status \u2014 reads and validation keep working because those never touch their instance.`;
     } else if (res.status === 409) {
       hint = " Conflict \u2014 the payload carries the specifics (a limit reached, or a prerequisite missing). Read its code field; do not blind-retry.";
     } else if (res.status === 422) {
@@ -39915,7 +39919,8 @@ async function hubRequest(config3, method, path, jsonBody, opts = {}) {
     } else if (res.status === 503) {
       hint = " The hub is temporarily unable to serve this \u2014 retry shortly.";
     }
-    throw new HubApiError(`${serverMsg}.${hint}`, res.status, body);
+    const stem = /[.!?]$/.test(serverMsg) ? serverMsg : `${serverMsg}.`;
+    throw new HubApiError(`${stem}${hint}`, res.status, body);
   }
   return body;
 }
@@ -40677,7 +40682,7 @@ server.registerTool(
   "awesomate_n8n_deploy",
   {
     annotations: DESTRUCTIVE,
-    description: "Workflow lifecycle writes on the client's n8n, all consent-gated and audited server-side. Actions: 'validate' (structural + n8n-mcp check of workflowJson \u2014 ALWAYS validate before create_draft), 'create_draft' (creates an INACTIVE '[CLI] ' workflow tagged awm:client-cli; returns its webhook URLs), 'activate'/'deactivate' (activation strips the [CLI] prefix; production webhooks respond only while active; agency-managed workflows are refused), 'promote' (swaps a TESTED draft into the live workflow IN PLACE \u2014 live id + webhookIds preserved so external callers keep working; pass workflowId=the LIVE id and draftId=the tested draft; the draft is archived '[promoted <date>]'; response includes operationId for rollback), 'rollback' (restore a promote's pre-swap state \u2014 pass operationId), 'update_draft' (replace an INACTIVE self-built draft's full JSON in place \u2014 pass workflowId + workflowJson; live workflows are refused, use the promote path), 'delete_draft' (inactive self-built drafts only). Get explicit user approval before activate, promote, rollback, and delete_draft. 429 quota_exceeded = daily plan limit; 403 consent_required \u2192 send user to settingsUrl.",
+    description: "Workflow lifecycle writes on the client's n8n, all consent-gated and audited server-side. Actions: 'validate' (structural + n8n-mcp check of workflowJson \u2014 ALWAYS validate before create_draft), 'create_draft' (creates an INACTIVE '[CLI] ' workflow tagged awm:client-cli; returns its webhook URLs), 'activate'/'deactivate' (activation strips the [CLI] prefix; production webhooks respond only while active; agency-managed workflows are refused), 'promote' (swaps a TESTED draft into the live workflow IN PLACE \u2014 live id + webhookIds preserved so external callers keep working; pass workflowId=the LIVE id and draftId=the tested draft; the draft is archived '[promoted <date>]'; response includes operationId for rollback), 'rollback' (restore a promote's pre-swap state \u2014 pass operationId), 'update_draft' (replace an INACTIVE self-built draft's full JSON in place \u2014 pass workflowId + workflowJson; live workflows are refused, use the promote path), 'delete_draft' (inactive self-built drafts only). Get explicit user approval before activate, promote, rollback, and delete_draft. 429 quota_exceeded = daily plan limit; 403 consent_required \u2192 send user to settingsUrl; 409 n8n_credential_invalid = the user's OWN n8n rejected the stored API key (NOT a hub outage \u2014 reads and validate keep working because they never touch their instance): tell them to create a new API key in their n8n under Settings \u2192 n8n API, paste it into their Awesomate account at hub.awesomate.ai/n8n/settings, then retry.",
     inputSchema: {
       action: external_exports.enum(["validate", "create_draft", "update_draft", "activate", "deactivate", "promote", "rollback", "delete_draft"]),
       workflowJson: external_exports.record(external_exports.unknown()).optional().describe("For validate: the full workflow JSON. For create_draft: must contain name, nodes, connections (settings optional)."),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.19.0",
+  "version": "0.19.1",
   "description": "Awesomate MCP server — lets Claude manage your Awesomate WordPress hosting, plan, limits, n8n automations, and build Node/static apps + databases",
   "license": "UNLICENSED",
   "type": "module",

package/skill/CHANGELOG.json

@@ -1,5 +1,11 @@
 {
   "versions": [
+    {
+      "version": "0.19.1",
+      "highlights": [
+        "When your n8n API key stops working, Claude now tells you exactly how to fix it instead of reporting a confusing server error"
+      ]
+    },
     {
       "version": "0.19.0",
       "highlights": [
@@ -14,13 +20,13 @@
       "highlights": [
         "Search your knowledge base with filters and ask questions within a slice of your content",
         "People & entities: your knowledge base now recognises who appears in your content, and you can name and merge them",
-        "Build AI agents from your own content — drafted, tested privately, and published only when you approve"
+        "Build AI agents from your own content \u2014 drafted, tested privately, and published only when you approve"
       ]
     },
     {
       "version": "0.14.0",
       "highlights": [
-        "Tools built for business owners, not developers — plain-language answers about your account, plan and limits",
+        "Tools built for business owners, not developers \u2014 plain-language answers about your account, plan and limits",
         "New support skill: get help, understand credits, or request a done-for-you build without leaving Claude",
         "New database skill: Claude picks the right place to keep your data and sets it up for you"
       ]

package/skill/awesomate-n8n/references/troubleshooting.md

@@ -3,6 +3,34 @@
 Diagnosis playbook. Work the flow top-to-bottom; do not jump to fixes before
 you have the failing execution's detail.
 
+
+## "Could not create the draft" / writes fail while reads work
+
+If reads, `awesomate_n8n_context` and `validate` all succeed but every WRITE
+(create draft, activate, promote, test-fire) fails, the cause is almost always
+the account's stored n8n API key — not the hub, not Cloudflare, not the
+workflow JSON. Validation runs on Awesomate's side and never touches the
+instance, which is exactly why it keeps passing.
+
+The server says so explicitly: HTTP **409** with `code: n8n_credential_invalid`.
+Older builds reported this as a 502, which reads like an outage — if you see a
+bare 502 on writes only, suspect the key before you suspect the platform.
+
+**Tell the user to do this, in this order:**
+
+1. Open their n8n (the response's `instanceUrl`, e.g. `https://<slug>.awesomate.io`)
+   → **Settings → n8n API** → **Create an API key**. Copy it.
+2. Open **https://hub.awesomate.ai/n8n/settings** → paste it into
+   **"New n8n API Key"** → save. The status chip should go from
+   *Key rejected* to *Connected*.
+3. Retry the action.
+
+Do not retry before they confirm the new key is saved, and do not go probing
+hub or Cloudflare status — a genuine hub problem breaks reads too.
+
+Common causes: the key was revoked or regenerated in n8n, or the instance was
+rebuilt (a rebuilt instance shows 0 workflows and invalidates every old key).
+
 ## Diagnosis flow
 
 1. `awesomate_n8n_context` — confirm consent flags, capabilities, and the