How to Access Live Presto Data in Power Automate Desktop via ODBC



The CData ODBC Driver for Presto enables you to integrate Presto data into workflows built using Microsoft Power Automate Desktop.

The CData ODBC Driver for Presto enables you to access live Presto data in workflow automation tools like Power Automate. This article shows how to integrate Presto data into a simple workflow, moving Presto data into a CSV file.

Through optimized data processing, CData ODBC Drivers offer unmatched performance for interacting with live Presto data in Microsoft Power Automate. When you issue complex SQL queries from Power Automate to Presto, the driver pushes supported SQL operations, like filters and aggregations, directly to Presto and utilizes the embedded SQL engine to process unsupported operations client-side (e.g. SQL functions and JOIN operations).

About Presto Data Integration

Accessing and integrating live data from Trino and Presto SQL engines has never been easier with CData. Customers rely on CData connectivity to:

  • Access data from Trino v345 and above (formerly PrestoSQL) and Presto v0.242 and above (formerly PrestoDB)
  • Read and write access all of the data underlying your Trino or Presto instances
  • Optimized query generation for maximum throughput.

Presto and Trino allow users to access a variety of underlying data sources through a single endpoint. When paired with CData connectivity, users get pure, SQL-92 access to their instances, allowing them to integrate business data with a data warehouse or easily access live data directly from their preferred tools, like Power BI and Tableau.

In many cases, CData's live connectivity surpasses the native import functionality available in tools. One customer was unable to effectively use Power BI due to the size of the datasets needed for reporting. When the company implemented the CData Power BI Connector for Presto they were able to generate reports in real-time using the DirectQuery connection mode.


Getting Started


Connect to Presto as an ODBC Data Source

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

Set the Server and Port connection properties to connect, in addition to any authentication properties that may be required.

To enable TLS/SSL, set UseSSL to true.

Authenticating with LDAP

In order to authenticate with LDAP, set the following connection properties:

  • AuthScheme: Set this to LDAP.
  • User: The username being authenticated with in LDAP.
  • Password: The password associated with the User you are authenticating against LDAP with.

Authenticating with Kerberos

In order to authenticate with KERBEROS, set the following connection properties:

  • AuthScheme: Set this to KERBEROS.
  • KerberosKDC: The Kerberos Key Distribution Center (KDC) service used to authenticate the user.
  • KerberosRealm: The Kerberos Realm used to authenticate the user with.
  • KerberosSPN: The Service Principal Name for the Kerberos Domain Controller.
  • KerberosKeytabFile: The Keytab file containing your pairs of Kerberos principals and encrypted keys.
  • User: The user who is authenticating to Kerberos.
  • Password: The password used to authenticate to Kerberos.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing workflows.

Integrate Presto Data into Power Automate Workflows

After configuring the DSN for Presto, you are ready to integrate Presto data into your Power Automate workflows. Open Microsoft Power Automate, add a new flow, and name the flow.

In the flow editor, you can add the actions to connect to Presto, query Presto using SQL, and write the query results to a CSV document.

Add an Open SQL Connection Action

Add an "Open SQL connection" action (Actions -> Database) and configure the properties.

  • Connection string: DSN=CData Presto Source

After configuring the action, click Save.

Add an Execute SQL Statement Action

Add an "Execute SQL statement" action (Actions -> Database) and configure the properties.

  • Get connection by: SQL connection variable
  • SQL connection: %SQLConnection% (the variable from the "Open SQL connection" action above)
  • SQL statement: SELECT * FROM Customer

After configuring the action, click Save.

Add a Write to CSV File Action

Add a "Write to CSV file" action (Actions -> File) and configure the properties.

  • Variable to write to: %QueryResult% (the variable from the "Execute SQL statement" action above)
  • File path: set to a file on disk
  • Configure Advanced settings as needed.

After configuring the action, click Save.

Add a Close SQL Connection Action

Add a "Close SQL connection" action (Actions -> Database) and configure the properties.

  • SQL Connection: %SQLConnection% (the variable from the "Open SQL connection" action above)

After configuring the action, click Save.

Save & Run the Flow

Once you have configured all the actions for the flow, click the disk icon to save the flow. Click the play icon to run the flow.

Now you have a workflow to move Presto data into a CSV file.

With the CData ODBC Driver for Presto, you get live connectivity to Presto data within your Microsoft Power Automate workflows.

Related Power Automate Articles

This article walks through using the CData ODBC Driver for Presto with Power Automate Desktop. Check out our other articles for more ways to work with Power Automate (Desktop & Online):

Ready to get started?

Download a free trial of the Presto ODBC Driver to get started:

 Download Now

Learn more:

Presto Icon Presto ODBC Driver

The Presto ODBC Driver is a powerful tool that allows you to connect with live data from Presto, directly from any applications that support ODBC connectivity.

Access Presto data like you would a database - read, write, and update Presto Tables, etc. through a standard ODBC Driver interface.