@awesomate/hosting-mcp 0.109.0 → 0.125.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -44,10 +44,12 @@ at most five urgent tasks in a day; the sixth goes as an ordinary task, and the
44
44
  (`urgent: false` with a `note`). Urgent wears off a day after the task is given. People switch chats off when they are
45
45
  woken for nothing, so most alerts are ordinary tasks.
46
46
 
47
- Until the Awesomate node has an Urgent field, give an urgent task with an HTTP Request node:
47
+ Give an urgent task with the Awesomate node's **Task: Give**, Additional Fields, **Urgent** on (see
48
+ [awesomate-node.md](awesomate-node.md)). Where their node does not have the Urgent field yet (check the
49
+ Give step's Additional Fields), use an HTTP Request node:
48
50
 
49
51
  - Method `POST`, URL `https://hub.awesomate.ai/api/hub-key/v1/<account>/tasks/tasks`
50
- - Authentication: Predefined Credential Type, **Awesomate Hub** (it is already on the instance)
52
+ - 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)
51
53
  - Header `X-Awesomate-Workflow`: `{{ $workflow.id }}`, so the task says an automation gave it
52
54
  - JSON body:
53
55