How to Automatically Email Tableau Reports as Excel Attachments

ATRS can export a Tableau report to Excel and email the workbook on a recurring schedule. You save the reporting instructions once, then use that job to produce and deliver the next file.

Imagine it is Monday morning. Finance needs last week's branch sales before its weekly review. The figures are already in Tableau, but someone still has to download them, put them into the familiar spreadsheet, rename the file and send it to the team.

None of those tasks is especially difficult. Together, however, they create a small deadline that comes back every week. A late download delays the review. A file with an unclear date prompts another email. When the usual analyst is away, someone else has to remember the routine.

For this example, the goal is a weekly sales workbook that arrives before the meeting, with the figures in the layout finance already uses.

Why the usual subscription is not the same thing

Tableau's native subscriptions deliver PNG or PDF snapshots. Those formats work well when someone wants to read a dashboard in their inbox. Our finance colleague needs to sort rows, reconcile sales and add review notes, so the attachment needs to be an Excel workbook.

Tableau also supports authorized crosstab downloads. For an occasional spreadsheet, that may be sufficient. The recurring work here includes preparing the workbook and emailing it, which is where we will use ATRS.

Start with the file, not the settings

Ask finance for the spreadsheet it wants to receive. Perhaps the downloaded table is already suitable. Perhaps the team has a workbook with a title, formulas and space for notes. Seeing that file makes the first choice much easier: generate a straightforward XLSX, or place fresh data into a prepared template.

Keep the request concrete: “Last week's sales by branch, in our Weekly Sales workbook, emailed before Monday's review.” That gives every later setting a purpose. You are replacing a familiar routine, not asking colleagues to invent a new way of working.

Before opening the schedule wizard, decide how much preparation the spreadsheet needs. ATRS provides two Excel output choices. Both create XLSX files, but they serve different workbook requirements.

The name “Data Only” can be misleading: it does not mean the workbook must be unformatted. Its additional controls help prepare tabular data for the way the recipient uses Excel.

Put the weekly figures into finance's familiar layout

For our example, finance chooses a template. The worksheet is called “Weekly Sales,” the title occupies the first two rows, and the table starts at cell A3 beneath it. Review notes belong to the right of the table, where the team can discuss unusual results during the meeting.

In ATRS's data-only output settings, select the template, the target worksheet and the starting row and column. You can also configure selected row or column totals and column formats. Give those controls a practical purpose: dates should read as dates, sales should be usable numbers, and branch identifiers should stay recognizable.

Here is a small example of the information finance expects in the completed workbook. These are illustrative values; the actual output must be checked against your selected Tableau data.

The three sample amounts total 47,000.00. In a real delivery, an agreed source total like this gives finance a quick reconciliation point. It also makes a missing branch easier to spot than a visual inspection of the attachment alone.

Leave room for the next week's data

A template that looks right with three rows may need more space later. Try a longer and a shorter sample, and look at the formulas and notes around the inserted table. Establish how your chosen template handles changing output size before making it recurring.

Keep the accepted workbook. When finance asks for an extra column next month, you will have a clear reference for what should change and what should still work.

Once you know what finance should receive, build the ATRS job that produces and emails it. For one report going to the same audience each week, use an ATRS Single Schedule.

Connect Tableau and select the source

Add and verify the Tableau account in ATRS's Integrations library. This connection identifies the server, site and account used to access the report. Follow the authentication requirements for your deployment, and have the Tableau administrator confirm the export account's access.

Then create the Single Schedule, select that account and choose the report item. Give the job a recognizable name, such as “Weekly branch sales — finance.” The name should help a covering colleague find it without opening several unrelated schedules.

Set the report values that determine the export. In our example, the selection must cover the agreed branches and the previous reporting week. Preview the result at this point. It is easier to resolve a period or branch-selection problem here than after a spreadsheet has reached the whole team.

Make the reporting period move with the schedule. A fixed date entered for the first sample will not, by itself, become “last week” on every later run. Establish how the selected Tableau report and your schedule will supply the changing period, and verify the next period as part of the initial setup.

Give the email enough context to be useful

Add an Email destination and choose the required Excel output. Set the finance recipients and the configured sending account, then write the message they will receive. ATRS supports plain-text and HTML messages, so a short, readable email is enough; elaborate formatting is optional.

Our example email could look like this:

Subject: Weekly branch sales — week ending 18 October

The attached workbook contains last week's sales by branch for Monday's finance review.

Please add any review notes beside the relevant branch and contact the reporting team if the figures need investigation.

