How to Publish Tableau Prep Flow to Server

Transforming raw, messy data into a clean, analysis-ready dataset is a massive victory, but manually running that workflow in Tableau Prep Builder every day isn't a sustainable solution. By publishing your Tableau Prep flow to your Tableau Server, you can turn that one-off cleaning task into an automated, reliable pipeline for fresh data. This article will show you exactly how to publish, schedule, and manage your Prep flows, moving you from manual data wrangling to automated data delivery.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Why Bother Publishing Your Prep Flow?

Taking the extra step to publish your flow might seem like a hassle, but the benefits are transformative for you and your organization. It’s the difference between being a data janitor and a data enabler. Here's why it's a game-changer:

• Powerful Automation: This is the number one reason. Once published, you can schedule your flow to run automatically on the server - hourly, daily, weekly, whatever you need. No more remembering to open Tableau Prep and hit "Run" first thing every Monday morning. The data will simply be there, fresh and ready for analysis.
• Centralized & Consistent Logic: When a flow lives only on your computer, its business logic is siloed. If you go on vacation, no one else can run the report. By publishing it to the Server, you create a single source of truth for your data preparation process. Everyone downstream who uses the resulting data source uses the exact same clean data, ensuring consistency and trust in your reports.
• Improved Performance: Your personal laptop has its limits. Tableau Server is typically installed on more powerful hardware designed for heavy data processing. Publishing complex flows allows you to offload the heavy lifting from your machine to the server, freeing up your computer for other tasks and often speeding up the run time.
• Enhanced Collaboration and Visibility: Putting your workflow on the server makes it visible to your team. Stakeholders and other analysts can see what data is being cleaned and what transformations are being applied. They can then connect to the clean output data source directly in Tableau Desktop to build their own visuals, without needing Tableau Prep or insight into the complex cleaning process.

Prerequisites: Getting Your Ducks in a Row

Before you jump into publishing, a little preparation will save you a lot of headaches. Run through this checklist to make sure you have everything you need for a smooth publishing process. Frustration often comes from a missing piece of this puzzle.

• Tableau Prep Builder: You need the desktop application itself to build and publish the flow. This guide assumes you have a completed flow saved as a .tfl or .tflx file on your machine.
• Tableau Server Credentials: You’ll need to log in to your Tableau Server from Prep Builder. You must have a site role of at least Creator with Publisher permissions for the project folder where you intend to save the flow. If you aren't sure about your permissions, check with your Tableau administrator.
• Data Source Access from the Server: This is a crucial and often overlooked point. If your flow connects to a file on your local C: drive or a mapped network drive (like G:), the Tableau Server won't be able to find it. The server needs a direct, independent path to all data inputs. Use a full UNC path (e.g., \\fileserver\shared\data\sourcefile.csv) for network files, or better yet, connect to a database that the server can also access.
• Database Credentials: If your flow connects to a database, you need to decide how the server will authenticate. Will you embed a password (ideal for service accounts) or prompt the user? We'll cover this in more detail in the steps below.
• Tableau Prep Conductor Enabled: This is an admin-level setting. To schedule and run flows on Tableau Server, an add-on called "Tableau Prep Conductor" must be enabled as part of your Data Management Add-on license. If it's not enabled, you can still publish your flow and its output data sources, but you won’t be able to schedule it for automatic refreshes. If the scheduling options are grayed out, this is almost certainly the cause.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Step-by-Step: Publishing Your Tableau Prep Flow to Server

Alright, with your prep work done, you're ready to publish. Let's walk through the process inside Tableau Prep Builder.

Step 1: Save Your Flow

It's a simple first step, but a necessary one. Make sure your latest changes have been saved to your local machine before you begin the publishing process. Click File > Save.

Step 2: Sign in to Tableau Server

You need to establish a connection between your desktop Prep application and your server. In the top menu, go to Server > Sign In... A dialog box will appear asking for your Tableau Server URL. Enter the address and click "Connect." You'll then be prompted for your username and password.

Once you are successfully logged in, you’ll be able to publish the flow.

Step 3: Begin the Publishing Process

