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, including every trigger, the full list of conditions and how to install and set up, see Pipeline Assistant.

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.

Most conditions in these recipes are named after the problem they catch. For example "Deal value missing or too low" matches a deal that has no value. Conditions such as "Project status is" and "Roles staffed" match when something is true.

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.

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:

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:

This rule tells the sales managers when a project reaches a late stage while some of its roles still have no assigned person, so staffing is not left to the last minute. The message names each role that is missing a person. Set it up with these values:

This rule reminds the person who marked a deal as Lost to say why, so you can learn from lost deals later. Both conditions must be true for it to fire. Set it up with these values:

Once reminders feel comfortable, you can let the assistant chase quiet deals on its own and announce important moments to the whole team.

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:

This rule posts to a shared chat channel whenever a project is marked Won, so the team sees each win as it lands. The channel list is currently available for Slack, and the Chat Agent must already be a member of the channel. Set it up with these values:

The most advanced rules let the assistant change a project for you, by moving it, setting its status, or undoing a change that should not have happened.

This rule protects your Won figures by undoing a Won status when the project's roles are not yet assigned. Both conditions must be true for it to fire. Set it up with these values:

This rule sets a project to Won as soon as its roles are staffed, so nobody has to remember to close the deal once the consultants are in place. Set it up with these values:

This rule sends a project back where it came from when it enters a stage it is not ready for. It does nothing if the project has no earlier stage to return to. Set it up with these values:

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:

Combine Pipeline Assistant with the Inbound integration to keep automatically-created projects moving even after Inbound's own matching finishes. Inbound reads incoming assignment requests, creates a project for each one, and matches it against your consultants, subcontractors, candidates and partners. When nothing matches, its No Match Action setting decides what happens next. The recipes below pick up from there, so unmatched or untouched requests do not just sit in your intake stage.

This rule catches every project that Inbound suspended because it found no match, and moves it straight into a separate pipe you review later, so unmatched requests stop cluttering your active pipeline without being lost. Set it up with these values:

This rule flags a project that Inbound created but that has sat in the intake stage without anyone looking at it, so a new request never quietly ages before someone opens it. It needs no condition, because the inactivity itself is the signal. Set it up with these values:

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:

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.

If you use an AI assistant to help design rules, the note below gives it the exact grammar of Pipeline Assistant so it can suggest settings that will actually save.