crm-stage-update

Standardize Notion CRM pipeline stage updates with Neon event logging.

1|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/antonyfmunoz/OS --skill crm-stage-update
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crm-stage-update
Source: https://github.com/antonyfmunoz/OS/tree/main/skills/Sales/crm_stage_update
Command: npx skills add https://github.com/antonyfmunoz/OS --skill crm-stage-update

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Eliminates inconsistent or conflicting pipeline updates when multiple agents touch lead and customer records by enforcing a single authoritative Notion stage update process.

Core Features & Use Cases

  • Standardized Pipeline Stage Updates: Ensures every lead/customer stage moves through the correct sequence (Lead → Contacted → Qualified → Proposal → Negotiation → Closed Won → Active Customer → At Risk → Churned).
  • Required Field Synchronization: Updates Stage, Last Contact, Next Action (with specific step and date), Assigned To, and conversation-relevant Notes in one coordinated workflow.
  • Dual-System Logging for Auditability: Logs the event in Neon events table and prevents mismatch between Notion and Neon so reporting stays reliable.
  • Use Case: When a sales agent qualifies a lead and schedules the next call, the record’s stage, next action date, ownership, and notes are updated consistently and immediately for accurate CRM visibility.

Quick Start

Ask the AI to run the crm-stage-update skill to update the Notion CRM Pipeline record for a lead after the latest interaction, including stage, next action (with date), assigned agent, notes, and Neon event logging.

Frequently Asked Questions about crm-stage-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I standardize Notion CRM pipeline stage updates after agent interactions?

To standardize Notion CRM pipeline stage updates, you enforce a single authoritative process requiring field updates for Stage, Last Contact, Next Action, Assigned To, and Notes alongside Neon event logging after any agent touches a lead record.

What is the correct sequence for moving leads through a sales pipeline in Notion?

The correct Notion sales pipeline sequence is Lead, Contacted, Qualified, Proposal, Negotiation, Closed Won, Active Customer, At Risk, and Churned, ensuring leads move through the correct stages to prevent inconsistent funnel data.

How do I keep Notion and Neon event logs consistent for sales workflows?

You keep Notion and Neon consistent by applying dual-system logging during CRM updates, which logs the pipeline stage change in the Neon events table to prevent mismatches and keep reporting reliable.

Can I use this skill to update lead qualification and next action dates in Notion?

Yes, you can update lead qualification by moving the stage to Qualified and synchronizing the Next Action field with a specific step and date, ensuring the record reflects the latest sales interaction accurately.

Why does my Notion CRM have conflicting pipeline stages when multiple agents update records?

Conflicting Notion CRM pipeline stages occur when multiple agents touch lead records without a standardized process, requiring an authoritative update workflow to coordinate field synchronization and prevent inconsistent data.

What fields are required to update a Notion CRM record for lead qualification?

Required fields for updating a Notion CRM record during lead qualification include Stage, Last Contact, Next Action with a specific date, Assigned To, and conversation-relevant Notes to maintain accurate CRM visibility.