Take 10 minutes.
Get hours back every week.
Short walkthroughs that turn the platform into your operations team: automated pipelines, instant follow-ups, AI-handled admin. One video, one less thing to do manually.
Email a dashboard as a Report Digest
Three ways to email a reporting dashboard as a digest — the Send Report button, the send_report_email automation action, and the inline {{report:UUID}} token.
Reporting dashboards are more useful when they land in your inbox automatically. With TrustPager's Report Digest feature you can send any dashboard as a formatted email snapshot — on a schedule, triggered by an automation, or on demand. A common use case: a daily digest that lands in your team's inbox each morning with yesterday's pipeline activity, so everyone starts the day on the same page without logging in first.
Three ways to send a dashboard
There are three surfaces depending on how you want to trigger the send:
- Send Report button — one-off send from the dashboard page itself. Good for ad-hoc sharing.
- send_report_email automation action — fires as part of an automation (e.g. every morning at 8am, or when a stage changes). Best for recurring digests.
- {{report:UUID}} inline token — embed a dashboard snapshot inside any existing email body. Good when you want the report alongside other content in an email you're already sending.
Setting up the automation action
Go to https://app.trustpager.com/auto/automations and open an existing automation (or create a new one). Add a new action and choose Send Report Email from the action list.
The action wizard has these key fields:
- Dashboard — pick the dashboard you want to send from the dropdown. The picker shows all dashboards in your workspace.
- Email provider — choose TrustPager Mail (always available) or Gmail (only if your workspace has a Gmail account connected at https://app.trustpager.com/settings/email). If Gmail is greyed out, connect an account there first.
- Recipients — who the digest goes to. You can target a specific team member, a role, or use the dynamic variable
{{user_id}}in the Recipient User ID field to send each team member their own personalised view. When{{user_id}}is set, cards that are scoped to a specific person (e.g. "my open opportunities") will reflect that person's data rather than the workspace total. - Intro / Outro — optional text that appears above and below the dashboard snapshot in the email body. You can load a previously saved template from the template picker at the top of the modal, or type directly and save for reuse.
- Skip when dashboard is empty — defaults to on. When enabled, if the dashboard has no data the action is skipped entirely and logged as a successful no-op (it won't show as a failed run). Turn this off if you want the email to send regardless.
Save the action and publish the automation. The digest will fire whenever the automation trigger fires.
Controlling which columns appear in table cards
Each table card in a dashboard has its own column list. You can control exactly which columns appear — and in what order — by editing the card's display_config.columns setting. This is separate from the card's query dimensions (the data groupings that determine what rows appear).
The distinction matters:
- query_spec.dimensions — the fields the query groups by (e.g.
["stage", "owner"]). These determine what rows are returned. - display_config.columns — the ordered list of columns the email renderer actually shows. A field can be in
query_spec.dimensionswithout appearing as a column, and vice versa for computed or aggregate columns. You can also rename a column label here without touching the underlying field name.
To update a card's column list via the MCP AI agent, use the update_report_card tool:
update_report_card(
card_id: "<card-uuid>",
display_config: {
columns: ["stage", "count", "total_value"]
}
)Pass only the columns you want shown, in the order you want them left to right. Omitting a field from columns hides it from the digest email without removing it from the underlying query.
The client virtual dimension (tasks data source)
The tasks data source has one virtual dimension: client. It resolves to whichever of contact_name or deal_name is present on the task row — a single human-readable label for who the task is about. It is computed after the query runs rather than being a real database column.
To include it in a tasks table card, add "client" to query_spec.dimensions alongside your other dimensions:
update_report_card(
card_id: "<card-uuid>",
query_spec: {
dimensions: ["due_date", "client", "status", "priority"]
}
)Because client has no corresponding database column, it is silently skipped in SQL WHERE and ORDER BY clauses. This means:
- You can include
"client"inquery_spec.dimensions— it works fine. - You cannot use
"client"inquery_spec.filtersorquery_spec.order_by— it will be silently ignored.
Multi-field sort
Table cards support sorting by more than one field. Set query_spec.order_by to an array of { field, direction } objects. The compiler applies them left to right — the first entry is the primary sort, the second is the tiebreaker, and so on. The alias query_spec.sort is also accepted for compatibility with older cards.
update_report_card(
card_id: "<card-uuid>",
query_spec: {
order_by: [
{ field: "due_date", direction: "asc" },
{ field: "contact_name", direction: "asc" }
]
}
)A single-object form is also valid: order_by: { field: "due_date", direction: "asc" }.
Inline report token
If you're already sending an email via an automation and want to include a dashboard snapshot inline — rather than a standalone digest — use the {{report:UUID}} token anywhere in your email body.
To find a dashboard's UUID, open it at https://app.trustpager.com/operations/reporting and look at the URL bar — it will read https://app.trustpager.com/operations/reporting/<UUID>. Copy the UUID from the URL and drop it into your token: {{report:abc123-...}}.
Use the inline token when the dashboard is supplementary context within a broader email. Use the dedicated Send Report Email action when the dashboard is the whole point of the email.
Sending a one-off report from the dashboard
On any dashboard at https://app.trustpager.com/operations/reporting, click the Send Report button in the toolbar. This opens the same Send modal — choose a provider, add recipients, add an optional intro, and send. The email goes immediately. Saved templates from previous sends are available in the template picker at the top of the modal.
Troubleshooting
- Your daily digest is missing some days. This is the suppress-if-empty setting doing its job. On days where the dashboard had no data, the action was skipped (and logged as successful). If you want the email every day regardless, open the automation action and turn off Skip when dashboard is empty.
- Gmail is greyed out in the provider dropdown. Your workspace doesn't have a Gmail account connected. Go to https://app.trustpager.com/settings/email and connect one, then come back to the action.
- Cards in the digest show no data for the recipient. If your cards are scoped to a specific user and you are sending to multiple people, make sure Recipient User ID is set to
{{user_id}}on the action. Without it, the digest renders as a generic workspace view rather than each person's own data. - The emailed table shows the wrong columns — it's still showing the old fixed set. Prior to 2026-05-17 the email renderer used a fixed five-column layout and ignored what individual cards requested. If your digest was set up before that date, re-run it once (trigger the automation or use the Send Report button) and the renderer will pick up the
display_config.columnsyou've configured.
Two ways to
meet FinalPiece.
Talk to Evie right now, or book a real human for a deeper walkthrough. Whichever feels right.
Pick up the phone.
Hear her in 10 seconds.
- RealHer voice passes for human.
- SmartKnows your prices, hours, and trade.
- PatientPolite, attentive, never has a bad day.
Pencil us in.
60 minutes with a real human · Google Meet · Free.