Ready to get started?

Download a free trial of the Monday.com Cmdlets to get started:

 Download Now

Learn more:

Monday.com Icon Monday.com Data Cmdlets

An easy-to-use set of PowerShell Cmdlets offering real-time access to Monday.com. The Cmdlets allow users to easily read live data - just like working with SQL server.

Pipe Monday.com Data to CSV in PowerShell



Use standard PowerShell cmdlets to access Monday.com tables.

The CData Cmdlets Module for Monday.com is a standard PowerShell module offering straightforward integration with Monday.com. Below, you will find examples of using our Monday Cmdlets with native PowerShell cmdlets.

Creating a Connection to Your Monday.com Data

You can connect to Monday.com using either API Token authentication or OAuth authentication.

Connecting with an API Token

Connect to Monday.com by specifying the APIToken. Set the AuthScheme to Token and obtain the APIToken as follows:

  • API tokens for admin users
    1. Log in to your Monday.com account and click on your avatar in the bottom left corner.
    2. Select Admin.
    3. Select "API" on the left side of the Admin page.
    4. Click the "Copy" button to copy the user's API token.
  • API tokens for non-admin users
    1. Click on your profile picture in the bottom left of your screen.
    2. Select "Developers"
    3. Click "Developer" and then "My Access Tokens" at the top.
    4. Select "Show" next to the API token, where you'll be able to copy it.

Connecting with OAuth Authentication

Alternatively, you can establish a connection using OAuth (refer to the OAuth section of the Help documentation).

$conn = Connect-Monday  -APIToken "$APIToken"

Selecting Data

Follow the steps below to retrieve data from the Invoices table and pipe the result into to a CSV file:

Select-Monday -Connection $conn -Table Invoices | Select -Property * -ExcludeProperty Connection,Table,Columns | Export-Csv -Path c:\myInvoicesData.csv -NoTypeInformation

You will notice that we piped the results from Select-Monday into a Select-Object cmdlet and excluded some properties before piping them into an Export-Csv cmdlet. We do this because the CData Cmdlets append Connection, Table, and Columns information onto each "row" in the result set, and we do not necessarily want that information in our CSV file.

The Connection, Table, and Columns are appended to the results in order to facilitate piping results from one of the CData Cmdlets directly into another one.