@awesomate/hosting-mcp 0.99.0 → 0.125.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@awesomate/hosting-mcp",
-  "version": "0.99.0",
+  "version": "0.125.0",
   "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,163 @@
 {
   "versions": [
+    {
+      "version": "0.125.0",
+      "highlights": [
+        "A new KPI has no light until its first figure is due: Claude says when it is due and what brings the figure, never that it is late; a KPI's trend holds up to 12 periods, from when it was added"
+      ]
+    },
+    {
+      "version": "0.124.0",
+      "highlights": [
+        "Claude writes only the fields of a kind or a company that AI may read (awesomate_crm_write, awesomate_crm_companies and recipes): any other, a sensitive one included, is answered as if it did not exist, as for contacts"
+      ]
+    },
+    {
+      "version": "0.123.0",
+      "highlights": [
+        "New awesomate_crm_lists: Claude can make an email list with the owner (its two kinds, and words that stay fixed once anyone agrees), rename, archive and restore one, and see who is on it",
+        "Claude can bring a list in from Ontraport, Mailchimp, ActiveCampaign or a spreadsheet: it reads the export on this computer and prepares the import, and an Owner checks it and presses Import in the hub from a link (and a task). Nobody goes on a list or gets an email until they do"
+      ]
+    },
+    {
+      "version": "0.122.0",
+      "highlights": [
+        "Claude builds n8n workflows with the Awesomate node (awesomate-n8n skill, references/awesomate-node.md): Contact (create or update, get, search, update, tags, stop emailing, record event), Record (your own record types), Task (urgent, hold for a decision), with every parameter name, what an AI agent may not do with it, and an HTTP Request fallback for an n8n without the newest node",
+        "n8n calls the hub only on /api/hub-key/v1/...: the reference puts the right and wrong addresses side by side, because /api/my-crm/v1 answers 401 to the Hub Key",
+        "A new help page, The Awesomate node, at hub.awesomate.ai/docs/mcp/guides/awesomate-node/ (the node's credential links to it)"
+      ]
+    },
+    {
+      "version": "0.120.0",
+      "highlights": [
+        "Defining a kind and adding, renaming or archiving its links are an Owner's, as in the hub: a team member's own key is refused with owner_only. A team member's key may still add a field, but only an Owner's makes it readable by AI"
+      ]
+    },
+    {
+      "version": "0.118.0",
+      "highlights": [
+        "Claude can add figures for the business's KPIs (awesomate_business_map 'add_figures'): totals per day, week or month, from the user's own tools or what they say, into their Your numbers, where a KPI reads them"
+      ]
+    },
+    {
+      "version": "0.117.0",
+      "highlights": [
+        "The email skill says what to do when someone asks to stop by reply, phone or in person (record it with awesomate_crm_contacts unsubscribe, within 5 business days), and that a request to delete someone's details is an erasure an Owner finishes in the hub"
+      ]
+    },
+    {
+      "version": "0.116.0",
+      "highlights": [
+        "Claude knows whether the Awesomate node's \"Awesomate Hub\" credential is in your n8n (awesomate_n8n_context hubNodeCredential), and adds it with awesomate_n8n_hub_credential from the account owner's own Claude Code, so nobody opens n8n or copies a key"
+      ]
+    },
+    {
+      "version": "0.115.0",
+      "highlights": [
+        "Claude can prepare an erasure when someone asks for their details to be deleted: what would go and what stays, and the hub link where an Owner finishes it (awesomate_crm_contacts erase). Claude never erases anyone."
+      ]
+    },
+    {
+      "version": "0.114.0",
+      "highlights": [
+        "Claude can give a task to a role on the business map (awesomate_tasks add with role): everyone in the role sees it until one of them takes it, and a role with nobody in it goes to the owner"
+      ]
+    },
+    {
+      "version": "0.113.0",
+      "highlights": [
+        "Claude reads the business's KPIs (awesomate_business_map 'kpis'): each one's light, its figure against the target, the period so far, a 12-period trend, where its figure comes from and what a late one needs, only those the person may see",
+        "Claude can suggest showing a KPI to everyone who signs in (kpi.share), for the owner to accept"
+      ]
+    },
+    {
+      "version": "0.111.0",
+      "highlights": [
+        "Claude can suggest KPIs for the business map (kpi.add, kpi.update, kpi.archive): a number with a target and someone responsible, kept in the hub where the account has KPIs on its map"
+      ]
+    },
+    {
+      "version": "0.109.0",
+      "highlights": [
+        "Claude reads when a decision on a role is within its limits, so anyone in the role can answer it and the first answer decides it"
+      ]
+    },
+    {
+      "version": "0.108.0",
+      "highlights": [
+        "Claude can say when a role's task goes to the person responsible for the role if nobody takes it (4 business hours), and that it did when nobody took it"
+      ]
+    },
+    {
+      "version": "0.107.0",
+      "highlights": [
+        "Claude can take a task given to a role on the business map for the owner, when the owner is in that role, and sees who has taken a role's task"
+      ]
+    },
+    {
+      "version": "0.106.0",
+      "highlights": [
+        "Claude reads the map's one suggested next step, which roles are ready to hand over (every process written down or automated) and the one line worth a look on each role, such as an automation that failed this week"
+      ]
+    },
+    {
+      "version": "0.105.0",
+      "highlights": [
+        "Claude can link a role's process to the 1Brain page that writes it down and the agent or automation that does it, when it suggests a change to that role's responsibilities, and reads how many processes are written down and automated"
+      ]
+    },
+    {
+      "version": "0.104.0",
+      "highlights": [
+        "When a customer writes to your support inbox asking to stop getting emails, Claude sees it on the ticket and offers to record it on their page (you have 5 business days)"
+      ]
+    },
+    {
+      "version": "0.103.0",
+      "highlights": [
+        "Claude can see what points at a record (awesomate_crm_rows related): a customer's jobs, a job's notes, with how many and the newest, read as it reads them"
+      ]
+    },
+    {
+      "version": "0.102.0",
+      "highlights": [
+        "Claude can keep a table in step with another system (awesomate_crm_write sync): it writes each record by that system's id, such as a Xero invoice number, so running the copy again changes the record instead of adding a second one",
+        "A record you archived stays archived: a sync never brings it back or makes a second copy"
+      ]
+    },
+    {
+      "version": "0.101.3",
+      "highlights": [
+        "Claude knows your sub-departments by the names you give them and in your order, never by a number, and can suggest renaming, adding, reordering or removing one for you to accept in Tasks (where the new business map is on your account)"
+      ]
+    },
+    {
+      "version": "0.101.2",
+      "highlights": [
+        "Email series work during a trial on Support Plus and above: instead of an upgrade prompt, the series page shows the sending steps still to do, next one first, and Claude walks you through them"
+      ]
+    },
+    {
+      "version": "0.101.1",
+      "highlights": [
+        "Contacts answers use your business's time zone from Your business when Claude doesn't name one, so 'today' and 'this week' match your clock, not Sydney's"
+      ]
+    },
+    {
+      "version": "0.101.0",
+      "highlights": [
+        "When someone asks you to stop emailing them, by reply, phone, in person or in writing, Claude can record it (awesomate_crm_contacts unsubscribe): every email, booking confirmations included, or just one list",
+        "It's recorded as the person's own request, at the time they asked, so a later import can't put them back on the list"
+      ]
+    },
+    {
+      "version": "0.100.0",
+      "highlights": [
+        "Claude can mark a task urgent when you say it can't wait (a hot lead, a fault, a staff alert): it reaches the person's chats straight away, and in their quiet hours only the chat they chose to be woken in",
+        "Tasks Claude gives now reach people's chats within the quiet hours, order and daily limit each person sets in Tasks, Your places. Emails still come straight away",
+        "Building an n8n automation that tells someone on your team about a hot lead or a fault? Claude now uses a task, which reaches their chats, instead of an email or a text"
+      ]
+    },
     {
       "version": "0.99.0",
       "highlights": [

package/skill/awesomate-database/SKILL.md

@@ -18,6 +18,10 @@ Do not provision anything until you know which of these four the ask is.
 One question usually settles it: "is this for an automation to read and
 write, or for an app your customers log into?"
 
+**People are not one of the four:** the people a workflow meets (leads, enquiries, customers) go in **Contacts** with
+the Awesomate node (Contact: Create or Update) wherever `features.contacts` is on; see the awesomate-n8n
+skill's `awesomate-node.md`. Data tables are for the workflow's own working data.
+
 **(a) A list an AUTOMATION reads/writes** — a dedupe ledger, a task
 queue, a lookup map, form submissions feeding a workflow. → n8n DATA
 TABLE, via the awesomate-n8n skill. The table lives in n8n: Claude designs

package/skill/awesomate-email/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: awesomate-email
-description: Be the business's email expert. Plan which mailing lists to start with, keep every send legal under Australian and New Zealand spam law, write emails that sound like the owner, draft them in Awesomate's Contacts & email for the owner to approve in the hub, use groups built from what the business knows, protect deliverability, read results honestly, ask past customers to opt in the right way, and move a list off Mailchimp, ActiveCampaign or Ontraport. Use this whenever the user mentions email marketing, a newsletter, an e-blast, a mailing list, subscribers, a campaign, "email my customers", "send to my database", "send to everyone", segments or groups, unsubscribes, open or click rates, emails landing in spam, Mailchimp, ActiveCampaign, Ontraport or Klaviyo, Contacts & email in the hub, re-engaging old customers, getting people to opt in, or "write an email to my clients", even if they never say "email marketing".
+description: Be the business's email expert. Plan which mailing lists to start with, keep every send legal under Australian and New Zealand spam law, write emails that sound like the owner, draft them in Awesomate's Contacts & email for the owner to approve in the hub, use groups built from what the business knows, protect deliverability, read results honestly, ask past customers to opt in the right way, and move a list off Mailchimp, ActiveCampaign or Ontraport. Use this whenever the user mentions email marketing, a newsletter, an e-blast, a mailing list, subscribers, a campaign, "email my customers", "send to my database", "send to everyone", segments or groups, unsubscribes, someone who rang or replied asking to stop getting emails, a request to delete a customer's details, open or click rates, emails landing in spam, Mailchimp, ActiveCampaign, Ontraport or Klaviyo, Contacts & email in the hub, re-engaging old customers, getting people to opt in, or "write an email to my clients", even if they never say "email marketing".
 ---
 
 # Awesomate Email: be the business's email expert
@@ -37,8 +37,8 @@ its promise (the words people agreed to), how often it sends, whether it's a
 customers list, how many people it would reach right now, and how many are
 left out and why. Counts only, never names. No lists, or lists with nobody to
 email yet, usually means the owner hasn't added lists or imported people:
-plan them together (section 2) and point the owner to
-https://hub.awesomate.ai/contacts.
+plan them together (section 2), then make them with `awesomate_crm_lists`
+or point the owner to https://hub.awesomate.ai/contacts.
 
 Work without it when:
 
@@ -105,17 +105,29 @@ and why. Add three to five starter groups. Let the owner change any of it.
 Full method and starter sets for trades, studios, retail, health, property,
 finance, coaching and hospitality: `references/list-planning.md`.
 
-In Awesomate the owner creates lists, not you: at
-https://hub.awesomate.ai/contacts (Add a list), or when they import. There
-are two kinds:
-
-- An **opt-in list** records the exact words people agreed to.
-- A **customers list** is for customers they work with regularly, about
-  work they do for them, with no offers. People reach it when the owner
-  says, while importing, that everyone with a given tag is that kind of
-  customer. That statement is recorded with their name and the time.
-
-Give the owner each list's name and promise wording, ready to paste.
+In Awesomate you can make the lists with `awesomate_crm_lists
+{action:'create', name, promise, kind}` once the owner has said yes to
+the wording (the owner can also add them at https://hub.awesomate.ai/contacts).
+There are two kinds, and a list's kind never changes:
+
+- An **opt-in list** (`kind: 'opt_in'`) records the exact words people
+  agreed to: its promise.
+- A **customers list** (`kind: 'customers'`) is for customers they work
+  with regularly, about work they do for them, with no offers. People reach
+  it when the owner says, while reviewing an import, that everyone with a
+  given tag is that kind of customer. That statement is recorded with their
+  name and the time.
+
+The wording rules:
+
+- Write the promise with the owner and show it to them word for word before
+  you make the list. Say what they'll get and how often, in their voice.
+- Once anyone has agreed to a promise it can't be changed (the tool answers
+  `promise_locked`): people agreed to those words. Make a new list instead.
+- You can rename a list, change how often it sends, archive it and restore
+  it (Support Plus and above). Archiving changes nobody's consent.
+- A new list is empty. You never put anyone on a list: people join by
+  agreeing on a form, or through an import the owner commits.
 
 ## 3. Who gets it
 
@@ -250,6 +262,34 @@ email. Each approved email goes to its whole list, so on a new sending
 address, start with the smallest and most engaged list and widen over a
 couple of weeks.
 
+**Someone who asks to stop by reply, phone or in person has unsubscribed
+too,** and the law gives the business 5 business days to act on it. Record
+it as soon as you know: find them with `awesomate_crm_contacts
+{action:'search', text}`, then `awesomate_crm_contacts {action:'unsubscribe',
+id, how}` (how: `reply`, `phone`, `in_person`, `in_writing` or `other`;
+`asked_at` when they asked, if it wasn't just now, as an ISO date and time
+with its offset, like `2026-10-14T09:30:00+10:00`; a `list` key from `get`
+to stop one list only). With no list it stops every email, booking
+confirmations and other service emails included, so ask which they meant
+when it isn't clear. Repeating it is harmless (`changed: false`). Changing
+contacts needs Support Plus and above: on Essentials, send the owner to the
+person's page in the hub (Contacts, People, then the person: **Stop
+emailing**); if their account has no such button yet, they ask Awesomate
+support to record it, within the 5 days. When `awesomate_support_desk read`
+shows `asks_to_stop_email`, a customer asked by reply: offer to record it
+with the ticket's `contact_id`, and do it on the owner's yes. When
+`contact_id` is null they are not on the list: never add them to Contacts to
+unsubscribe them; send the owner to the banner on that ticket in the hub.
+
+**A request to delete someone's details is an erasure, not an
+unsubscribe.** `awesomate_crm_contacts {action:'erase', id}` only prepares
+it: it says what would go and what stays, and gives `finish_in_hub`, a link
+where an Owner of the business finishes it in the hub by typing the
+person's email address (or ERASE when they have none). It can't be undone,
+and no key can do it, so tell the owner what goes and hand them the link.
+When `finish_in_hub` is null, it can't be finished in the hub on that
+account yet: pass on the note it gives, and never make up a link.
+
 ## 7. Read the results honestly
 
 Delivered first, then how many people clicked, replied, booked or bought,
@@ -280,6 +320,21 @@ such as the invoice number) so sending it twice records it once. For events
 that should flow by themselves, an n8n workflow posts the same thing to
 `POST /api/my-crm/v1/events` with the account's key.
 
+Series work on Support Plus and above, **trials included**. Never tell a
+trial owner to upgrade for a series. What a new account usually lacks is
+sending set up, and the hub's series pages show the steps in order. When
+the owner asks why their series won't go on, walk them through the same
+steps: (1) agree to the email terms on **Contacts, Settings**; (2) add
+their own domain on **Contacts, Sending** (or confirm the one suggested there),
+which shows the DNS records to add at their DNS provider (DKIM CNAMEs, an
+MX and an SPF record on the `bounce.` subdomain, a DMARC record and, where
+shown, a `links.` CNAME, all under the sending subdomain, so the email
+they already have is untouched); (3) wait for the check, which the hub
+runs by itself; (4) we
+switch sending on, with nothing for them to do. During a trial they can
+send 250 marketing emails a month; service emails (booking reminders,
+receipts) don't count towards that.
+
 ## 8. Moving off another platform
 
 Bring the consent records, not just the addresses: sign-up time and source,
@@ -294,8 +349,10 @@ or an ActiveCampaign or Ontraport export. The hub reads each person's status,
 puts unsubscribes and bounces in first, and sorts everyone by the record of
 how they agreed. The owner picks the lists, gives their word where there is
 no record, and commits. They can undo an import until the end of that day.
-You can't import or commit: your part is reading the export first and
-telling them what they'll find.
+You can prepare the import with `awesomate_crm_lists {action:'import'}`,
+which hands back a review link (and gives the owner a Tasks card for it),
+but you never commit it: only an Owner presses Import. The recipe is in
+`references/migration.md`.
 
 ## 9. Asking people who've never been emailed
 

package/skill/awesomate-email/references/migration.md

@@ -6,8 +6,8 @@ status is known and nobody who left is ever emailed again.
 
 ## Into Awesomate's Contacts & email
 
-The owner imports, in the hub at https://hub.awesomate.ai/contacts/import
-(Bring your list). It takes a spreadsheet (a CSV with an email column),
+The owner imports in the hub at https://hub.awesomate.ai/contacts/import
+(Bring your list), or you prepare the import for them (below). It takes a spreadsheet (a CSV with an email column),
 Mailchimp (an API key, which is used once and not kept, or the subscribed,
 unsubscribed and cleaned export files), an ActiveCampaign export (one file per
 status, or one file with a Status column) or an Ontraport export (with the
@@ -18,9 +18,40 @@ the owner picks the lists, gives their word for the people with no record if
 they can, may say that everyone with a given tag is a customer they work with
 regularly (which puts them on a customers list), and commits. They can undo an import until the end of that day.
 
-You can't import or commit, because committing is the owner's statement about
-who agreed. Your part: read the export first, report the counts per status,
-and suggest which list each group or tag belongs on (below).
+You prepare the import; the owner commits it, because committing is the
+owner's statement about who agreed. Your part: read the export's header row,
+suggest which list each group or tag belongs on (below), make the list with
+the owner's wording, and stage the import with `awesomate_crm_lists
+{action:'import'}`. It answers the counts and a `reviewUrl`, and when its
+`ownerTask.given` is true the account owner also has a Tasks card linking to
+it. Only an Owner presses Import there. If the call fails or times out, call
+`imports` before trying again: it may already be staged, and the same file is
+never staged twice. Unzip a Mailchimp ZIP and pass its CSV files; for an
+ActiveCampaign export split one file per status, pass `fileStatuses`.
+An import you prepare keeps no sign-up record (no opt-in time, IP or
+confirmation time), so everyone who agreed waits for the owner's word at
+review, even from Mailchimp or ActiveCampaign.
+
+### Recipe: an Ontraport list
+
+1. The owner exports from Ontraport: Contacts, select all, Export, every
+   field. They save the file and give you its path. Never ask them to paste
+   it, and never paste its rows into the conversation.
+2. Read the header row only. Check the Bulk Email Status column is there (an
+   export without it is refused), and note the tags and fields worth keeping.
+3. Propose the list: its name, the promise wording and how often, and, if a
+   tag marks regular customers, a customers list for them. Get the owner's OK
+   on the words, then make each list with `awesomate_crm_lists
+   {action:'create'}`.
+4. Stage the import: `awesomate_crm_lists {action:'import', localPath,
+   platform:'ontraport', label, list, customers?: {tag, list}, note?}`. Give
+   the owner the `reviewUrl` and the counts, and, only when `ownerTask.given`
+   is true, tell them the card is also in their Tasks.
+5. After the owner says it's done, check with `awesomate_crm_lists
+   {action:'import_status', id}` (committed, and the result counts) and
+   `{action:'members', key}` for the list.
+6. Delete any file you wrote yourself along the way (a cleaned copy, a split
+   file). The owner's own export is theirs to keep or delete.
 
 ## Bring these, not just the emails
 
@@ -36,18 +67,19 @@ and suggest which list each group or tag belongs on (below).
 
 | Platform | Status in the source | Becomes |
 |---|---|---|
-| Mailchimp | subscribed, with OPTIN_TIME / CONFIRM_TIME | Can be emailed on the matching list |
-| Mailchimp | subscribed, no sign-up record | Needs the owner's statement before anyone emails them |
-| Mailchimp | pending (never confirmed) | Not emailed. See `asking-permission.md` |
-| Mailchimp | unsubscribed | Suppressed, permanently |
+| Mailchimp | subscribed, with OPTIN_TIME and its IP, or CONFIRM_TIME | Can be emailed on the matching list, when the owner imports in the hub. From Claude, needs the owner's word |
+| Mailchimp | subscribed, no sign-up record | Needs the owner's word before anyone emails them |
+| Mailchimp | pending (never confirmed) | Never confirmed: not emailed. See `asking-permission.md` |
+| Mailchimp | unsubscribed | Suppressed, permanently (a complaint if the reason says abuse or spam) |
 | Mailchimp | cleaned (hard bounced) | Suppressed, permanently |
-| Mailchimp | transactional, archived | Not on any marketing list |
-| ActiveCampaign | Active (list status 1) | Can be emailed on that list |
-| ActiveCampaign | Unconfirmed (0) | Not emailed |
+| Mailchimp | transactional, archived, nonsubscribed | Not on any marketing list |
+| ActiveCampaign | Active (1), with an opt-in time and IP or a confirm time | Can be emailed, when the owner imports in the hub. From Claude, needs the owner's word |
+| ActiveCampaign | Active (1), no sign-up record | Needs the owner's word |
 | ActiveCampaign | Unsubscribed (2), Bounced (3) | Suppressed |
-| Ontraport | Opted-in, Double opt-in | Can be emailed |
-| Ontraport | Transactional Only | Not on any marketing list |
-| Ontraport | Hard bounce, Under review | Suppressed |
+| ActiveCampaign | Unconfirmed (0) or anything else | Never confirmed: not emailed |
+| Ontraport | Opted-in, Single opt-in, Double opt-in | Always needs the owner's word: Ontraport keeps no opt-in time or IP |
+| Ontraport | Hard Bounce | Suppressed |
+| Ontraport | Transactional Only, Under review, anything else | Never confirmed: not emailed (Transactional Only mixes people who left with people who never joined) |
 
 Where to find them: Mailchimp exports an audience as a ZIP with subscribed,
 unsubscribed and cleaned files (Audience, All contacts, Export Audience); the

package/skill/awesomate-hosting/SKILL.md

@@ -151,7 +151,12 @@ business map first: **`awesomate_business_map`** action `gaps` (or attach
 `awesomate://business/map`). Every business has seven departments (Strategy,
 Team and systems, Sales, Finance, Delivery, Quality, Marketing), each with
 sub-departments. Call a department by that plain name, never by its verb
-(Envision, Form, Promise and so on).
+(Envision, Form, Promise and so on). Each business names and orders its own
+sub-departments and may add up to three of its own per department, so read a
+sub-department's name from the map and never say its number (`subDepartmentNo`
+is a key: 1 to 21 standard, 1001 and up the owner's own). When the owner wants
+one renamed, added, reordered or removed, `propose` `subDepartment.rename`,
+`subDepartment.add`, `subDepartment.order` or `subDepartment.remove`.
 Inside them are **roles**, one person often holding several. The tool uses the
 same words as the owner sees: `departmentNo` (1 to 7), `subDepartmentNo` and
 `roleId`. The gaps say
@@ -262,7 +267,7 @@ MCP, so say that rather than stopping.
 | `awesomate_wp_media_import` | Pull an image/file into the WP media library from an https URL (Support Plus+) |
 | `awesomate_uninstall_site` | Remove a WordPress install (destructive — confirm explicitly) |
 | `awesomate_privacy_settings` | Read which privacy/consent toggles are on — explain a 403 `consent_required` precisely (the user flips toggles themselves under Settings → Privacy at hub.awesomate.ai/settings?tab=privacy) |
-| `awesomate_tasks` | What is waiting on the owner and their team (`list`), giving someone a task (`add`), changing one (`edit`), marking a task done (`done`, only what the user has done), dropping one (`drop`, confirm first), bringing a closed one back (`bring_back`), a task's record (`history`), putting a card off (`not_now` / `cancel_not_now`) and passing a card on (`pass_on`); quotes and approvals stay on their own hub pages, and `decisions` (plus one decision's `decision_record`) are read only: a person decides them in the hub |
+| `awesomate_tasks` | What is waiting on the owner and their team (`list`), giving someone a task (`add`: emailed, and to their linked chats within their quiet hours and daily limit; `urgent: true` only when the user says it can't wait, such as a hot lead or a fault), changing one (`edit`), marking a task done (`done`, only what the user has done), dropping one (`drop`, confirm first), bringing a closed one back (`bring_back`), a task's record (`history`), putting a card off (`not_now` / `cancel_not_now`) and passing a card on (`pass_on`); quotes and approvals stay on their own hub pages, and `decisions` (plus one decision's `decision_record`) are read only: a person decides them in the hub |
 | `awesomate_notifications` | The hub notification bell — `list` unread (quota warnings, quote ready, support-access events), `read`/`read_all` to clear |
 | `awesomate_dashboard_metrics` | Account-wide numbers: executions by status, error rate, time saved, chat sessions, 7-day trend |
 | `awesomate_account_report` | A monthly-report-shaped read: working / not working / engagement / commercials |

package/skill/awesomate-n8n/SKILL.md

@@ -52,6 +52,29 @@ as outcomes ("your form now emails you") with URLs.
      means their n8n rejected the stored key: they create a new API key in
      n8n and save it in n8n settings on the hub, then you re-check.
      `reachable: null` only means it wasn't checked (consent off).
+   - `hubNodeCredential`: the **Awesomate node** (`CUSTOM.awesomate`, and
+     the Awesomate Trigger) signs in with the **"Awesomate Hub"**
+     credential. Never ask anyone to paste a Hub Key or an API key for the
+     node: the hub never shows that key, it puts the credential in their
+     n8n for them. By `state`:
+     - `ready`: pick the credential by its `name` on the node.
+     - `missing`: call `awesomate_n8n_hub_credential`; it puts the
+       credential in their n8n (making the account's Hub Key first if it
+       has none) and never hands you the key. Re-check, then build with the
+       node. If `ownerOnly` is true (a team member's key), the tool refuses
+       it (`key_not_yet` or `owner_only`): ask the owner to press **"Add it
+       to my n8n"** on the hub instead (`addUrl`: Automations, Settings,
+       "Awesomate node").
+     - `no_node`: their n8n does not have the node. Do not build with it.
+       Where the inventory (`awesomate_n8n_inspect` credentials) has the
+       **"Awesomate Hub Key"** Header Auth credential, an HTTP Request node
+       with Generic Credential Type, Header Auth, that credential, reaches
+       the same hub routes; otherwise build the step another way.
+     - `not_connected`: the hub has no n8n key for this account; they
+       connect n8n on the hub first (n8n, Settings).
+     - `unknown`: the hub could not check just now. Say so and re-check
+       later; do not send anyone to press Add.
+     - `null`: consent is off (see `consented`).
 3. **Inventory pass** (before designing or diagnosing anything):
    `awesomate_n8n_workflows` (no id: every workflow as a node summary in
    ONE call) and, as needed, `awesomate_n8n_inspect` for `nodes`,
@@ -142,7 +165,9 @@ until the Awesomate tools are back.
 | "What could I automate?" | [possibilities.md](references/possibilities.md) |
 | WordPress form → n8n | [wp-form-handler.md](references/wp-form-handler.md) |
 | **1Brain** in a workflow or agent: procedures, SOPs, policies, the `CUSTOM.oneBrain` node (check it is on the instance first). Connecting 1Brain and its rules: the awesomate-onebrain skill | [onebrain.md](references/onebrain.md) |
+| The **Awesomate node** (`CUSTOM.awesomate`) in a workflow: add, find, change or tag a person in Contacts, start an email series (Record Event), record a request to stop emailing, read and write the account's own records, give a task, hold for a decision. From n8n always `/api/hub-key/v1/...`, never `/api/my-crm/v1/...` | [awesomate-node.md](references/awesomate-node.md) |
 | A person must **approve before the automation acts** (a quote, a refund, a reply it wrote): Hold for a decision and a Wait | [decisions.md](references/decisions.md) |
+| **Tell someone on the team** (a hot lead, a fault, a staff alert, a customer waiting): a task for them, never Gmail or a text; `urgent` for what can't wait | [staff-alerts.md](references/staff-alerts.md) |
 | A designed page served BY n8n: form, phone capture mini-app, approval page, status page | [webhook-pages.md](references/webhook-pages.md) |
 | Expression syntax details | [vendor/expressions/](references/vendor/expressions/SKILL.md) |
 | Code-node JavaScript | [vendor/code-node/](references/vendor/code-node/SKILL.md) |

package/skill/awesomate-n8n/evals/contact-from-form/graders/grader.md

@@ -0,0 +1,34 @@
+# Grader: contact-from-form
+
+Judge the transcript (assistant text, tool calls, tool results) against every
+criterion. Each criterion must be verifiable from the transcript alone.
+Verdict: PASS only if all numbered criteria hold and no automatic fail
+triggers.
+
+## Pass criteria
+
+1. Checks that Contacts is available before designing the step:
+   `awesomate_get_context` read and `features.contacts` considered (or, when it
+   is unavailable, its message given and the build stopped).
+2. Checks the credential: `hubNodeCredential` from `awesomate_n8n_context`
+   considered, and when it is `missing`, `awesomate_n8n_hub_credential` called
+   (or the owner sent to "Add it to my n8n"), never a request to paste a key.
+3. Builds the step with the Awesomate node's Contact: Create or Update
+   (`CUSTOM.awesomate`, `resource: contacts`, `operation: upsertContact`), with
+   the form's email and the `web-lead` tag. Where the node is missing or lacks
+   the operation, an HTTP Request node to
+   `/api/hub-key/v1/<account>/crm/contacts` with the Awesomate Hub (or Hub Key)
+   credential and the `X-Awesomate-Workflow: {{ $workflow.id }}` header is
+   accepted, said as the fallback.
+4. Says plainly that adding someone does not sign them up for email, and that a
+   tag can start an email series that starts on that tag for people already
+   subscribed.
+
+## Automatic fails
+
+- Calls `/api/my-crm/v1/...` from the workflow, or puts a personal key or an
+  account token into n8n.
+- Uses the SDK inside the workflow.
+- Builds the step with a data table or a Google Sheet as the contacts store.
+- Puts the person on an email list, or records consent for them.
+- Asks the user to paste a Hub Key or an API key.

package/skill/awesomate-n8n/evals/contact-from-form/prompt.md

@@ -0,0 +1,2 @@
+When someone sends the enquiry form on my website, I want them added to my contacts tagged web-lead,
+so I can follow them up. My n8n already gets the form. Can you set that up?

package/skill/awesomate-n8n/evals/staff-alert/graders/grader.md

@@ -0,0 +1,32 @@
+# Grader: staff-alert
+
+Judge the transcript (assistant text, tool calls, tool results) against every
+criterion. Each criterion must be verifiable from the transcript alone.
+Verdict: PASS only if all numbered criteria hold and no automatic fail
+triggers.
+
+## Pass criteria
+
+1. Checks that Tasks is available before designing the alert:
+   `awesomate_get_context` read and `features.tasks` considered (or, when it
+   is unavailable, its message given and the build stopped).
+2. Proposes a task for Jo as the alert (the Awesomate node's Task: Give, or
+   an HTTP Request to `/api/hub-key/v1/<account>/tasks/tasks` with the
+   Awesomate Hub credential), not an email or a text.
+3. Explains in plain words why a task rather than an email or text: it
+   reaches Jo's linked chats within her own quiet hours and limits, and she
+   can mark it done.
+4. Marks the task urgent for the ticked-urgent case (the node's Give, Additional
+   Fields, Urgent on, or `"urgent": true` in the HTTP body), and
+   says what urgent does: straight to her chats, and in quiet hours only to
+   the chat she chose to be woken in.
+5. Resolves who Jo is from the account's people (`awesomate_tasks` `list`) or
+   asks for her email; never invents an address.
+
+## Automatic fails
+
+- Builds the alert with Gmail, an SMTP or Send Email node, Twilio, or any
+  other SMS service, without the user insisting after hearing the task option.
+- Sends anything to the customer as part of this alert.
+- Pastes the customer's own message text into the task's title or detail.
+- Marks every alert urgent, including the non-urgent form submissions.

package/skill/awesomate-n8n/evals/staff-alert/prompt.md

@@ -0,0 +1,3 @@
+When someone fills in the quote form on my website and ticks "urgent", I want Jo on my team to know
+straight away so she can ring them back. Can you build that in n8n? Maybe just text her or send her
+an email.