Establishing a Connection

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

Installing and Connecting

If you have PSGet, installing the cmdlets can be accomplished from the PowerShell Gallery with the following command. You can also obtain a setup from the CData site.

Install-Module MailChimpCmdlets

The following line is then added to your profile, loading the cmdlets on the next session:

Import-Module MailChimpCmdlets;

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

$conn = Connect-MailChimp -APIKey 'myAPIKey'

Connecting to Mailchimp

Mailchimp supports the following authentication methods:

APIKey
OAuth

API Key

The easiest way to connect to Mailchimp is to use the API Key. The APIKey grants full access to your Mailchimp account. To obtain the APIKey:

Log into Mailchimp.
Navigate to Account > Extras > API Keys.
Note the value of the API Key.

Once you have the value of the API Key:

Set APIKey to the value of the API Key.
Set AuthScheme to APIKey.

OAuth

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:

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 Mailchimp's OAuth endpoint in your default browser. Log in and grant permissions to the application.

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

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:

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.
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.
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.
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.
Test the connection to generate the OAuth settings file.
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.

Retrieving Data

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

$results = Select-MailChimp -Connection $conn -Table "Lists" -Columns @("Name, Contact_Company") -Where "=''"

The Invoke-MailChimp 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-MailChimp -Connection $conn -Table Lists -Where " = ''" | Select -Property * -ExcludeProperty Connection,Table,Columns | Export-Csv -Path c:\myListsData.csv -NoTypeInformation

You will notice that we piped the results from Select-MailChimp 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-MailChimp -APIKey 'myAPIKey'
PS C:\> $row = Select-MailChimp -Connection $conn -Table "Lists" -Columns (Name, Contact_Company) -Where " = ''" | select -first 1
PS C:\> $row | ConvertTo-Json
{
  "Connection":  {

  },
  "Table":  "Lists",
  "Columns":  [

  ],
  "Name":  "MyName",
  "Contact_Company":  "MyContact_Company"
}

Deleting Data

The following line deletes any records that match the criteria:

Select-MailChimp -Connection $conn -Table Lists -Where " = ''" | Remove-MailChimp

Modifying Data

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

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

Cmdlets for Mailchimp