Feeds

The client UX layer for every workspace project.

Feeds turn workspace data and automation results into the artifact each audience needs: a dashboard for leaders, a briefing for an operating team, a statement for a customer, a document for review, or an alert when something changes. Groups decide who receives what.

How agents use feeds

Ops Director→Morning Briefing07:30 daily

Supervisor→SLA Alerton trigger

Board→Performance Scorecardmonthly

Customer→Order Status Updateon milestone

Finance→Account Statementmonthly

Vendor→Compliance Documenton event

Planning→Demand Forecastmonthly

Care Manager→Risk Briefing07:00 daily

Ops Director→Morning Briefing07:30 daily

Supervisor→SLA Alerton trigger

Board→Performance Scorecardmonthly

Customer→Order Status Updateon milestone

Finance→Account Statementmonthly

Vendor→Compliance Documenton event

Planning→Demand Forecastmonthly

Care Manager→Risk Briefing07:00 daily

Automated Intelligence Delivery

The briefing arrives before the meeting. Always.

Zipdata generates the right output for each person in your operation. The ops director gets the morning briefing. The supervisor gets the alert. The customer gets the status update. The board gets the scorecard. Automatically. On cadence. Without anyone assembling it.

A morning in manufacturingHow the briefing builds itself before 8am

06:30OTIF Agent fires

Scans 14 orders within 48h of delivery window

06:45Risk flags queued

At-risk orders identified by production stage

07:00Briefing generated

KPI summary + exceptions + recommended actions

07:15Briefing delivered

In the ops director's inbox — before standup

08:00Actions approved

One-click approval on escalation drafts

See all 12 output types →

Why Feeds

Feeds connect all three solution paths to the people using them.

Unified data projects need dashboards and reports. Automation projects need generated documents, statements, and updates. Agentic projects need briefings, alerts, and approval-ready outputs. Feeds give each path one delivery model.

Static dashboard

–Best for live exploration and standing views
–Usually designed for internal users
–Requires the reader to visit the product
–Often separate from document or email delivery
–Does not naturally personalize by audience

Feed

✓Works for dashboards, briefings, reports, alerts, and documents
✓Formatted for the group receiving it
✓Generated from workspace data or automation output
✓Scheduled, shared, or trigger-based
✓Can reach internal and external audiences

Feed Types

From a board scorecard to a customer status update — one generation engine.

All twelve feed types are generated from live workspace data and formatted for their audience. Internal feeds stay inside the workspace. External feeds go to customers and stakeholders.

internal

Internal operating rhythm

Briefings, dashboards, scorecards, alerts, reports, and forecasts for the people running the operation.

daily

Briefing

The 07:30 operational briefing: KPIs, exceptions, and recommended actions for the leadership team.

daily

Dashboard

Live KPI grid updated from query data — production throughput, SLA status, fill rate, OTIF.

monthly

Scorecard

Metric performance table against targets — board-ready, versioned, and auto-generated.

trigger

Alert

Fires only when the watch condition is met — threshold breach, anomaly, or critical exception.

weekly

Report

A sortable, filterable table of any workspace entity — orders, jobs, accounts, and more.

monthly

Forecast

Projection chart from current trend data — shipment volume, revenue, demand, or workload.

external

External stakeholder outputs

Customer updates, documents, commercials, statements, and promos generated from the same live record.

trigger

Customer Update

Status card sent directly to the customer when an order or job milestone is reached.

trigger

Document

Formal letter, certificate, or compliance document generated from a template and workspace data.

trigger

Commercial

Line-item commercial output — quotes, invoices, or proposals generated from entity records.

monthly

Statement

Transaction statement with running balance — for collections, property, or financial services.

trigger

Promo

Promotional communication generated from customer segment data and offer configuration.

mixed

Shared notifications

Compact updates that can route internally or externally depending on the trigger and audience.

trigger

Notification

Compact header notification for internal or external audiences — status change, confirmation.

Generation Flow

Generated from live data. Shaped for the audience. Delivered on your cadence.

No copy-paste, no manual template filling, and no dashboard that waits for someone to remember it. The briefing is built from current data and saved as a versioned artifact.

Query fires

The linked analytics query pulls live workspace data — orders, jobs, accounts, or KPI snapshots — at the scheduled time.

The feed builds itself

Feed Studio takes the query results and assembles a complete, self-contained feed — charts, tables, narrative, and recommended actions — shaped for the audience it is going to.

Auto-saved and versioned

The artifact is automatically saved to workspace-documents storage. Every version is immutable and linkable.

Tasks schedule delivery

Tasks hold the committed delivery cadence — daily, weekly, monthly. The feed arrives before the meeting that depends on it.

Groups receive delivery

Workspace groups define the audience. Members get the briefing in their inbox. External recipients get a secure share token.

Agent Output

Feeds are how agents communicate with humans.

When an agent detects an anomaly, runs a scheduled program, or prepares an escalation, its output becomes a feed: drafted, approved, scheduled, delivered, and logged.

OTIF Agent

Trigger fires

OTIF drops below threshold and 14 orders are within 48 hours of expected delivery.

Feed Studio

Briefing generated

The agent creates an exception feed with charts, records, root-cause notes, and a recommended action.

Governance

Approval enforced

Internal briefing is auto-drafted. Customer-facing escalation waits in Pending Actions for one-click approval.

Delivery

The right feed to the right person at the right time.

Scheduling is the contract: the feed arrives before the operating cadence that depends on it.

Committed delivery schedule

Daily, weekly, or monthly with a committed send time. The ops briefing arrives at 07:30 every working day — not when someone remembers to send it.

Audience groups

Workspace groups define who gets what. Leadership gets the briefing; the board gets the scorecard; customers get the update. One workspace, many audiences.

External share tokens

Recipients outside the workspace get a secure, time-limited share link. No login required. The link expires on the schedule you set.

Trigger-based dispatch

Some feeds run on cadence; others fire only when a watch condition is met. The same engine handles both with a single configuration model.

Immutable version history

Every generated artifact is saved and linkable. The 14 March briefing is still there in March next year — bit-identical, audit-grade.

Delivery observability

Tasks shows last run, next run, status, and every version. Failures surface immediately; reruns are one click; provenance is always available.

First briefing in 48 hours

See a live operational briefing built from your data.

We configure the workspace, seed realistic data, and deliver the first automated briefing before the demo call.