Skip to content
Supaboard

Automations

Your reporting, running without you

Set a question to run on Monday morning, or the moment a number crosses a line. The answer arrives already written up, as an email, a deck or a spreadsheet.

Weekly Revenue Digest
Path 1Path 2
1Every Monday 9am
2Generate AI summary
3Check revenue drop
4Send email
5Post to Slack

Trusted by 1,000+ businesses across the world

  • Jindal Healthcare
  • Shopee
  • NetEase Games
  • Holcim
  • Publicis Sapient
  • Nilfisk
  • ClickBus
  • AAA
  • Scopely markScopely
  • FunPlus
  • Bilt
  • GlobalSign
  • Katalon
  • StockGro
  • Yami
  • Immutable
  • Plane
  • Gabriella
  • Visily
  • Poka
  • Trafilea

The recurring report is a job nobody applied for

A chat thread where a data request waits days for an analyst's reply

Someone rebuilds it every Monday

The same pull, the same paste, the same formatting, by a person who was hired to do something else.

Stacked database discs frozen mid-refresh

The spike is found in the review

Nobody watches every metric daily, so a bad week gets discovered three weeks later.

Disconnected database and platform shapes scattered across a grid

The report lands where nobody looks

Insight that arrives in a tool people don't open is the same as no insight.

Set it once. It keeps running.

Run it on a clock, or on a change

A schedule covers the reports you already know you need. An alert covers the ones you don't: it watches a query and fires the moment the result crosses your line — then the rest of the chain investigates and writes it up before anyone has opened a tab.

  • Daily, weekly, monthly or a precise time
  • Alerts that fire on the change, not the check
  • Paused and edited without rebuilding
A three-step automation: an alert on revenue collection falling under $10k, a deep-research step finding the root cause, then an email sending the analysis

More than one step

Chain the work: query the database, ask an analyst about the result, summarise it, split on a condition, loop over every row, build the file. 17 blocks, joined in the order you want.

  • 17 building blocks
  • Conditions and loops
  • Exports to 3 file formats, and a webhook out
The block catalogue: answer questions with AI, summarise insights, ask analysts, query your data, send email, and export a dashboard as PDF or PowerPoint

Every run leaves a record

Each run is listed with what triggered it, when it started and whether it finished, and the result it produced is one click away. When a step fails, the log says which step and why.

  • Every run timestamped, with its status
  • The output of a run kept alongside it
  • A failure names the step, not the chain
An automation run log listing plan-purchase, weekly-revenue and high-risk-user runs, each timestamped, marked completed and linking to its results

What runs on its own

  • 17 Building blocks

    Queries, analysts, conditions, loops, exports and sends.

  • 3 File formats it hands you

    PDF, PowerPoint and Excel, built from the run itself.

  • 0 People running it on Monday

    Once it is set, the report writes and sends itself.

Frequently asked questions

What can I automate?

Anything you can ask an analyst, plus the steps around it: run a query, summarise the result, branch on a condition, loop over rows, build a file, send it.

How do alerts work?

An alert watches a query on an interval and compares each result to the last. It fires when the answer changes, so a quiet week stays quiet.

Where do results go?

Email, or a webhook into whatever else you run. An automation can attach a PDF, a PowerPoint or an Excel file built from the same run.

Do I have to draw a workflow?

Only if you want to. A single scheduled question is one block. Conditions, loops and multi-step chains are there when the job gets bigger.

What happens if a step fails?

The run stops at the failing step and records where and why, so you fix that step instead of re-reading the whole chain.

Your data has the answers

Start free trialBook a demo