change-deal-stage

Update deal stages via REST API with validation and verification.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Cimminelli1982/crm-frontend --skill change-deal-stage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-deal-stage
Source: https://github.com/Cimminelli1982/crm-frontend/tree/main/docs/openclaw-skills/change-deal-stage
Command: npx skills add https://github.com/Cimminelli1982/crm-frontend --skill change-deal-stage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the process of updating deal stages in sales pipelines, reducing manual updates and ensuring consistent progress tracking across systems.

Core Features & Use Cases

  • Parse context: extracts Deal ID, Deal Name, and Contact ID from user input or context.
  • Info retrieval & validation: fetches current deal data and validates the requested stage against the allowed list.
  • Stage update & verification: updates the deal stage via PATCH and confirms the change with a follow-up GET.
  • Ambiguity handling: if no Deal ID is provided, can search by deal name or prompt for selection.
  • Audit-ready output: returns a concise confirmation message suitable for logs and user feedback.

Quick Start

Provide a deal ID and the target stage to update its pipeline status.

Frequently Asked Questions about change-deal-stage

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

FAQPage Schema
How do I update deal stages in a CRM pipeline automatically?

To update deal stages automatically, provide a valid deal ID or name and target stage, patch the record via REST API, and verify the change with a follow-up GET request.

What information do I need to change a deal stage in my pipeline?

Changing a deal stage requires a valid deal identifier (ID or name), a target stage from the allowed list, and REST API access to patch and verify the update.

Can I update a pipeline deal stage if I only know the deal name?

Yes, if no Deal ID is provided, the system searches by deal name or prompts for selection to resolve ambiguity before applying the validated stage update.

How does automation handle stage validation when changing a deal stage?

Stage validation fetches current deal data and checks the requested stage against an allowed list before applying the PATCH update to the pipeline.

Does updating a deal stage through an API provide confirmation logs?

Yes, after patching the deal stage via REST API, a follow-up GET verifies the change and returns a concise confirmation message suitable for audit logs.