Automate Tableau Report Delivery to Email and File Destinations

Yes. Single schedules can embed a report in the email body and include an attachment. SMTP supports HTML embedding; MAPI embedding is text-only. Data-driven packages use attachments and cannot embed. Grouping single data-driven outputs by email address also disables embedding.

Yes. Use HTML, company logos, images, links, tables and formatted instructions, with default font and size settings for consistent report messages.

Yes. Configure SMTP, Office 365 or the documented Exchange/Outlook mail options. Standalone Outlook requires a logged-in session with Outlook open; choose the mail setup appropriate to unattended delivery.

Yes. Select a configured mail account for each schedule. You can configure backup SMTP servers to use when the primary SMTP server is unavailable.

Yes. A maintained data source can supply recipients, filters, formats, filenames, subjects, messages and destination instructions when the schedule runs.

Yes. A package schedule runs selected reports and sends their exported files together in one email. Set each report’s format, filename and processing order.

Yes. Merge selected report outputs into an ordered PDF or a combined Excel workbook as part of the reporting-pack workflow.

Yes. Prepare completed report files as a ZIP archive and apply password protection before email delivery.

Set PDF passwords, permissions and text or graphic watermarks. Other options include Excel workbook passwords and configured PGP encryption for the file-delivery workflow.

Use a static or data-driven reply-to address for SMTP email. SMTP and Office 365 delivery also support email priority settings.

With Exchange email settings, set a receipt deadline and a task for a missing receipt, such as an SMS or another schedule. Receipt availability depends on the recipient’s mail client; a returned receipt does not prove an attachment was read.

ATRS Email Log records SMTP messages. For Exchange or Office 365, check the sending account’s Sent Items folder. Use schedule History View to review report and destination results.

Yes. Use the missing-attachment control in the email custom task. Prepare the merged or protected files before the sending task runs.

Yes. Set separators, delimiters and header options for the receiving system. Use the filename timestamp and date-offset settings to label files with the required reporting date.

Set the package-email size option for your mail setup and test representative reporting packs. Include a missing file and an unavailable destination, then review individual destination results and the selected recovery actions.

Delivery options include email, local and network folders, FTP/SFTP, Microsoft Teams, SharePoint, Amazon S3 and Azure storage. Choose the destination and account required by the reporting job.

Recipients can read delivered files without opening Tableau. The exporting account needs the appropriate Tableau permissions and licensing; recipient and filter mappings do not replace those access controls.

Install ATRS on a supported Windows host and configure its unattended service with the source and destination credentials needed by the reporting job. The browser-based client provides access to supported schedule controls.

For a static single schedule, use a data count of one. Calculate driver records × enabled reports × enabled delivery destinations/formats for each schedule run. Add the runs expected on the busiest reporting day and use the report-output calculation guide to size the requirement.

Update the affected schedule’s workbook or view reference and test its output and delivery. Involve ATRS support when migration or package references need further adjustment.