Attachment: Weekly-Branch-Sales-2026-10-18.xlsx

The attachment name and subject identify the period covered by the data. A run timestamp can help distinguish files, but finance should not have to infer the reporting week from the time an email was sent.

Set the weekly run

Choose the appropriate recurring frequency in ATRS, then allow enough time between source-data readiness and the meeting. Custom calendars are available when the reporting timetable needs specific business dates.

If export must wait for another process to finish, define that dependency as part of the workflow. A Monday eight o'clock schedule is a delivery timetable; it is not proof that the overnight data load succeeded.

Before relying on unattended execution, check the current ATRS host and Office prerequisites and the service account's access to the template and mail resources. Keep those technical setup details with the administrator, so the reporting owner can concentrate on the source, workbook and audience.

Our finance group receives one workbook containing all three branches. That is a simple shared delivery. Now suppose the branch managers also want the figures, but each manager should receive only their own branch.

Forwarding finance's workbook to everyone would change the audience without changing the data. Instead, maintain the relationship between each recipient and the report values used to produce their file.

Use a data-driven schedule when the instructions vary

ATRS Data-Driven Schedules can read reporting instructions from database tables or queries at run time. Those instructions can supply parameters, destinations and output choices. For this extension of our example, each maintained record associates a manager's email address with the branch value their report should use.

North's manager receives North's workbook; South's manager receives South's. The reporting design stays consistent while the selected values and recipient change. When a manager moves roles, the maintained record becomes the place to update the relationship.

This is where an automated export becomes a useful distribution process. You are no longer asking someone to open the report, change a branch, download a file and compose another email for every person on the list.

Keep authorization separate from the mapping. The organization still needs to decide who may receive each branch's data. A database row containing an address and a parameter value supplies instructions to the job; it does not establish that the person is entitled to the information.

Choose how to maintain the audience

For a stable shared report, ATRS's email destination can use addresses entered directly or selected from maintained recipient sources. For a changing, personalized audience, database-driven instructions can keep addresses and report values together.

The important choice is which source the responsible team can keep current. Include removals as well as additions: a departed manager should not remain on a recurring distribution simply because the reporting job continues to run.

For confidential workbooks, choose the file protection required by your organization. ATRS documents workbook-password and encrypted-file options. Include the recipient's opening experience in the first delivery review, especially when the attachment will travel outside your organization.

You can leave this extension until it is needed. First establish finance's shared workbook, then add personalized deliveries when there is a clear audience and reporting scope for each one.

The most useful first test is the ordinary one: finance opens the attachment and uses it for the weekly review. Does the file contain the expected branches and dates? Can the team sort the figures and add its notes without rebuilding the spreadsheet?

Make that received workbook the reference. It connects the source data, ATRS settings and recipient's task in a way that a successful export message alone cannot.

Use one short acceptance check

• Data: the branches, period, rows and agreed control total match the selected Tableau result.
• Workbook: the worksheet, columns, formats, formulas and review areas work in the received file.
• Email: the intended recipient receives the attachment with a clear subject, filename and message.
• Next run: the next reporting period and the unattended configuration produce the expected delivery too.

For the sample table, the total is 47,000.00. If the received file differs, start with the selected period and branch scope, then trace the export if those are correct.

Know where to look when Monday's file is missing

ATRS System Monitor provides a History View for examining schedule results. When a destination fails, expand the result to identify the affected report or destination. A job with several destinations can be partially successful, so establish which delivery failed before repeating the whole run.

The Retry View shows failed schedules configured to retry. It helps the reporting owner find jobs still awaiting a successful run or attention. If ATRS records a send but finance cannot find the message, investigate the mail path with the mail administrator rather than repeatedly regenerating the workbook.

Also agree what “nothing to report” should look like. Finance may prefer an explicit notification to an unexplained absence. Configure and test the appropriate exception behavior for your installed build, with an owner who knows what should happen.

Keep the routine easy to hand over

Once the job is working, record where its Tableau source, template and recipients are maintained. Revisit the accepted sample when any of them changes. Adding a branch, renaming a column or revising a formula is a reason to review the affected output, not to repeat every setup decision from the beginning.

The result should be a routine that finance can recognize and a covering colleague can support: the right week's figures, in the familiar workbook, arriving before the meeting.

To try this with your own report, explore ATRS for recurring Tableau Excel reports and template workbooks. Bring the spreadsheet your team wants to receive. Its layout and the work people do with it will give the evaluation a useful starting point.