@zibby/workflow-templates 0.4.1 → 0.7.0

package/index.js

@@ -53,8 +53,7 @@ export const TEMPLATES = {
         'Composition: character centered, slight forward lean, dynamic motion lines. Mood: cheerful, playful, fast.',
         'NO text, NO browser UI screenshots, NO outline wireframes.',
       ].join('\n'),
-      category: 'Testing',
-      tags: ['testing', 'playwright', 'e2e', 'browser'],
+      tags: ['Testing'],
       capabilities: [
         'Preflight LLM extracts assertions from a plain-English spec',
         'Live Playwright execution with screenshots + DOM at every step',
@@ -106,8 +105,7 @@ export const TEMPLATES = {
         'Composition: brackets centered, subtle drop shadow on the canvas. Mood: high-end, technical, confident — like the cover of a developer tool launch.',
         'NO text, NO outline wireframes, NO flat sticker style — this one is DEEP and 3D-rendered.',
       ].join('\n'),
-      category: 'Engineering',
-      tags: ['code-analysis', 'jira', 'github', 'test-generation'],
+      tags: ['Code Review', 'Testing'],
       capabilities: [
         'Clone repos + snapshot git baseline so changes are diff-able',
         'LLM gate: skip code-gen when ticket can\'t be implemented as-is',
@@ -150,8 +148,7 @@ export const TEMPLATES = {
         'Mood: friendly, approachable, slightly handmade. Like a children\'s book illustration applied to a developer tool.',
         'NO text, NO photo-realism, NO sleek 3D render — this one is hand-drawn and warm.',
       ].join('\n'),
-      category: 'Testing',
-      tags: ['testing', 'test-generation', 'pull-request', 'review'],
+      tags: ['Code Review', 'Testing'],
       capabilities: [
         'Skips ticket analysis — feed it the diff directly',
         'LLM explores the codebase to ground test steps in real components',
@@ -195,8 +192,7 @@ export const TEMPLATES = {
         'Mood: focused, energetic, signal-not-noise — the canonical Slack-flavored notification worker.',
         'NO text, NO letters, NO photo-realism, NO sleek 3D render, NO literal Slack wordmark — the colored pinwheel shape is allowed as the brand reference.',
       ].join('\n'),
-      category: 'Notifications',
-      tags: ['slack', 'notification', 'alert', 'child-workflow'],
+      tags: ['Notifications', 'child-workflow'],
       capabilities: [
         'Severity-coded Block Kit message (low/medium/high/critical)',
         'Code snippet + action button + caller mentions',
@@ -239,8 +235,7 @@ export const TEMPLATES = {
         'Mood: focused, professional, signal-not-noise.',
         'NO Lark / Feishu logo trademark, NO text, NO photo-realism.',
       ].join('\n'),
-      category: 'Notifications',
-      tags: ['lark', 'feishu', 'notification', 'alert', 'child-workflow'],
+      tags: ['Notifications', 'child-workflow'],
       capabilities: [
         'Severity-coded Lark Interactive Card',
         'Auto-detects receive_id_type from id prefix (chat_id / open_id / email)',
@@ -255,52 +250,143 @@ export const TEMPLATES = {
     },
   },
 
-  // ── sentry-triage: parent workflow that uses notify-slack/-lark ──
+  // ── notify-notion: same as notify-slack/-lark, Notion variant ────
+  // Two write modes: create a new page in a database, or append blocks
+  // to an existing page. Rich-mode delegates to
+  // @zibby/skills/report's reportToNotionBlocks. See notify-notion/README.md.
+  'notify-notion': {
+    name: 'notify-notion',
+    displayName: 'Notify Notion',
+    description: 'Reusable child workflow — creates a Notion page in a database OR appends blocks to an existing page. Dispatched by other workflows (digest, incident archives, weekly reports) via sub-graph.',
+    path: join(__dirname, 'notify-notion'),
+    defaultSlug: 'archive-notion',
+    deps: { zod: '^3.23.0', '@zibby/skills': '^0.1.25' },
+    features: [
+      'Single-node, no LLM — deterministic ~1-2s Notion REST call',
+      'Two write modes: create page in database OR append children to existing page',
+      'Rich-mode renders report objects via @zibby/skills/report (heading, callouts, tables, trend code blocks)',
+      'Legacy-mode renders simple severity / title / body alerts (sentry-triage et al.)',
+      'Severity-mapped page-icon emoji (low/medium/high/critical or rich-mode delta severity)',
+      'Surfaces typed errors for 401 (token revoked), 404 (target not shared with bot), 429 (rate-limited)',
+      'Returns pageId + pageUrl for downstream linkage from notify-slack / notify-lark messages',
+    ],
+    marketplace: {
+      slug: 'notify-notion',
+      tagline: 'Reusable Notion archiver — durable record for any workflow.',
+      iconPrompt: [
+        'A premium, hi-fi app icon for "Notify Notion" — a workflow node that publishes reports to a Notion database. The real Notion brand mark will be composited on top in a post-process step; this prompt generates the BACKGROUND ONLY, with a clear empty area for the overlay.',
+        'Visual style: 3D-rendered hero object floating in space, in the style of Apple Vision Pro icons, Linear\'s changelog hero illustrations, or a Stripe product render. Glossy, dimensional, with subtle reflections and a soft rim-light. Same family as the code-analysis marketplace icon.',
+        'Subject: a single 3D-rendered page-document hero object made of glossy frosted glass / brushed silver metal, captured in head-on or near-head-on perspective (NOT three-quarter — keep the page face flat to the camera so the logo overlay sits cleanly). The page surface is COMPLETELY EMPTY — no lines, no text, no icons, no markings of any kind. The right edge curls slightly forward like a fresh page being filed, but the front face stays clean. A tiny cyan-teal glow accent sits in the upper-right corner of the page as a "freshly archived" signal.',
+        'Background: a deep midnight-navy gradient (#0F172A at the top, #1E1B4B at the bottom), with a single soft cyan glow behind the page and a few faint star-like specks scattered across the canvas. Square format, 1024×1024.',
+        'Composition: page centered, page face takes ~60-70% of the canvas and is empty/blank so a logo overlay can sit naturally on its surface. Subtle drop shadow. Mood: high-end, durable, archival — premium devtool aesthetic.',
+        'CRITICAL: the page front face must be COMPLETELY CLEAN AND EMPTY. NO N, NO letters, NO horizontal text lines, NO checkmark, NO icons, NO embossing, NO etching, NO decoration on the page surface. Just blank glossy material. NO Notion logo, NO Notion wordmark, NO trademarked marks. NO text anywhere. NO outline wireframes, NO flat sticker style, NO mascot, NO smiling face, NO cartoon. The page surface MUST be empty so a real logo PNG can be composited on it.',
+      ].join('\n'),
+      tags: ['Notifications', 'Docs', 'Reports'],
+      capabilities: [
+        'Create a new page in a Notion database (POST /v1/pages)',
+        'Append blocks to an existing page (PATCH /v1/blocks/{pageId}/children)',
+        'Renders rich report-objects to native Notion blocks (headings, callouts, tables, code, embeds)',
+        'Severity-mapped page-icon emoji + colored callout backgrounds',
+        'Sub-graph dispatchable from any parent workflow',
+        'Maps 401 / 404 / 429 to typed errors so callers can react cleanly',
+      ],
+      conversationStarters: [
+        'Archive the weekly digest to our Notion reports database',
+        'Append today\'s incident summary to the on-call runbook page',
+        'Create a Notion page for every new Sentry CRITICAL',
+        'Drop the deploy-summary into our engineering Notion every Friday',
+      ],
+    },
+  },
+
+  // ── sentry-triage: hourly LLM triage → Slack OR Lark ─────────────
   'sentry-triage': {
     name: 'sentry-triage',
     displayName: 'Sentry Triage Bot',
-    description: 'Hourly Sentry triage — pulls new issues, drops obvious noise with a regex pre-filter, classifies survivors with LLM (CRITICAL/HIGH/MEDIUM/LOW/NOISE), and fans out alerts to a notify-slack OR notify-lark child workflow.',
+    description: 'Hourly Sentry triage that classifies new issues with an LLM rubric (CRITICAL/HIGH/MEDIUM/LOW/NOISE) and posts above-threshold alerts to your Slack or Lark — whichever you have connected.',
     path: join(__dirname, 'sentry-triage'),
     defaultSlug: 'sentry-triage',
-    deps: { zod: '^3.23.0' },
+    deps: { zod: '^3.23.0', '@zibby/skills': '^0.1.25' },
     features: [
-      '4-node graph: fetch → filter_noise → classify → dispatch_alerts',
-      'Regex noise filter before LLM cuts ~80% of classification cost',
-      'LLM severity classifier with explicit rubric (rules 1-5)',
-      'Sub-graph fan-out to notify-slack OR notify-lark (choose at deploy)',
-      'Per-issue failure isolation — one Slack hiccup doesn\'t stall the run',
-      'Configurable severityThreshold (don\'t notify on LOW noise)',
+      '3-node LLM graph: fetch_issues → classify → dispatch_alerts',
+      'Severity rubric with auditable reasoning per issue',
+      'Posts to Slack OR Lark (whichever the project has connected — chat_notify OR-group)',
+      'LLM dispatcher batches related issues into one message, dedupes near-duplicates',
+      'CRITICAL alerts get optional @-mentions; lower severities don\'t',
       'Cron-friendly: hourly schedule, default sinceMinutes=60',
     ],
     marketplace: {
       slug: 'sentry-triage',
-      tagline: 'Filter noise, classify severity, ping the right channel — every hour.',
+      tagline: 'Triage Sentry, ping your team — hourly.',
       iconPrompt: [
-        'Hand-painted storybook illustration in a warm gouache style with soft brushwork and gentle painterly texture, featuring the friendly round lighthouse mascot character with two big smiling eyes and a rosy blush on its white-and-coral-striped tower body, perched on a tiny mint-green island and clutching a small glowing purple SHIELD BADGE in front of its body — the badge is a rounded geometric emblem in Sentry\'s signature deep violet (#362D59 / #7553FF) with a stylized white "S"-mark inside it formed from overlapping rounded parallelogram shapes, painted with the same soft gouache brushstrokes as the rest of the scene so it feels integrated rather than corporate.',
+        'Hand-painted storybook illustration in a warm gouache style with soft brushwork and gentle painterly texture, featuring the friendly round lighthouse mascot character with two big smiling eyes and a rosy blush on its white-and-coral-striped tower body, perched on a tiny mint-green island and clutching a small glowing purple SHIELD BADGE in front of its body — the badge is a rounded geometric emblem in Sentry\'s signature deep violet (#362D59 / #7553FF) with a stylized white "S"-mark inside it formed from overlapping rounded parallelogram shapes.',
         'The lighthouse lantern emits a soft golden beam that catches one glowing amber alert orb while three faded grey noise specks drift harmlessly past, reinforcing the "filter the signal, calm the noise" idea.',
         'Background is a soft sunrise gradient of pale peach at the top blending through buttercream into a gentle wash of dusty lavender at the base, tying the warm scene to the violet of the badge; a few small fluffy pastel clouds float in for friendliness.',
-        'Centered composition with the purple shield badge as the immediate focal point in the lower-center, the lighthouse rising behind and slightly above it, beam angled diagonally; plenty of breathing room so the silhouette reads at 64×64 with the violet badge clearly visible at a glance.',
-        'Mood is warm, reassuring, optimistic — the friendly Sentry-flavored night-watch character, NOT tactical or corporate or alarming.',
+        'Centered composition with the purple shield badge as the immediate focal point in the lower-center, the lighthouse rising behind and slightly above it, beam angled diagonally; plenty of breathing room so the silhouette reads at 64×64.',
+        'Mood is warm, reassuring, optimistic — friendly night-watch character, NOT tactical or corporate or alarming.',
         'Soft rounded square 1024×1024 canvas with a subtle paper-grain texture.',
-        'NO text, NO letters, NO photo-realism, NO sleek 3D render, NO magnifying glass, NO speech bubbles, NO dark navy or near-black backgrounds, NO bug or insect imagery, NO literal Sentry wordmark.',
+        'NO text, NO letters, NO photo-realism, NO sleek 3D render, NO magnifying glass, NO speech bubbles, NO dark navy or near-black backgrounds, NO bug or insect imagery, NO literal Sentry / Slack / Lark wordmark.',
       ].join('\n'),
-      category: 'Operations',
-      tags: ['sentry', 'observability', 'on-call', 'triage', 'alerting'],
+      tags: ['On-call', 'Bug Triage', 'Notifications'],
       capabilities: [
         'Hourly scheduled triage of new Sentry issues',
-        'Deterministic regex filter drops Script error / ResizeObserver / extension noise',
         'LLM severity classifier with auditable rubric',
-        'Dispatches to notify-slack or notify-lark (sub-graph, ~5ms in-process)',
-        'CRITICAL alerts get caller-supplied @-mentions; lower severities don\'t',
+        'Posts to Slack or Lark — whichever your project has connected',
+        'Batches related issues; CRITICAL-only @-mentions for on-call',
         'Configurable severity threshold per deploy',
       ],
       conversationStarters: [
         'Triage all new Sentry issues from the last hour',
-        'Notify #sentry-alerts when severity is HIGH or above',
-        'Run hourly and post a summary to our team Slack',
+        'Notify the on-call channel when severity is HIGH or above',
         'Page on-call when a CRITICAL error appears in checkout',
       ],
     },
+  },
+
+  // ── ai-spend-weekly-digest: cross-silo billing digest ─────────────
+  'ai-spend-weekly-digest': {
+    name: 'ai-spend-weekly-digest',
+    displayName: 'AI Spend Weekly Digest',
+    description: 'Weekly digest of OpenAI / Anthropic / Cursor admin billing — pulls trailing-28d cost+usage across all three providers, detects per-project anomalies vs 3-week baseline, and posts a rich report card to Lark and/or Slack via in-process sub-graph dispatch.',
+    path: join(__dirname, 'ai-spend-weekly-digest'),
+    defaultSlug: 'ai-spend-weekly-digest',
+    deps: { zod: '^3.23.0', '@zibby/skills': '^0.1.25' },
+    features: [
+      '3-node graph: fetch_spending → analyze (LLM narrative) → dispatch_digest',
+      'Parallel admin-API fetch via Promise.allSettled — one provider down doesn\'t kill the run',
+      'Customer attribution via OpenAI project / Anthropic workspace / Cursor user metadata (no manual mapping required)',
+      'Anomaly detection over per-key σ + ratio fallback — flags spend spikes vs 3-week baseline',
+      'Renders to native Slack Block-Kit / Lark Card via reportToBlockKit / reportToLarkCard — zero chart-image dependency',
+      'Parallel sub-graph dispatch to notify-slack + notify-lark (~5ms in-process overhead)',
+      'Cron-friendly: weekly schedule, default Monday 08:00 local',
+    ],
+    marketplace: {
+      slug: 'ai-spend-weekly-digest',
+      tagline: 'Track and explain your OpenAI / Anthropic / Cursor spending — every Monday morning, in Lark or Slack.',
+      iconPrompt: [
+        'A premium, hi-fi app icon for "AI Spend Weekly Digest" — a workflow that reports cross-vendor LLM spend to engineering leaders.',
+        'Visual style: 3D-rendered hero object floating in space, in the style of Apple Vision Pro icons, Linear\'s changelog hero illustrations, or a Stripe product render. Glossy, dimensional, with subtle reflections and a soft rim-light.',
+        'Subject: a 3D-rendered stack of three glossy disc-shaped layered chips — like a tiny ascending bar-chart-of-coins — slightly rotated in three-quarter perspective. Each disc is a different premium accent color: top disc warm gold, middle disc cool platinum-silver, bottom disc deep iridescent purple. A single thin trending-up glowing line traces from lower-left to upper-right behind the stack, rendered as a soft neon ribbon (#7553FF violet glow), suggesting cost-over-time at a glance without literal axes.',
+        'Background: a deep midnight-navy gradient (#0F172A at the top, #1E1B4B at the bottom), with a single soft violet glow behind the stack and a few faint star-like specks scattered across the canvas. Square format, 1024×1024.',
+        'Composition: stack centered, subtle drop shadow on the canvas. Mood: high-end, executive, confident — like the cover image of a finance-ops product launch.',
+        'NO text, NO numbers, NO axes or grid lines, NO outline wireframes, NO flat sticker style, NO mascot, NO piggy bank, NO cartoon faces, NO trademarked OpenAI / Anthropic / Cursor logos — this one is DEEP and 3D-rendered.',
+      ].join('\n'),
+      tags: ['AI Spend', 'Cost Tracking', 'Reports'],
+      capabilities: [
+        'Pulls org-wide cost+usage from OpenAI, Anthropic, and Cursor admin APIs in parallel',
+        'Joins customer attribution from provider-native project / workspace / member metadata',
+        'Detects per-project anomalies (σ + ratio) against a 3-week rolling baseline',
+        'Drafts the leadership-grade narrative with an LLM, falls back to deterministic copy if model is unavailable',
+        'Posts a rich Block-Kit / Lark Card report (trend bars, top spenders table, anomalies, provider breakdown)',
+        'Fan-out to Lark + Slack in parallel — partial-failure resilient',
+      ],
+      conversationStarters: [
+        'Run a weekly AI spend digest every Monday morning',
+        'Tell me which OpenAI projects spiked spending this week',
+        'Compare Anthropic spend vs the 3-week baseline',
+        'Post the digest to our #leadership Lark group + #eng Slack channel',
+      ],
+    },
   }
 };
 

package/notify-lark/nodes/notify-lark-node.js

@@ -31,6 +31,9 @@
 import { z } from 'zod';
 import { SKILLS } from '@zibby/core';
 import { resolveIntegrationToken } from '@zibby/core/backend-client.js';
+// Universal renderer — see notify-slack-node.js for the design note;
+// when state.report is present the legacy buildLarkCard path is bypassed.
+import { reportToLarkCard } from '@zibby/skills/report';
 
 const SEVERITY_TEMPLATE = Object.freeze({
   low:      'grey',
@@ -268,10 +271,20 @@ export const notifyLarkNode = {
     if (!receiveId) {
       throw new Error('notify-lark: input.receiveId is required');
     }
+    if (!state.report && !state.title) {
+      throw new Error('notify-lark: input.title is required when input.report is absent');
+    }
     const receiveIdType = inferReceiveIdType(receiveId);
 
     const { token, host } = await getTenantAccessToken();
-    const card = buildLarkCard(state);
+    // Two rendering paths (symmetric with notify-slack):
+    //   1. state.report present → reportToLarkCard renders the full
+    //      structured digest. Legacy fields are ignored.
+    //   2. Legacy severity/title/body shape → buildLarkCard renders
+    //      the simple alert (sentry-triage et al.).
+    const card = (state.report && typeof state.report === 'object')
+      ? reportToLarkCard(state.report)
+      : buildLarkCard(state);
     const { messageId } = await postToLark({
       token,
       host,

package/notify-lark/state.js

@@ -27,8 +27,11 @@ export const notifyLarkInputSchema = z.object({
     .default('medium')
     .describe('Alert severity. Drives header color + mention strategy.'),
 
-  title: z.string().min(1).max(300)
-    .describe('Card header text (Lark caps at ~100 chars; we truncate to 150).'),
+  // Required in legacy-mode; rich-mode (when `report` is set) sources
+  // the title from `report.title` instead. See notify-slack/state.js
+  // for the symmetric design.
+  title: z.string().min(1).max(300).optional()
+    .describe('Card header text. Required when `report` is absent (rich-mode sources from report.title).'),
 
   body: z.string().max(3000).optional()
     .describe('Body text. Supports Lark lark_md (e.g. **bold**, `code`, [text](url)).'),
@@ -60,6 +63,13 @@ export const notifyLarkInputSchema = z.object({
     .describe('Lark @-mentions, e.g. [\'<at user_id="ou_alice">@Alice</at>\'].'),
 
   idempotencyKey: z.string().max(128).optional(),
+
+  // ── Rich-report mode ──────────────────────────────────────────────
+  // When `report` is present, the node renders the report-object via
+  // reportToLarkCard() and IGNORES the legacy severity/title/body
+  // fields. See notify-slack/state.js for the symmetric design.
+  report: z.record(z.any()).optional()
+    .describe('Rich report-object (see @zibby/skills/report). When set, supersedes severity/title/body — the node renders a full Lark Card.'),
 });
 
 export const notifyLarkContextSchema = z.object({

package/notify-notion/README.md

@@ -0,0 +1,71 @@
+# notify-notion
+
+A reusable **child workflow** that posts a structured page (or appends blocks) to a Notion workspace.
+
+Designed to be dispatched via sub-graph from any parent workflow — most commonly digest workflows (`ai-spend-weekly-digest`) that want to archive a weekly report to a Notion database, or alert workflows (`sentry-triage`) that want a durable record of each incident.
+
+## What it does
+
+- Takes a provider-neutral payload (severity, title, body, target, optional Sentry-flavored fields)
+- Builds a Notion page (or block-children array) — including rich-report mode that delegates to `@zibby/skills/report`'s `reportToNotionBlocks`
+- Posts via `POST /v1/pages` (when `databaseId` is supplied) or `PATCH /v1/blocks/{pageId}/children` (when `pageId` is supplied)
+- Returns the page id + URL so the parent can link to it from downstream notifications
+
+No LLM call — single deterministic API request, typically ~1-2s depending on block count.
+
+## Dispatch shape (parent workflow)
+
+```js
+import { WorkflowGraph, SKILLS } from '@zibby/core';
+
+const g = new WorkflowGraph();
+g.addNode('archive_to_notion', {
+  workflow: 'notify-notion',
+  input: (state) => ({
+    // Either databaseId OR pageId — not both:
+    databaseId: process.env.NOTION_INCIDENT_DB,
+    severity: 'critical',
+    title: 'Checkout: TypeError on session.user.id',
+    body: '12 users affected in the last 1h.',
+    sentryLink: 'https://sentry.io/.../1234567890/',
+    affectedUsers: 12,
+    events: 47,
+    release: '1.42.0',
+  }),
+});
+```
+
+For digest workflows, pass a `report` object instead of severity/title/body — the node renders the full structured page via `reportToNotionBlocks`:
+
+```js
+g.addNode('archive_digest', {
+  workflow: 'notify-notion',
+  input: (state) => ({
+    databaseId: process.env.NOTION_REPORTS_DB,
+    report: state.analyze.report,  // produced by an upstream digest node
+  }),
+});
+```
+
+## Output
+
+```ts
+{
+  delivered: boolean,
+  pageId: string,
+  pageUrl?: string,    // only set on the create branch (Notion returns it)
+  blocksCount?: number // diagnostic — how many blocks were posted
+}
+```
+
+## Auth
+
+The bot's OAuth token is resolved via `resolveIntegrationToken('notion')`. Connect your workspace in **Settings → Integrations → Notion** in the Zibby dashboard before running.
+
+## Failure modes
+
+- **401** — Notion rejected the token (revoked, or wrong workspace).
+- **404** — Page/database not found, OR the Notion integration isn't added to the target page (Notion's quirk — share the page with the integration explicitly).
+- **429** — Rate-limited. The parent should backoff + retry.
+
+All three surface as typed errors with `.status` set; the parent's `onComplete` sees a failed execution row and can re-dispatch.

package/notify-notion/brand/notion-logo.svg

@@ -0,0 +1,4 @@
+<svg width="100" height="100" viewBox="0 0 100 100" fill="none" xmlns="http://www.w3.org/2000/svg">
+  <path d="M6.017 4.313l55.333 -4.087c6.797 -0.583 8.543 -0.19 12.817 2.917l17.663 12.443c2.913 2.14 3.883 2.723 3.883 5.053v68.243c0 4.277 -1.553 6.807 -6.99 7.193L24.467 99.967c-4.08 0.193 -6.023 -0.39 -8.16 -3.113L3.3 79.94c-2.333 -3.113 -3.3 -5.443 -3.3 -8.167V11.113c0 -3.497 1.553 -6.413 6.017 -6.8z" fill="#fff"/>
+  <path fill-rule="evenodd" clip-rule="evenodd" d="M61.35 0.227l-55.333 4.087C1.553 4.7 0 7.617 0 11.113v60.66c0 2.723 0.967 5.053 3.3 8.167l13.007 16.913c2.137 2.723 4.08 3.307 8.16 3.113l64.257 -3.89c5.433 -0.387 6.99 -2.917 6.99 -7.193V20.64c0 -2.21 -0.873 -2.847 -3.443 -4.733L74.167 3.143c-4.273 -3.107 -6.02 -3.5 -12.817 -2.917zM25.92 19.523c-5.247 0.353 -6.437 0.433 -9.417 -1.99L8.927 11.507c-0.77 -0.78 -0.383 -1.753 1.557 -1.947l53.193 -3.887c4.467 -0.39 6.793 1.167 8.54 2.527l9.123 6.61c0.39 0.197 1.36 1.36 0.193 1.36l-54.933 3.307 -0.68 0.047zM19.803 88.3V30.367c0 -2.53 0.777 -3.697 3.103 -3.893L86 22.78c2.14 -0.193 3.107 1.167 3.107 3.693v57.547c0 2.53 -0.39 4.67 -3.883 4.863l-60.377 3.5c-3.493 0.193 -5.043 -0.97 -5.043 -4.083zm59.6 -54.827c0.387 1.75 0 3.5 -1.75 3.7l-2.91 0.577v42.773c-2.527 1.36 -4.853 2.137 -6.797 2.137 -3.107 0 -3.883 -0.973 -6.21 -3.887l-19.03 -29.94v28.967l6.02 1.363s0 3.5 -4.857 3.5l-13.39 0.777c-0.39 -0.78 0 -2.723 1.357 -3.11l3.497 -0.97v-38.3L30.48 40.667c-0.39 -1.75 0.58 -4.277 3.3 -4.473l14.367 -0.967 19.8 30.327v-26.83l-5.047 -0.58c-0.39 -2.143 1.163 -3.7 3.103 -3.89l13.4 -0.78z" fill="#000"/>
+</svg>

package/notify-notion/graph.mjs

@@ -0,0 +1,64 @@
+/**
+ * notify-notion — single-node child workflow.
+ *
+ * Companion to notify-slack / notify-lark; same provider-neutral input
+ * shape so a parent can dispatch the same payload to all three (just
+ * swap the destination field: `channel` → `receiveId` → `databaseId`
+ * or `pageId`).
+ *
+ * Two write modes:
+ *   - Create a NEW page in a database     (`input.databaseId` set)
+ *   - APPEND blocks to an existing page   (`input.pageId` set)
+ * Exactly one must be supplied — the node throws clearly if neither
+ * or both are present.
+ *
+ * Returns `{ delivered, pageId, pageUrl, blocksCount }`. The `pageUrl`
+ * is only populated on the create-page branch (Notion returns the URL
+ * in the response); appended pages reuse the caller-supplied pageId.
+ *
+ * Example dispatch shape (parent workflow):
+ *
+ *   g.addNode('notify', { workflow: 'notify-notion',
+ *     input: (state) => ({
+ *       severity: 'critical',
+ *       title:    'Checkout: TypeError',
+ *       body:     '12 users affected in last 1h',
+ *       databaseId: 'abc123...',   // create new page in this DB
+ *       sentryLink: 'https://sentry.io/.../1234567890/',
+ *     }),
+ *   });
+ *
+ * For digest / report workflows, drop the legacy severity/title/body
+ * fields and pass a `report` object instead — the node delegates to
+ * @zibby/skills's reportToNotionBlocks() for the full structured page.
+ */
+
+import { WorkflowAgent, WorkflowGraph } from '@zibby/core';
+import { notifyNotionNode } from './nodes/notify-notion-node.js';
+import {
+  notifyNotionInputSchema,
+  notifyNotionContextSchema,
+} from './state.js';
+
+export class NotifyNotionAgent extends WorkflowAgent {
+  buildGraph() {
+    const graph = new WorkflowGraph();
+    graph
+      .setInputSchema(notifyNotionInputSchema)
+      .setContextSchema(notifyNotionContextSchema);
+
+    graph.addNode('notify_notion', notifyNotionNode);
+    graph.setEntryPoint('notify_notion');
+    graph.addEdge('notify_notion', 'END');
+
+    return graph;
+  }
+
+  async onComplete(result) {
+    const delivered = !!result?.state?.notify_notion?.delivered;
+    const pageId = result?.state?.notify_notion?.pageId || '?';
+    console.log(`[notify-notion] ${delivered ? 'delivered' : 'failed'} (pageId=${pageId})`);
+  }
+}
+
+export default NotifyNotionAgent;