Pipeline Assistant keeps your sales pipeline accurate on its own. It watches your Cinode projects, checks them against rules you define, and messages the right person whenever a deal is missing information, has gone quiet, or needs a status change — so nobody has to run manual pipeline reviews or chase colleagues for updates.

Its messages reach you inside your chat tool. Pipeline Assistant delivers everything through the Cinode Chat Assistant, so alerts and reminders arrive in Slack or Microsoft Teams alongside your other Cinode chats. There is nothing new to learn: you read the message, click the link, and fix the deal in Cinode.

Pipeline Assistant is an add-on that you install and set up yourself from Cinode Flows, the self-service integration catalogue built into Cinode. Everything happens inside Cinode — there is no separate portal to log in to.

Pipeline Assistant runs a set of rules against your projects and acts on them automatically. Here is what it can do for your team.

When someone updates a project, Pipeline Assistant checks it in real time against the rules that apply to that pipeline stage. If required information is missing or invalid — no deal value, a close date in the past, roles without a rate — the person who made the change gets a message listing exactly what needs fixing, with a direct link to the project in Cinode. Each issue is marked as an error, a warning, or a note.

Each night, Pipeline Assistant looks for open projects that have sat untouched in a stage for longer than you allow. Depending on the rule, it can notify the deal's sales managers, move the project to another stage, or change its status — with no manual follow-up. A stale deal is flagged once and is not flagged again until someone actually works on it, so the same reminder never repeats night after night.

Every Monday at 09:00 (Central European Time), each sales manager receives one summary message covering all of their projects that still have open items. It is a single recap of everything outstanding, so issues never wait a full week unnoticed.

Because it works through the Chat Assistant, you can also act on a deal by asking in plain language. Tell the assistant to move a project to a stage, set its status to Won, Lost, Abandoned, or Suspended, undo a stage move, or run the weekly digest right now instead of waiting for Monday. These actions are available to managers.

Any user can ask the Chat Assistant to subscribe them to pipeline-issue alerts, on top of whatever the rules already send. Ask to unsubscribe at any time. This is self-service and needs no administrator.

Everything Pipeline Assistant does is driven by rules you define. Every rule follows one simple pattern — when → if → then: when something happens to a project in a stage you choose, if a set of conditions is met, then Pipeline Assistant takes an action. Rules are configured per pipeline by a Cinode administrator in the configuration wizard.

The trigger decides when a rule is evaluated, together with the pipeline stage or stages you attach it to. There are four triggers:

Conditions decide whether the rule actually acts. A rule can require any combination of the checks below, and all of them must pass. A rule with no conditions always acts on its trigger. The table below lists every available check and what it requires.

The action is what happens when the trigger fires and the conditions pass. There are three actions:

Notifications work with all four triggers. Moving a project or setting its status can be used with the stage-entered, inactive-for-days, and status-changed triggers, but not with project-updated, because those changes are not made on every save.

For a notification rule, you choose who gets the message:

People are matched to their chat account by email. A user with no email in Cinode cannot be matched, so they are skipped. Nightly reminders for inactive deals have no person who "made the change", so they go to the deal's sales managers instead.

A pipeline is only as useful as it is accurate, and accuracy slips when keeping it clean depends on people remembering to check. Pipeline Assistant removes that dependency.

Pipeline Assistant works through the Chat Assistant and inherits its security model, so the same protections apply to every message and action.

For the full security and privacy model, see Meet the Chat Assistant.

Setup is self-service and happens entirely inside Cinode, in Cinode Flows. An administrator installs Pipeline Assistant from the Flows marketplace and steps through its configuration wizard, which walks you through each part.

Once setup is done, Pipeline Assistant starts working the next time a matching project changes.

Notifications appear in Slack or Microsoft Teams, delivered through the Chat Assistant. Real-time issue alerts go to the person tied to the rule, and the weekly digest goes to each sales manager.

Pipeline Assistant has no other way to deliver, so no messages will arrive until the Chat Assistant is set up for your workspace. If notifications are missing, confirming the Chat Assistant is connected is the first thing to check.

Yes. Add several conditions to one rule so they must all pass, or add several rules to the same stage. All the issues found are combined into a single message.

Yes, by controlling your rules. The weekly digest and nightly inactivity checks only run when you have rules that use them, so removing those rules stops that activity. There is no separate schedule to manage.

Stale-deal reminders are sent once and are not repeated until someone actually works on the project. Once a person updates it, the deal is eligible to be flagged again if it goes quiet once more. The weekly digest still recaps deals with open items.

Only managers. Asking the assistant to move a project, set its status, undo a stage move, or run the digest on demand requires a manager account. Any user can subscribe or unsubscribe themselves to alerts.

People are matched to their chat account by email, so a person whose Cinode email does not match their Slack or Microsoft Teams email, or who has no email in Cinode, cannot be reached and is skipped.