Haulers can have reports delivered on a recurring schedule instead of opening the platform to pull them. A scheduled export runs the report's underlying query, renders the output in the format you choose, and delivers it to a destination you configure.
This page covers what haulers can schedule and the constraints worth knowing before you build a workflow on top of it. For destination-by-destination setup steps, see the individual guides linked below.
Three delivery modes are available:
- On-demand download — pull a file immediately in the browser.
- Recurring schedule — deliver on a cadence to one or more destinations.
- Manual send of a schedule — trigger an existing schedule outside its normal cadence, useful for backfilling a missed delivery or verifying a new configuration.
Each mode can target a whole report, a single page of a report, or one element on a page. Narrower scopes unlock more granular formats — element-level exports can produce raw tabular output, while whole-report exports are limited to document formats.
| Destination | What you can export | Availability |
|---|---|---|
| Download (in browser) | Whole report, page, or element | Always available |
| Whole report, page, or element | Always available | |
| Slack | Whole report, page, or element | Where your Hauler Hero organization has enabled the Slack integration |
| Microsoft Teams / SharePoint | Whole report, page, or element | Where your Hauler Hero organization has enabled the Microsoft integration |
| Google Drive | Whole report, page, or element | Where your Hauler Hero organization has enabled the Google integration |
| Google Sheets | A single element only | Where your Hauler Hero organization has enabled the Google integration |
Direct-to-cloud-storage and webhook delivery are not available to haulers — those are reserved for internal Hauler Hero reporting. If a destination you need is not listed, contact your Hauler Hero account manager; availability is gated on integration configuration rather than on your account's permissions.
Schedules run against the published report, not your draft. Edits you have not published will not appear in scheduled deliveries. While editing, you can download the draft directly, but that draft is not what a schedule sends. If a hauler reports that a scheduled file looks stale, an unpublished edit is the first thing to check.
Every export issues a fresh query. Precomputed or materialized results are not reused for exports — the export re-runs the query against the warehouse. This matters for cost: a daily schedule on an expensive report is a daily warehouse bill, not a cached read. Consider cadence and report scope accordingly.
Filtered views can leak. If a report uses controls to narrow data — to a single customer, route, or yard — the export reflects whatever the control values were when the schedule was configured. Verify control state before scheduling anything that leaves the platform, particularly for multi-tenant or customer-facing reports.
Size limits apply and vary by format and destination. Large exports can fail rather than truncate. If a schedule stops delivering without an obvious cause, check whether the report has grown past the limit for its format.
Saved views and tagged versions have uneven destination support. Not every destination can deliver an element that exists only on a saved view. Where support exists, the export must generally be configured from within that view rather than from the published report.
- Haulers can review and edit schedules they own or subscribe to, from their profile.
- Schedules attached to a specific report can be managed from that report.
- The organization-wide view of all schedules is retained by Hauler Hero for support and cost review, and is not exposed to haulers.
Scheduled exports are processed by Sigma, Hauler Hero's reporting provider, before they reach the destination you configure. How Sigma handles exported content — including any retention or logging that applies — is governed by Sigma's own export notice, linked below. Review it before scheduling exports of sensitive or customer-facing data.
See Sigma's Notice for exports, reports, and downloads for the authoritative terms.
- Send or schedule workbook exports — upstream reference
- Download and export limitations — current size limits