Poppi briefings

A Poppi briefing is an AI-powered step on the canvas that pulls live data from your connected integrations and shows it to staff as a short, written summary before they fill in an element. It is one-way information, designed to give the worker the context they need to do the next step well.

What a Poppi briefing is for

A briefing reads the data sources you enable, then composes a contextual message based on your prompt. The worker sees it as the first thing on the screen when they open that part of the workflow.

Good fits include:

• Showing today's open Shopify orders above a "Pre-shift kitchen check" element so staff know what to prep first
• Pulling today's Google Calendar events above a meeting summary element so the worker knows which meetings to write up
• Surfacing yesterday's unresolved chat threads above a handover element so the next team picks up where the last one left off
• Reminding staff who is on the team today and what their roles are before a daily briefing element

If you find yourself writing the same context paragraph by hand every day, a briefing is probably the right tool.

Where a briefing sits on the canvas

A briefing attaches to a single element or group on the canvas and lives to the right of that node as a satellite. It does not change what staff have to fill in, it just adds context above it on the mobile screen.

The briefing has one connection only — to its parent element. It does not branch, it does not route anywhere else, and it is read-only for the worker.

How to add a Poppi briefing

You add a briefing from the element or group it should attach to.

1. Right-click the element or group on the canvas, or click the plus menu on the node
2. Pick Briefing from the list
3. A new Poppi briefing node spawns to the right of the parent, already connected
4. Click the new node to focus it and fill in the fields

The header on the new node reads Poppi (AI) briefing with an orange background, so you can tell it apart from other node types at a glance.

Configuration fields

The briefing node has two fields to fill in.

Prompt (textarea, required)

This is where you tell Poppi what the briefing should say. The label reads Tell Poppi what information should be added to the [element-type] node, with the element type filled in based on which element the briefing is attached to. For example, a briefing attached to a text input element shows Tell Poppi what information should be added to the text input node.

The placeholder text reads: e.g. Brief the worker on yesterday's open issues, today's team, and any calendar meetings they're invited to.

Write the prompt in plain English. Poppi reads your prompt at runtime, looks at the data sources you have enabled, and composes the briefing.

Data sources (multi-select checkboxes)

This is the list of connected integrations Poppi is allowed to read from when it builds the briefing. Only services with active connections appear in the list, plus Pilla itself which is always available and marked Always on.

Tick every service you want Poppi to consider. Poppi will only query the ones you select, so leaving a service unticked means it will be ignored even if connected.

How a briefing renders on mobile

When a worker opens the element the briefing is attached to, the briefing appears as a full-width information card above the element. It is read-only. The worker cannot tap, edit, or dismiss it, they just read it and then fill in the element below.

The briefing runs once when the worker first opens the element. It is not refreshed if they leave and come back later in the same workflow run.

Plan requirements

Briefings that read from external integrations like Slack, Google Calendar, Google Drive, Shopify, or WhatsApp need a Pro or Enterprise plan, because those integrations are gated by plan. A briefing that only uses Pilla as a data source is available on any plan.

Tips

• Keep the prompt short and specific, "show today's open orders from Shopify" works better than "tell the worker everything they need to know about today"
• Tick only the data sources the prompt actually needs, every extra source adds latency and noise
• If a service is not in the data sources list, it is not connected yet, head to the Integrations page to connect it before adding it to a briefing
• If a data source becomes disconnected after you have set up the briefing, the briefing fails silently for that source, the rest of the briefing still runs with whatever sources remain connected
• Briefings are one-way, so if you need staff to make a decision based on the context, pair the briefing with a Poppi decision in the same workflow