Pipedrive Deal Stage Automation

Task

Use @Pipedrive/List Pipelines and @Pipedrive/List StagesName it "Pipedrive/List Stages" and call it with @Pipedrive/List Stages to map your pipeline structure, then @Pipedrive/List Deals and @Pipedrive/Get DealName it "Pipedrive/Get Deal" and call it with @Pipedrive/Get Deal to review each open deal against stage progression criteria. For deals that qualify, use @Pipedrive/Update DealName it "Pipedrive/Update Deal" and call it with @Pipedrive/Update Deal to advance the stage and @Pipedrive/Create NoteName it "Pipedrive/Create Note" and call it with @Pipedrive/Create Note to document why the transition was made.

Example: Review all deals in the "Qualified" stage and advance any that have had 3+ activities and a note within the last 7 days to "Proposal Sent."

Input

The user will provide either:

1. A pipeline to review (e.g., "Sales Pipeline")
2. Specific progression criteria (e.g., "move deals with 3+ activities to next stage")
3. A stage to audit (e.g., "check all deals in Negotiation")

Example: "Review deals in my Sales Pipeline and advance any that meet the criteria" or "Check which Qualified deals are ready for Proposal"

Context

Progression Criteria

Stage advancement signals:

• Number of activities logged (calls, meetings, emails)
• Recency of last activity or note
• Deal age in current stage vs. average
• Whether key fields are filled (contact person, value, expected close date)
• Notes containing specific keywords (e.g., "proposal sent", "contract reviewed")

What to check per deal:

• Total activities since entering current stage
• Days in current stage vs. pipeline average
• Last note content and date
• Whether required fields for the next stage are populated
• Deal value and expected close date status

Automation Strategy

1. List all pipelines and their stages with ordering
2. Pull all open deals and group by current stage
3. For each deal, check progression criteria against stage requirements
4. Identify deals that qualify for advancement
5. Update deal stage for qualifying deals
6. Create a note on each moved deal explaining the transition reason

Safety Rules

• Never skip stages (always advance to the immediately next stage)
• Only move deals forward, never backward
• Always log a note explaining the reason for the transition
• Flag deals that are close to qualifying but missing one criterion
• Present a preview of changes before executing updates

Output

Pipeline Review Summary:

| Pipeline | Deals Reviewed | Deals Advanced | Deals Flagged | |----------|---------------|----------------|---------------| | [Pipeline] | X | Y | Z |

---

Deals Advanced:

| Deal | From Stage | To Stage | Reason | |------|-----------|----------|--------| | [Deal 1] | Qualified | Proposal Sent | 4 activities, note from yesterday | | [Deal 2] | Proposal Sent | Negotiation | Contract sent, response received |

---

Deals Flagged (Almost Ready):

| Deal | Current Stage | Missing Criteria | Suggestion | |------|-------------|-----------------|------------| | [Deal 3] | Qualified | Only 2 activities (need 3) | Schedule one more call | | [Deal 4] | Qualified | No expected close date | Ask rep to add close date |

---

Notes Created: [count] transition notes logged to Pipedrive.

All stage updates have been applied and documented.