Poppi decisions

A Poppi decision is an AI-powered step on the canvas that evaluates a yes or no question at runtime and routes the workflow accordingly. Poppi reads the upstream workflow context (what staff have answered so far), plus any data sources you give it, then decides yes or no and follows the branch you have set up.

What a Poppi decision is for

A decision lets the workflow branch based on what actually happened, not just what was scheduled. The question is yours, the answer is Poppi's, and what runs next depends on the answer.

Good fits include:

• Branching after an inspection element, run a Slack action on the Yes branch when everything is fine, run a different action on the No branch when something failed
• Gating a delivery check element so it only runs on days a delivery is booked
• Splitting a workflow into "open as normal" or "open with reduced staff" paths based on yesterday's chat handover
• Routing a complaint element down a "minor" or "major" path based on the photo and the worker's note

If the workflow needs to do something different based on context, a decision is the step that decides what that is.

The two placements

A Poppi decision can sit in two positions relative to the element it is connected to. The placement changes what the decision does.

Right-satellite (Yes / No router)

The default placement. The decision sits to the right of an element. After the element is filled in, Poppi evaluates the question and routes the workflow into one of two branches. The Yes branch (green) goes to the top right and the No branch (pink) goes to the bottom right. Each branch can feed a Poppi action.

This is the right pick when the decision is about what to do AFTER the element is completed, like "post a summary to Slack if everything is fine, send a manager alert if not".

Left-gate

The decision sits on the LEFT of a single node. It is evaluated BEFORE the node runs, when the workflow is set up for the day. If the answer is Yes, the node runs as normal. If the answer is No, the node is skipped entirely and the worker never sees it.

Use a gate for conditional skipping, like "only run this delivery check if a delivery is booked today" or "skip the outdoor inspection if the weather forecast is rain".

If you want to branch the main flow of the workflow itself (not just a follow-up action), use a decision connector instead. See Decision connector.

How to add a Poppi decision

You add a decision from the element it should attach to.

1. Right-click the element on the canvas, or click the plus menu on the node
2. Pick Decision from the list
3. A new Poppi decision node spawns at the chosen placement, already connected
4. Click the new node to focus it and fill in the fields

The header reads Poppi (AI) decision with an orange background. For a left-gate, the header reads Poppi (AI) decision (gate) so you can tell the placement at a glance.

Configuration fields

The fields depend on the placement.

Right-satellite placement

This shows a single prompt field.

The label reads What should Poppi decide? and the placeholder reads: e.g. Were all critical items ticked? Was the photo clean and well-lit?

Write the question as a yes or no question. Poppi reads the worker's answers from the element above, then answers your question and picks the matching branch.

Left-gate placement

A gate has two prompt fields plus optional data sources.

The first field is the gate question itself. The label reads When should this [element-type] node run?, with the element type filled in based on the gated node. The placeholder reads: e.g. Only run if a delivery is booked today, or skip if the weather forecast is rain.

The second field is an optional briefing. When the gate resolves to Yes and the node runs, Poppi can also show a short briefing to the worker explaining the context that made the gate fire. This works exactly like a standalone Poppi briefing, with a prompt and a multi-select of data sources to read from.

Data sources are available on the gate field as well, so Poppi can read live data (today's calendar, today's orders, today's chat) when making the gate decision, not just static workflow context.

How to build out a branch

A right-satellite decision creates two branches, Yes and No. Each branch starts empty.

1. Click the + button on the Yes or No handle of the decision node
2. The only option is Action, so a Poppi action node is added straight away
3. Fill in the new node like you would any other

You can only add one node per branch directly off the decision. If you need more, chain extra nodes off the first one.

How to delete a branch

To delete a branch, remove the edge between the decision and the branch's target node. Once the edge is gone, the + button on that branch reappears and you can add a different node.

Validation warnings

The decision node uses two visual cues to flag problems.

• A red border around the node means the decision is orphaned, usually because the branch is not connected to anything
• The test button (the play icon in the header) is disabled if the prompt is empty, the tooltip reads "Add a question first"

Plan requirements

A Poppi decision is available on any plan, the AI evaluation itself is part of the platform. If a left-gate uses external integrations as data sources, those integrations need a Pro or Enterprise plan.

Tips

• A decision is most useful when paired with an action, the decision picks the branch and the action does something useful on that branch
• Phrase the question so Yes is the "happy path", it makes the canvas easier to read at a glance
• Left-gates are powerful for conditional work, use them when you do not want staff to see an element at all on days it does not apply
• If you need the rest of the workflow to fork rather than just a single follow-up action, use a decision connector instead
• Test the decision with the play button before publishing, so you can see how Poppi answers on real workflow data