Pipe Zoom Data to CSV in PowerShell

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

Creating a Connection to Your Zoom Data

Start by setting the Profile connection property to the location of the Zoom Profile on disk (e.g. C:\profiles\Zoom.apip). Next, set the ProfileSettings connection property to the connection string for Zoom (see below).

Zoom API Profile Settings

To authenticate to Zoom, you can use the OAuth standard to connect to your own data or to allow other users to connect to their data.

First you will need to create an OAuth app. To do so, navigate to https://marketplace.zoom.us/develop/create and click Create under the OAuth section. Select whether or not the app will be for individual users or for the entire account, and uncheck the box to publish the app. Give the app a name and click Create. You will then be given your Client Secret and Client ID

After setting the following connection properties, you are ready to connect:

• AuthScheme: Set this to OAuth.
• InitiateOAuth: Set this to GETANDREFRESH. You can use InitiateOAuth to manage the process to obtain the OAuthAccessToken.
• OAuthClientID: Set this to the OAuth Client ID that is specified in your app settings.
• OAuthClientSecret: Set this to the OAuth Client Secret that is specified in your app settings.
• CallbackURL: Set this to the Redirect URI you specified in your app settings.

$conn = Connect-API  -Profile "$Profile" -Authscheme "$Authscheme" -OAuthClientId "$OAuthClientId" -OAuthClientSecret "$OAuthClientSecret" -CallbackUrl "$CallbackUrl"

Selecting Data

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

Select-API -Connection $conn -Table MeetingRegistrants | Select -Property * -ExcludeProperty Connection,Table,Columns | Export-Csv -Path c:\myMeetingRegistrantsData.csv -NoTypeInformation

You will notice that we piped the results from Select-API 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.