How Do You Schedule Tableau Reports by Email?
Every Monday, someone exports the sales update, attaches the files and writes much the same email. The team is waiting for the report while the analyst repeats the preparation.
Advanced Tableau Report Scheduler (ATRS) can prepare those Tableau Cloud files and deliver the email, including the workbook and related reports readers need.
- THE PROBLEM AND ANSWER Make Monday’s report email useful to its readers
- YOUR OPTIONS Give each reader the right files and message
- SET IT UP Set up the email once, then let ATRS repeat it
- FOR DEVELOPERS Let your application request the prepared email
- YOUR NEXT STEP Have the Monday update waiting in the inbox
Make Monday’s report email useful to its readers
The operations analyst starts Monday with the sales dashboard and a list of people expecting the weekly update. The managers want a quick view of the figures. Finance wants the workbook it can reconcile.
At first the handoff is manageable: export, attach, write the message and send. As another report or regional version is added, more of the morning goes into preparing the email.
A native Tableau subscription may already cover the managers’ image or PDF. Keep that route when it gives them what they need.
ATRS helps with the work left around it. It can prepare finance’s Excel file, assemble related reports and send a recognizable message from the configured account, so the analyst can turn to the questions behind the figures.
Choose the deliverable first: a snapshot, a document to retain or data the reader can work with.
What native Tableau subscriptions cover
Tableau’s subscription guide covers scheduled PNG images, PDF attachments or both. Choose the current view or entire workbook, with PDF paper size and orientation where needed.
Save a custom view when the subscription must retain filters; temporary browser selections do not define it. Recipients need the required view and image/PDF download permissions, and subscribing other people depends on your role and ownership.
Group membership is captured when a subscription is created. New members need the group subscribed again; removing someone from the group does not automatically remove their subscription unless their access to the view is removed. Review that behavior when your audience changes.
Native subscriptions are available in Tableau Cloud and Tableau Server. Server administrators also manage the subscription email configuration. ATRS connects to Tableau Cloud only.
Ask what readers do next
A quick management review and a finance reconciliation need different files. The readers can explain which preparation matters.
Give each reader the right files and message
Use the email readers already find useful as your starting point. A clear subject identifies the week, and the message tells people what they are receiving and what needs their attention.
ATRS can maintain HTML or plain-text messages with inserts for changing values. Its recipient options include address books, database queries and text mailing lists, so the audience can come from a source someone already owns.
When regional managers need different figures, keep the regional inputs and recipients together in a data-driven schedule. When finance needs Sales and Returns together, use a package to send their attachments or merge the workbook. Each capability takes over a piece of the analyst’s existing Monday work.
Email lists, embedding and delivery options
The Email destination guide documents To, CC and BCC, address-book contacts/groups, database queries and one-address-per-line text files. If a list is maintained in Excel, use a supported data-source connection or publish its addresses to one of those documented inputs; do not assume an XLSX file can be selected as a text mailing list.
Use a data-driven schedule when records should control parameters, output formats and destinations as well as recipients. Review the mapping with sample outputs before sending the full set.
For a report in the email body, choose Embed Report. Enable Include Attachment when a file should accompany the embedded report; embedding alone does not add an attachment. HTML embedding uses SMTP, while MAPI embedding is limited to text.
Choose the configured sending account. ATRS supports SMTP and Office 365 accounts, including documented MSAL authentication options. A changed display sender does not grant permission to send from that address.
For several reports, follow the package schedule guide. Separate attachments, ZIP, merged Excel and merged PDF suit different readers. Grouped outputs in data-driven packages are attachments rather than embedded report bodies. Mail-provider size limits still apply.
Use a list with an owner
Choose a maintained recipient source, then keep the reporting assignments connected with the people who hear about team changes.
Set up the email once, then let ATRS repeat it
Begin with the sales report and your own test mailbox. Select the Tableau Cloud account and report in an ATRS Single Schedule, and use a week whose figures you know.
Add the Email destination and prepare the output. Write the message you would otherwise send by hand, identifying the reporting week and the files finance should review.
If the workbook needs a template, useful tab names or number formats, include that preparation now. Add the related reports as a package when the review calls for them.
Open the received email with its reader. Look at the file and the task it supports, then choose the recurrence and reporting-period rule. Agree who hears about a failed or unexpectedly empty report before making the routine part of Monday morning.
The Email destination in ATRS. Set the recipients, message, output format and mail server for your reporting job.
Excel preparation that can travel with the email
The ATRS Excel guide covers MS Excel and MS Excel Data Only XLSX outputs. Both offer worksheet naming, workbook passwords, file properties and output naming. Data Only adds template placement on a chosen worksheet, a starting row/column or the next available position, selected totals, reusable styles and column data types/custom formats.
These controls let finance receive a prepared workbook: recognizable tabs, useful number/date formats and data placed where the existing template expects it. Check the resulting cells and totals in Excel, including shorter and longer reporting periods.
File names can use inserts and date/time suffixes. Configured ZIP encryption, PGP encryption and deferred delivery add protection or control when the prepared output is released. Confirm that recipients can open or unpack the result.
The Files & Folders tasks can merge existing Excel files and adjust workbook password, read-only and summary properties. Build Excel Workbook can assemble database query results into a workbook; it is a separate database task, rather than an extra Tableau export mode.
Use the current ATRS installation prerequisites for the supported Office version, and make the templates and file locations available to the scheduling service. Test the finished attachment through the actual sending route.
Read the first email together
Finance can show you whether the workbook is ready for its next task, and whether the message makes the week clear.
Let your application request the prepared email
The operations portal may need a way to send another update after the figures are approved. It can request the saved ATRS job, with the email and files still maintained by the reporting team.
The application follows the requested run so operations can find the particular update someone is asking about.
API example: request and monitor the prepared email
Use the ATRS execution guide and operation contracts. This example runs an existing ordinary single-report schedule. Replace 101 with its actual UniqueId and use your ATRS HTTPS address. Keep the bearer token on a backend that authorizes the requested reporting job.
POST /api/Schedule/ExecuteScheduleAsync
Authorization: Bearer <ATRS-access-token>
Content-Type: application/json
{
"ScheduleType": "report",
"UniqueId": 101,
"RunBy": "Operations application"
}
GET /api/Schedule/GetExecutionStatus?ExecutionId=<returned-id>
Authorization: Bearer <ATRS-access-token>Save the returned ExecutionId with the application request and poll GetExecutionStatus within a defined limit. Parse the JSON-encoded ResultJson: Completed can still contain Result=false. Check the output and destination evidence before reporting success.
The execution call uses the saved reporting configuration. It does not take a new recipient list or reporting period in this payload, and it does not return the attachment bytes. For a package, use the documented package schedule family and its actual identifier.
After an uncertain response, reconcile the execution and destination before retrying to avoid sending the update twice. A mail server accepting a message also does not prove that a manager has read it.
Keep the extra update easy to find
Save the request and execution reference so a colleague can follow the particular email operations asked for.
Have the Monday update waiting in the inbox
The weekly email can be waiting when the readers begin their work. Managers have the snapshot they need, finance has its workbook, and the analyst has time to help explain an unusual result.
Start with one email you currently prepare by hand. Use its report, audience and attachments to explore how ATRS can take over the recurring handoff.
Contributors:
Christian Ofori-Boateng
CEO, ChristianSteven Software

