With the CData Cmdlets users can install a data module, set the connection properties, and start scripting. This section provides examples of using our Monday Cmdlets with native PowerShell cmdlets, like the CSV import and export cmdlets.

Connecting to Monday

Monday AuditLog API

The Monday AuditLog API only supports authentication via API Token.

To generate the audit log API token:

1. Log into your monday.com account.
2. Click on your avatar (picture icon) in the top right corner of your screen.
3. Select Administration from the resulting menu.
4. In the left-hand navigation, click Security.
5. Click the Audit tab.
6. Click Monitor by API > Copy to copy your AuditLog API token.

After you retrieve the API token, set the following connection properties:

• Schema: Set this to "AuditLog".
• AuthScheme: Token
• APIToken: The audit log API token you just obtained.
• URL: Your Monday account URL. You can copy the URL of your Monday homepage after logging in. For example: https://your-account-name.monday.com/.

Monday GraphQL API

The Monday GraphQL API supports authentication via either API Token or the OAuth standard.

API Token

To connect to cmdlet via an API Token, set the AuthScheme to Token and obtain the APIToken as follows:

1. Log into your monday.com account.
2. Click on your avatar (picture icon) in the top right corner of your screen.
3. Select Administration from the resulting menu (this requires you to have admin permissions).
4. In the left-hand navigation, click Connections, then click the API tab in the resulting page.
5. Under Personal API Token, click Create token to create an personal API token. Set the APIToken connection property to this value.
   • If you've already made a token, under Personal API Token, click the Copy button to copy your API token. Set the APIToken connection property to this value.

OAuth

Monday supports OAuth authentication only. To enable this authentication from all OAuth flows, you must set AuthScheme to OAuth, and you must create a custom OAuth application.

The following subsections describe how to authenticate to Monday from three common authentication flows:

• Desktop: a connection to a server on the user's local machine, frequently used for testing and prototyping.
• Web: access to data via a shared website.
• Headless Server: a dedicated computer that provides services to other computers and their users, which is configured to operate without a monitor and keyboard.

For information about how to create a custom OAuth application, see Creating a Custom OAuth Application.

For a complete list of connection string properties available in Monday, see Connection.

Desktop Applications

To authenticate with the credentials for a custom OAuth application, you must get and refresh the OAuth access token. After you do that, you are ready to connect.

Get and refresh the OAuth access token:

• InitiateOAuth = GETANDREFRESH. Used to automatically get and refresh the OAuthAccessToken.
• OAuthClientId = the client Id assigned when you registered your application.
• OAuthClientSecret = the client secret that was assigned when you registered your application.
• CallbackURL = the redirect URI that was defined when you registered your application.

When you connect, the cmdlet opens Monday's OAuth endpoint in your default browser. Log in and grant permissions to the application.

After you grant permissions to the application, the cmdlet then completes the OAuth process:

1. The cmdlet obtains an access token from Monday and uses it to request data.
2. The OAuth values are saved in the path specified in OAuthSettingsLocation. These values persist across connections.

When the access token expires, the cmdlet refreshes it automatically.

Automatic refresh of the OAuth access token:

To have the cmdlet automatically refresh the OAuth access token, do the following:

1. The first time you connect to data, set the following connection parameters:
   • InitiateOAuth = REFRESH.
   • OAuthClientId = the client Id in your application settings.
   • OAuthClientSecret = the client secret in your application settings.
   • OAuthAccessToken = the access token returned by .
   • OAuthSettingsLocation = the path where you want the cmdlet to save the OAuth values, which persist across connections.
2. On subsequent data connections, set the following:
   • InitiateOAuth
   • OAuthSettingsLocation

Headless Machines

If you need to log in to a resource that resides on a headless machine, you must authenticate on another device that has an internet browser. You can do this in either of the following ways:

• Option 1: Obtain the OAuthVerifier value.
• Option 2: Install the cmdlet on a machine with an internet browser and transfer the OAuth authentication values after you authenticate through the usual browser-based flow.

After you execute either Option 1 or Option 2, configure the driver to automatically refresh the access token on the headless machine.

Option 1: Obtaining and Exchanging a Verifier Code

To obtain a verifier code, you must authenticate at the OAuth authorization URL. Do the following:

1. Authenticate from the machine with an internet browser, and obtain the OAuthVerifier connection property.

   Set the following properties:

   • InitiateOAuth = OFF.
   • OAuthClientId = the client Id assigned when you registered your application.
   • OAuthClientSecret = the client secret assigned when you registered your application.

2. Call the GetOAuthAuthorizationURL stored procedure. The stored procedure returns the CallbackURL established when the custom OAuth application was registered. (See Creating a Custom OAuth Application.)

   Copy this URL and paste it into a new browser tab.

