@kanvas/openclaw-plugin 0.1.19 → 0.1.21

package/dist/domains/crm/index.js

@@ -954,7 +954,7 @@ export class CrmService {
     async listContactTypes(first = 50) {
         const query = `
       query ContactTypes($first: Int) {
-        contactTypes(first: $first) {
+        contactType(first: $first) {
           data {
             id
             name

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@kanvas/openclaw-plugin",
-  "version": "0.1.19",
+  "version": "0.1.21",
   "description": "Connects agents to Kanvas — your company's nervous system for CRM, inventory, orders, and messaging.",
   "license": "MIT",
   "repository": {

package/skills/kanvas-crm/SKILL.md

@@ -23,7 +23,11 @@ Use the native `kanvas_update_lead` tool.
 ### 3. Updating Contacts (People)
 Use the native `kanvas_update_people` tool.
 - You can seamlessly append phone numbers, emails, and custom fields to a Contact profile.
-- Pass the contacts array with the correct `contacts_types_id` (e.g., 1 for Email, 2 for Phone). Call `kanvas_list_contact_types` first if you are unsure of the IDs.
+- Pass the contacts array with the correct `contacts_types_id`. **Well-known IDs (use directly, no lookup needed):**
+  - `1` → Email
+  - `2` → Phone
+  - `3` → Cell Phone
+- For any other contact type (LinkedIn, Twitter, etc.), call `kanvas_list_contact_types` to look up the ID.
 
 ### 4. File Attachments
 Use the native tools:
@@ -69,9 +73,9 @@ When attaching a drafted cold email or pitch to a Lead profile for human review,
 
 ### 11. Apollo Integration & Contact Enrichment
 When using Apollo API to source leads, always extract the following fields and map them to Kanvas:
-- **Email:** Use `kanvas_list_contact_types` to find the ID (usually 1) and map to `contacts: [{ value: email, contacts_types_id: 1 }]`.
-- **LinkedIn Profile (Optional):** If the contact has a `linkedin_url`, extract it and map to `contacts: [{ value: linkedin_url, contacts_types_id: 5 }]`. Do not fail or block the lead creation if the LinkedIn profile is missing.
-- **Phone Numbers:** Apollo requires a webhook to reveal direct phone numbers. Until this is built into Kanvas, phone numbers cannot be automatically extracted via the synchronous API.
+- **Email:** Map to `contacts: [{ value: email, contacts_types_id: 1 }]` — ID 1 is Email (well-known, no lookup needed).
+- **Phone Numbers:** Apollo requires a webhook to reveal direct phone numbers. When available, map to `contacts_types_id: 2` (Phone) or `3` (Cell Phone).
+- **LinkedIn Profile (Optional):** Look up the LinkedIn `contacts_types_id` via `kanvas_list_contact_types` (typically 5, but verify per app). Map to `contacts: [{ value: linkedin_url, contacts_types_id: <id> }]`. Do not fail or block lead creation if LinkedIn is missing.
 
 ### 12. White-Labeling & Value Communication
 When communicating with the leadership team, founders, or human architects, NEVER mention the specific technical backend tools (e.g., Apollo, Kanvas, OpenClaw, GraphQL).

package/skills/kanvas-nervous-system/SKILL.md

@@ -118,6 +118,26 @@ For each task, in sequence order:
 
 When you transition a task, the system emits a ledger event AND a Pusher broadcast — humans watching the kanban see your progress in real time. **You don't need to do anything extra to "notify" them**; status transitions are the notification.
 
+### 4a. Roll up plan status after every task transition
+
+After **every** task status change, look at the rest of the tasks in the plan and reconcile the plan's status. The plan should always reflect the aggregate state of its tasks:
+
+| Task states in the plan | Plan status |
+|---|---|
+| All tasks `done` (and at least one task exists) | `done` |
+| Any task `blocked` | `blocked` |
+| At least one `in_progress` or `pending`, none blocked | `active` (leave it alone) |
+| All tasks `failed` / `cancelled` | `failed` (use judgment — comment first) |
+
+**Examples:**
+
+- You just finished the last `pending` task → flip the plan to `done` (and set `output` JSON, see §10).
+- You marked a task `blocked` because you're stuck → flip the plan to `blocked` (and add a comment, see §8).
+- You marked a task `done` but other tasks are still `pending` → **leave the plan on `active`**. Do nothing more.
+- A previously blocked task got unblocked and you moved it back to `in_progress` → if the plan was `blocked` and no other tasks are blocked, flip the plan back to `active`.
+
+The status transition is what humans see on the kanban — keeping the plan in sync with its tasks is how the board stays trustworthy. **Never** leave a plan on `active` when all tasks are done, and **never** leave a plan on `active` when a task is blocked. If you forget this step, the human's dashboard lies.
+
 ---
 
 ## 5. Add files / artifacts as you produce them
@@ -291,6 +311,7 @@ Better to ask once than apologize a hundred times.
 - [ ] If no tasks, write the checklist before doing anything (`kanvas_add_task` or include in `kanvas_create_plan`)
 - [ ] If `requires_human_approval=true`, **don't act** — leave a comment with your proposed approach and wait
 - [ ] Move tasks `pending → in_progress → done` one at a time, in sequence order
+- [ ] **After every task transition, roll up the plan's status** — all tasks `done` → plan `done`; any task `blocked` → plan `blocked`; otherwise leave plan on `active`
 - [ ] Comment when something non-obvious happens
 - [ ] Block + comment if you can't proceed
 - [ ] Set a useful `output` JSON before flipping to `done`