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



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

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

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

Connect to Cassandra 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, Port, and Database connection properties to connect to Cassandra. Additionally, to use internal authentication set the User and Password connection properties.

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 Cassandra Data into Power Automate Workflows

After configuring the DSN for Cassandra, you are ready to integrate Cassandra 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 Cassandra, query Cassandra 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 Cassandra 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 Cassandra data into a CSV file.

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

Related Power Automate Articles

This article walks through using the CData ODBC Driver for Cassandra 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 Cassandra ODBC Driver to get started:

 Download Now

Learn more:

Apache Cassandra Icon Cassandra ODBC Driver

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

Access Cassandra data like you would a database - read, write, and update NoSQL tables through a standard ODBC Driver interface.