3. Log in and grant permissions to the cmdlet. The OAuth application redirects you the redirect URI, with a parameter called code appended. Note the value of this parameter; you will need it later, to configure the OAuthVerifier connection property.

4. Exchange the OAuth verifier code for OAuth refresh and access tokens. On the headless machine, set the following connection properties to obtain the OAuth authentication values:

   • InitiateOAuth = REFRESH.
   • OAuthVerifier = the noted verifier code (the value of the code parameter in the redirect URI).
   • OAuthSettingsLocation = persist the encrypted OAuth authentication values to the specified file.
   • OAuthClientId = the client Id in your custom OAuth application settings.
   • OAuthClientSecret = the client secret in the custom OAuth application settings.

5. Test the connection to generate the OAuth settings file.

6. After you re-set the following properties, you are ready to connect:

   • InitiateOAuth = REFRESH.
   • OAuthSettingsLocation = the file containing the encrypted OAuth authentication values. To enable the automatic refreshing of the access token, be sure that this file gives read and write permissions to the cmdlet.
   • OAuthClientId = the client Id assigned when you registered your application.
   • OAuthClientSecret = the client secret assigned when you registered your application.

Option 2: Transferring OAuth Settings

Prior to connecting on a headless machine, you must install and create a connection with the driver on a device that supports an internet browser. Set the connection properties as described above in "Desktop Applications".

After completing the instructions in "Desktop Applications", the resulting authentication values are encrypted and written to the path specified by OAuthSettingsLocation. The default filename is OAuthSettings.txt.

Test the connection to generate the OAuth settings file, then copy the OAuth settings file to your headless machine.

To connect to data via the headless machine, set the following connection properties:

• InitiateOAuth = REFRESH
• OAuthSettingsLocation = the path to the OAuth settings file you copied from the machine with the browser. To enable automatic refreshing of the access token, ensure that this file gives read and write permissions to the cmdlet.
• OAuthClientId = the client Id assigned when you registered your custom OAuth application.
• OAuthClientSecret = the client secret assigned when you registered your custom OAuth application.

Creating a Connection Object

You can then use the Connect-Monday cmdlet to create a connection object that can be passed to other cmdlets:

$conn = Connect-Monday -APIToken "eyJhbGciOiJIUzI1NiJ9.yJ0aWQiOjE0MTc4NzIxMiwidWlkIjoyNzI3ODM3OSwiaWFkIjoiMjAyMi0wMS0yMFQxMDo0NjoxMy45NDFaIiwicGV"

Retrieving Data

The Select-Monday cmdlet provides a native PowerShell interface for retrieving data:

$results = Select-Monday -Connection $conn -Table "Invoices" -Columns @("Id, DueDate") -Where "Status='SENT'"

The Invoke-Monday cmdlet provides an SQL interface. This cmdlet can be used to execute an SQL query via the Query parameter.

Piping Cmdlet Output

The cmdlets return row objects to the pipeline one row at a time. The following line exports results to a CSV file:

Select-Monday -Connection $conn -Table Invoices -Where "Status = 'SENT'" | 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 object in the result set, and we do not necessarily want that information in our CSV file.

However, this makes it easy to pipe the output of one cmdlet to another. The following is an example of converting a result set to JSON:

 
PS C:\> $conn  = Connect-Monday -APIToken "eyJhbGciOiJIUzI1NiJ9.yJ0aWQiOjE0MTc4NzIxMiwidWlkIjoyNzI3ODM3OSwiaWFkIjoiMjAyMi0wMS0yMFQxMDo0NjoxMy45NDFaIiwicGV"
PS C:\> $row = Select-Monday -Connection $conn -Table "Invoices" -Columns (Id, DueDate) -Where "Status = 'SENT'" | select -first 1
PS C:\> $row | ConvertTo-Json
{
  "Connection":  {

  },
  "Table":  "Invoices",
  "Columns":  [

  ],
  "Id":  "MyId",
  "DueDate":  "MyDueDate"
} 

Deleting Data

The following line deletes any records that match the criteria:

Select-Monday -Connection $conn -Table Invoices -Where "Status = 'SENT'" | Remove-Monday

Modifying Data

The cmdlets make data transformation easy as well as data cleansing. The following example loads data from a CSV file into Monday, checking first whether a record already exists and needs to be updated instead of inserted.

Import-Csv -Path C:\MyInvoicesUpdates.csv | %{
  $record = Select-Monday -Connection $conn -Table Invoices -Where ("Id = `'"+$_.Id+"`'")
  if($record){
    Update-Monday -Connection $conn -Table Invoices -Columns @("Id","DueDate") -Values @($_.Id, $_.DueDate) -Where "Id  = `'$_.Id`'"
  }else{
    Add-Monday -Connection $conn -Table Invoices -Columns @("Id","DueDate") -Values @($_.Id, $_.DueDate)
  }
}