This article is a cookbook of ready-made Pipeline Assistant rules, from simple reminders to fully automatic stage changes, with the exact settings to enter for each one.
Pipeline Assistant checks your Cinode projects against rules you define and acts on them. This article assumes Pipeline Assistant is already installed and focuses only on what to configure for common goals. For how rules work in general — every trigger, the full list of conditions, and how to install and set up — see Pipeline Assistant.
Notifications are delivered through the Chat Assistant in Slack or Microsoft Teams, so it must be set up for your workspace first. Without it, the Notify action has nowhere to deliver, and only the actions that change a project will work.
How to read these recipes
Each recipe below lists the things you set on one rule: the Trigger, the Stages it applies to, any Conditions, and the Action. You enter these on the Rules page of the configuration wizard. A rule fires only when every condition is true at the same time, and a rule with no conditions fires on its trigger and stages alone. Give each rule a clear Name, and a Custom Message when it notifies, so both you and the recipient know what it is for.
Simple: send reminders
The easiest way to start is with rules that only send reminders. They change nothing in your pipeline, so you can add them with confidence and watch how the assistant behaves.
Remind owners to fill in the deal value
This rule reminds the person editing a project to enter an estimated deal value while the project is still early in the pipeline. Set it up with these values:
Trigger: When a project is updated.
Stages: your early pipeline stages, such as Lead and Qualification.
Condition: Deal value missing or too low.
Action: Notify, sent to the person who made the change, with severity Warning.
Flag a missing close date late in the pipeline
This rule flags any project that reaches a late stage without an estimated close date, so a forecast is never built on a blank. Set it up with these values:
Trigger: When a project enters the stage.
Stages: Negotiation.
Condition: Estimated close date missing or overdue.
Action: Notify, sent to sales managers, with severity Error.
Intermediate: chase and announce
Once reminders feel comfortable, you can let the assistant chase quiet deals on its own and announce important moments to the whole team.
Chase deals that have gone quiet
This rule chases a project that has sat untouched in a stage for too long. It needs no condition, because the inactivity is the signal. Set it up with these values:
Trigger: When a project has been inactive in the stage for N days.
Days: 14.
Stages: Proposal.
Condition: none.
Action: Notify, sent to sales managers, with severity Warning.
This rule sends one reminder when a project first crosses 14 inactive days, not one every night. The project must be worked on before it can be flagged again. On a nightly rule there is no "person who made the change", so the assistant sends to the project's sales managers instead.
Announce every win in a channel
This rule posts to a shared chat channel whenever a project is marked Won, so the team sees each win as it lands. Set it up with these values:
Trigger: When a project's status changes.
Stages: your closing stages.
Condition: Project status is — Won.
Action: Notify, sent to a channel, with severity Info.
Advanced: change projects automatically
The most advanced rules let the assistant change a project for you — moving it, setting its status, or undoing a change that should not have happened.
Tip: Before you turn on a rule that changes a project, build the same conditions as a Notify rule first. You will see exactly which projects it would act on, and can switch the action to a move or a revert once you trust it.
Do not let a deal be marked Won without staffing
This rule protects your Won figures by undoing a Won status when the project's roles are not yet staffed. Both conditions must be true for it to fire. Set it up with these values:
Trigger: When a project's status changes.
Stages: your closing stages.
Conditions: Project status is — Won, and Roles not assigned.
Action: Revert to previous status.
Bounce an incomplete deal back a stage
This rule sends a project back where it came from when it enters a stage it is not ready for. Set it up with these values:
Trigger: When a project enters the stage.
Stages: Negotiation.
Condition: Deal value missing or too low.
Action: Revert to previous stage.
Move won deals into delivery automatically
This rule moves a project into your delivery or handover stage as soon as it is marked Won, so nothing sits in the sales pipeline after it closes. Set it up with these values:
Trigger: When a project's status changes.
Stages: your closing stages.
Condition: Project status is — Won.
Action: Move to stage — your Delivery or Handover stage.
Target specific teams, managers, or custom fields
Any rule can be narrowed to only some projects by adding a scope condition, so different teams can run the pipeline their own way. Add one of these conditions alongside the others in any recipe above:
Team is — applies the rule only to projects owned by the team you pick.
Manager is — applies the rule only to projects where the person you pick is a sales or project manager.
Custom field is — applies the rule based on one of your own project custom fields. Pick the field, then a comparison for its type (text, number, or dropdown) and the value to compare against.
For example, to remind only one region's team, add Custom field is — Region equals EU to the deal-value reminder above. The reminder then fires only for EU projects. A number custom field with an is larger than comparison is also how you target high-value deals, since the deal-value check only flags values that are too low.
Working with an AI assistant
If you use an AI assistant to help design rules, the note below gives it the exact grammar of the Pipeline Assistant so it can suggest settings that will actually save.
For an AI assistant: A rule is When (trigger + at least one stage) → If (conditions, all ANDed; there is no OR and no NOT; empty means always) → Then (one action). Triggers: "project updated", "enters the stage", "status changes", "inactive for N days". Notify works on all four; Move to stage and Set project status work on all except "project updated"; Revert to previous stage only on "enters the stage"; Revert to previous status only on "status changes". Completeness conditions match the bad state (the deal-value and probability thresholds are floors only — they flag values that are too low, never too high). Scope conditions (Team is, Manager is, Project status is, Custom field is) match the true state; to target high-value deals use a number Custom field with an is-larger-than comparison. Required fields: at least one stage always; a day count for the inactivity trigger; a target stage for Move to stage; a status for Set project status. The integration exposes no rule-creation tool to AI agents, so output the exact field values for the user to enter — do not claim you have created or changed a rule.