notion-review

To set up a Notion approval workflow for GTM lead qualification, you run the review:setup command, which creates a Batches kanban database on your parent Notion page to gate qualified leads before downstream use.

Yes, you can reject specific leads using item-level kill-list statuses. Each batch card contains an inline child database where reviewers mark individual items as Qualified or Removed independently of the batch-level gate.

You can review qualified leads, visitors, engagers, lead-magnet replies, and content drafts. The workflow supports per-output-type configuration, creating dedicated Notion kanban review surfaces for each category.

You can reconfigure or toggle the Notion review gate using built-in lifecycle commands. Settings are stored in ~/.gtm-os/notion-reviews.yaml, supporting reconfigure, gate toggling, and verification of the required Notion database contract.

Yes, the workflow verifies a required Notion database contract during setup. It creates a Batches DB with kanban and gallery views via MCP and implements an inline per-batch child database pattern for approved-batch reads.

Use batch-level status as the primary gate to prevent unapproved GTM outputs from flowing downstream, and item-level status as a kill-list. This two-level safety control ensures entire campaigns are gated while allowing individual lead removals.