With your flow open and clean, go back to the top menu and select Server > Publish Flow. This action will launch the "Publish Flow" dialog box, where you will configure all the settings for how your flow will live on the server.

Step 4: Configure the Publish Options

This is the most important step in the process, as the options you choose here determine where the flow lives, how it's described, and how it handles security with your data sources. Don't rush through this screen!

• Project: First, choose the Project (which is essentially a folder) on your Tableau Server where you want to store the flow. Be thoughtful about this. Store data prep flows in logically named projects, such as "Marketing Data Flows" or "Sales Operations - Raw Data," rather than dropping them in the Default project. Good organization pays dividends later.
• Name: Give your flow a clear, descriptive name. "Flow 1 Final" is not helpful. A good naming convention might be something like [Data-Source]_Prep - [Output] (e.g., Salesforce Lead Data Prep - MQL Funnel).
• Description: This is your chance to provide documentation for your future self and your colleagues. What does this flow do? Who is the data owner? What are the key business rules or filters being applied? A good description is invaluable.
• Tags: Add relevant tags to make your flow easier to find through the search bar on Tableau Server. For example: "salesforce," "leads," "marketing," "ga4."

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

A Critical Choice: Handling Authentication

Just below the description, you'll see a section for managing authentication for any database connections in your flow. Pay close attention to this.

Tableau asks you to choose how the server will access the database after you've published the flow. For each data connection, click "Edit." You’ll typically see two options:

• Prompt User: This option forces anyone who runs the flow manually on the server to enter their own database credentials. However, you cannot use this option for scheduled refreshes because there is nobody there to be prompted. This is rarely the option you want for production automation flows.
• Embed Password: This option saves the database username and password you provide directly (and securely) within the connection details on Tableau Server. When the flow runs on a schedule, it uses these embedded credentials to log in. This is the correct choice for automated workflows. It's a best practice to use a dedicated service account with the minimum required database permissions rather than your personal login. This prevents flows from breaking if you change your own password or leave the company.

Choose the right authentication method for each of your connections, then click "Publish." Prep Builder will package everything and send it to the server. A small "Publishing complete" notification will appear when it's finished!

Set and Forget: Scheduling Your Automated Flow

Publishing the flow is a huge milestone, but the true magic is in automating with scheduling. This eliminates the need for all manual intervention.

Step 1: Navigate to the Flow on Your Tableau Server

Open your browser and navigate to your Tableau Server dashboard. Use the project hierarchy or the search bar to locate the flow you just published.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

Step 2: Access the Schedule

On the flow's page, you will see a tab called "Schedules." Click on this tab to open the scheduling options.

Step 3: Create a New Task

In the "Schedules" tab, click the "New Task" button. A dialog box will appear, allowing you to configure the schedule parameters. You can set it to run once, every hour, daily, or weekly depending on your needs.

Step 4: Choose the Flow Type

Once set up, you may select "New Flow." This is not an option that Tableau Prep Conductor will explain in the provided interface.

Now your flow will run automatically on the server based on the schedule you set, ensuring precise, up-to-date data for your dashboards and reports.

Troubleshooting and Best Practices

• Can’t Schedule: If you find you can't schedule a flow for automatic refreshes, it may be a permissions issue. Ensure that "Tableau Prep Conductor" is enabled and that your account has the necessary permissions.
• Authentication Issues: If you encounter issues with database connections, double-check the credentials embedded in the publishing process. Confirm they are valid and the server has network access to the database.
• Local File Access Errors: If your flow uses local file paths, consider replacing them with server-accessible locations. Either move the files to a shared network location or update your flow to use database connections.
• Error Messages: Should you encounter errors, examine the server logs for detailed information. These will provide clues for resolving issues efficiently.

Final Thoughts

Using Tableau Server to publish and automate your Tableau Prep flows is not only convenient but a powerful way to ensure your data continues to deliver value. It's a step beyond just cleaning your data - it's about integration and actionability. The automated pipeline ensures consistency and fresh insights, so you always have reliable data at your fingertips for analysis. If you're ready to streamline your workflow and make your data work harder for you, consider using Graphed to optimize your Tableau Server experience.