Skip to content
PulseDeck

Build your own

The five guides are starting points, not a menu. PulseDeck doesn’t know or care what your reports are about — it stores structured blocks and renders them. If something in your world produces numbers, events, or status on a schedule, it fits.

pulsedeck.app / dashboards / your-team

The pattern fits anything

Section titled “The pattern fits anything”

Every guide is the same three moves — and they don’t change with the subject:

  1. Plan the structure — a category and a stream slug for the data.
  2. Send the report — your agent gathers the numbers and POSTs a report of blocks, on whatever schedule makes sense.
  3. Build the dashboard — drop in widgets that read them.

Learn the loop once (start with the Quickstart) and the subject is just data.

More ideas to steal

Section titled “More ideas to steal”

A few directions beyond the five guides — none of these needed a new feature, just a different report:

  • Deployments & releases — every deploy posts status, duration, and what changed.
  • Data-pipeline health — row counts, freshness, and failed jobs per run.
  • Customer support — daily ticket volume, first-response time, CSAT trend.
  • Security & compliance — scan results, exposed-secret alerts, patch status.
  • Content & marketing — publish cadence, traffic, campaign results.
  • Research digests — an agent’s daily reading, summarized into one report.
  • Sensors & IoT — temperature, occupancy, battery — anything with a reading.
  • Finance & ops — invoices, payroll runs, inventory, SLA breaches.
  • Personal automations — your own scripts reporting on themselves.

If it runs on a schedule and has something to say, it belongs in PulseDeck.

Share your use case

Section titled “Share your use case”

Built something with PulseDeck? Tell us — we add the good ones to these docs so others can follow along, with credit to you.

  • Open a discussion or issue on GitHub describing the job, the report you send, and the dashboard you built.
  • A screenshot or your report/dashboard JSON is plenty — we’ll turn it into a guide.

The more scenarios people share, the more useful this section gets for everyone.

Next steps

Section titled “Next steps”