How Do You Deliver Tableau Reports to an SFTP Server Automatically?

Imagine your service team answering a customer’s call about a missing daily activity file. The Tableau report is ready, but the customer does not collect email attachments. Its import looks in a particular directory on its transfer server.

Until someone exports the report and completes the upload, the customer cannot finish its reconciliation. The recurring task includes both the file and the transfer.

ATRS can maintain the Tableau Cloud report inputs, output and FTP destination together, using the supported secure transfer type agreed with the customer. That turns a repeated desktop task into a reporting job the team can maintain.

Conceptual illustration: Report files routed to the people and locations that use them.

For a one-off file, an authorized export and your organization’s approved transfer client may be enough. A maintained script is another option when your development team wants to own the connection, scheduling and recovery.

ATRS is useful when the same customer file is needed every day, or when other customers need their own periods, filenames and directories. Keep those requirements with the reporting instructions so an address change does not become another set of disconnected reminders.

Ask the customer how it recognizes a complete delivery and whether it expects a fixed filename. A successful connection test alone does not establish that the import found the intended file.

Create the activity report schedule with a test directory agreed by the customer. Select the Tableau Cloud report and its customer/date inputs, then choose the output the receiving process accepts.

Add the FTP destination and configure the approved transfer type, server, port, account and directory. Verify the connection before sending the sample file. This separates access problems from questions about the export itself.

Have the customer retrieve and import that delivered sample. Find a known activity record and compare the agreed total. Use the filename and date rule it will see in production, so the trial tests the actual handoff.

Then try an unavailable destination and agree who receives the failure notification. When the connection, file and recovery are understood, enable the recurring job after the day’s required data is ready.

The ATRS FTP destination includes connection and remote-directory settings. Select the secure transfer type agreed with the receiving administrator.

Your service application can request an extra customer file through the saved ATRS job. The reporting team keeps its export and transfer settings in one place.

Retain the application request with the reporting date, so another colleague can follow the transfer without starting it again.

POST /api/Schedule/ExecuteScheduleAsync
Authorization: Bearer <ATRS-access-token>
Content-Type: application/json

{
  "ScheduleType": "report",
  "UniqueId": 101,
  "RunBy": "Customer activity transfer"
}

GET /api/Schedule/GetExecutionStatus?ExecutionId=<returned-id>
Authorization: Bearer <ATRS-access-token>

The customer can begin its reconciliation from the file in its agreed directory, and your service team can discuss the activity rather than repeat the upload.

Bring the accepted sample and transfer requirements to your first ATRS trial. Prove one customer’s complete handoff before extending the routine.

Explore ATRS file-transfer delivery