Tableau Via Kondado Connection

You can connect Tableau to your Via Kondado destination through Kondado's PostgreSQL endpoint (kdb.kondado.io). You use Tableau's native PostgreSQL connector and your destination token as the password. Once connected, your destination tables are available to build data sources, sheets and dashboards.

  1. Before you start
  2. Step by step
  3. After connecting
  4. FAQ

Before you start

  • You need an active Via Kondado destination in your account. If you don't have one yet, see how to create Via Kondado.
  • Have your destination's access token ready — it will be used as the connection password. It is the same token used for the other access methods. See how to get your token.
  • Use Tableau Desktop (Windows or macOS). Tableau uses the PostgreSQL connector; on some versions you may need to install Tableau's PostgreSQL driver (Tableau shows the download link if it is missing).

Connection details (keep these for the steps below): Connector: PostgreSQL • Server: kdb.kondado.io • Port: 5432 • Database: kdb • Username: any value (e.g. kondado) • Password: your Via Kondado destination token • SSL: required (check “Require SSL”).

Step by step

1. In Tableau, on the Connect pane, under To a Server, choose PostgreSQL. If it isn't listed, click More….

2. Fill in the connection dialog exactly like this:

  • Server: kdb.kondado.io
  • Port: 5432
  • Database: kdb
  • Authentication: Username and Password
  • Username: any value, e.g. kondado
  • Password: your Via Kondado destination token
  • Check the “Require SSL” option — the SSL connection is required

3. Click Sign In. Tableau opens the Data Source page, showing the public schema and your destination tables on the left.

4. Drag a table onto the canvas and click Update Now to preview the data. We recommend using a Live connection to query the source directly.

5. That's it! Go to a Sheet and drag dimensions and measures to build your visualizations.

After connecting

  • All of your destination tables appear in the public schema. Your Via Kondado saved queries also appear as tables.
  • You can build sheets and dashboards, create calculated fields, apply filters, aggregations (SUM/COUNT/AVG), date bucketing (year/month), JOINs/relationships across tables and TOP N. To exercise filter pushdown to the source, prefer the Live connection.

FAQ

How to connect Tableau to Via Kondado

Connect Tableau to your Via Kondado destination through the PostgreSQL connector kdb.kondado.io using the destination token as the password.

1
Choose PostgreSQL

In Tableau's Connect pane, under To a Server, choose PostgreSQL.

2
Fill in the connection

Server kdb.kondado.io, Port 5432, Database kdb, Username any value (e.g. kondado) and Password equal to your Via Kondado destination token.

3
Enable SSL

Check the Require SSL option. The SSL connection is required.

4
Sign in and open the source

Click Sign In. Tableau opens the Data Source page with the public schema and your destination tables.

5
Build visualizations

Drag a table onto the canvas, refresh the preview and go to a Sheet to build your visualizations.

Frequently asked questions

Which password do I use in the Tableau connection?
The password is your Via Kondado destination access token — the same token used for the other access methods. The username can be any value; authentication is done by the password (token) only.
Is there a Linux version of Tableau?
No. Tableau Desktop is available only for Windows and macOS. Use one of those systems to connect to Via Kondado.
Do I need to install the PostgreSQL driver?
On some Tableau versions you need to install the PostgreSQL driver. If it is missing, Tableau shows a link to download the correct driver right on the connection screen.
Is SSL required?
Yes. Check the “Require SSL” option when configuring the PostgreSQL connection. Connecting without SSL is not recommended.
Should I use a Live or Extract connection?
To query the source directly and push filters/aggregations down to Via Kondado, prefer the Live connection. Extract also works when you want a local copy of the data.
What database name should I enter?
Use kdb. The database name does not affect routing — the table catalog is determined by your token — but we recommend kdb by default.

Written by·Published 2026-07-03