@awesomate/hosting-mcp 0.109.0 → 0.126.0

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

@@ -16,8 +16,10 @@ decision has to name one.
                                                                      └ else → stop, or tell the customer "we'll be in touch"
 ```
 
-1. **Hold for a decision.** Until the Awesomate node has its own "Hold for a decision" operation, use an
-   HTTP Request node with the account's **Awesomate Hub** credential (it is already on the instance):
+1. **Hold for a decision.** Use the Awesomate node's **Task: Hold for a Decision** (`holdForDecision`; see
+   [awesomate-node.md](awesomate-node.md)): it reads the run's own resume address and id. Where their
+   node does not have it yet (check its Operation list), use an HTTP Request node with the account's
+   **Awesomate Hub** credential (check `hubNodeCredential` in `awesomate_n8n_context`: when it is missing, add it with `awesomate_n8n_hub_credential` (or the owner presses "Add it to my n8n" on the hub); when their n8n has no Awesomate node, use Generic Credential Type, Header Auth, **Awesomate Hub Key**, if the credential inventory has it):
 
    - `POST https://hub.awesomate.ai/api/hub-key/v2/<account>/decisions`
    - JSON body:

package/skill/awesomate-n8n/references/staff-alerts.md

@@ -44,10 +44,12 @@ at most five urgent tasks in a day; the sixth goes as an ordinary task, and the
 (`urgent: false` with a `note`). Urgent wears off a day after the task is given. People switch chats off when they are
 woken for nothing, so most alerts are ordinary tasks.
 
-Until the Awesomate node has an Urgent field, give an urgent task with an HTTP Request node:
+Give an urgent task with the Awesomate node's **Task: Give**, Additional Fields, **Urgent** on (see
+[awesomate-node.md](awesomate-node.md)). Where their node does not have the Urgent field yet (check the
+Give step's Additional Fields), use an HTTP Request node:
 
 - Method `POST`, URL `https://hub.awesomate.ai/api/hub-key/v1/<account>/tasks/tasks`
-- Authentication: Predefined Credential Type, **Awesomate Hub** (it is already on the instance)
+- Authentication: Predefined Credential Type, **Awesomate Hub** (check `hubNodeCredential` in `awesomate_n8n_context`: when it is missing, add it with `awesomate_n8n_hub_credential` (or the owner presses "Add it to my n8n" on the hub); when their n8n has no Awesomate node, use Generic Credential Type, Header Auth, **Awesomate Hub Key**, if the credential inventory has it)
 - Header `X-Awesomate-Workflow`: `{{ $workflow.id }}`, so the task says an automation gave it
 - JSON body: