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 Asana 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 AsanaCmdlets

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

Import-Module AsanaCmdlets;

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

$conn = Connect-Asana -InitiateoAuth "GETANDREFRESH" -OAuthClientId "YourClientId" -OAuthClientSecret "YourClientSecret" -CallbackURL "http://localhost:33333"

Connecting to Asana

You can optionally set the following to refine the data returned from Asana.

WorkspaceId: The globally unique identifier (gid) associated with your Asana Workspace to only return projects from the specified Workspace. To get your Workspace Id, navigate to https://app.asana.com/api/1.0/workspaces while logged into Asana. This displays a JSON object containing your Workspace name and Id.
ProjectId: The globally unique identifier (gid) associated with your Asana Project to only return data mapped under the specified Project. Project Ids can be found in the URL of your project's Overview page. This will be the numbers directly after /0/.

Authenticating to Asana

Asana uses the OAuth authentication standard.

User Accounts (OAuth)

AuthScheme must be set to OAuth in all user account flows.

Desktop Applications

CData provides an embedded OAuth application that simplifies OAuth desktop Authentication. Alternatively, you can create a custom OAuth application. See Creating a Custom OAuth App for information about creating custom applications and reasons for doing so.

Get and Refresh the OAuth Access Token

After setting the following, you are ready to connect:

InitiateOAuth: GETANDREFRESH. You can use InitiateOAuth to avoid repeating the OAuth exchange and manually setting the OAuthAccessToken.
OAuthClientId (custom applications only): The client Id assigned when you registered your app.
OAuthClientSecret (custom applications only): The client secret assigned when you registered your app.
CallbackURL (custom application only): The redirect URI defined when you registered your app. For example: https://localhost:3333

When you connect, the cmdlet opens Asana's OAuth endpoint in your default browser. Log in and grant permissions to the application. The cmdlet then completes the OAuth process:

The cmdlet obtains an access token from Asana and uses it to request data.
The OAuth values are saved in the location specified in OAuthSettingsLocation, to be persisted across connections.

The cmdlet refreshes the access token automatically when it expires.

Headless Machines

To configure the driver, use OAuth with a user account on a headless machine. You need to authenticate on another device that has an internet browser.

Choose one of two options:
- Option 1: Obtain the OAuthVerifier value as described in "Obtain and Exchange a Verifier Code" below.
- 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.
Then configure the cmdlet to automatically refresh the access token on the headless machine.

Option 1: Obtain and Exchange a Verifier Code

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

Follow the steps below to authenticate from the machine with an internet browser and obtain the OAuthVerifier connection property.

Choose one of these options:
- If you are using the Embedded OAuth Application, call the GetOAuthAuthorizationURL stored procedure. Open the URL returned by the stored procedure in a browser.
- If you are using a custom OAuth application, set the following properties:
  - InitiateOAuth: Set to OFF.
  - OAuthClientId: Set to the client Id assigned when you registered your application.
  - OAuthClientSecret: Set to the client secret assigned when you registered your application.
  Then call the GetOAuthAuthorizationURL stored procedure with the appropriate CallbackURL. Open the URL returned by the stored procedure in a browser.
Log in and grant permissions to the cmdlet. You are then redirected to the redirect URI. There will be a parameter called code appended to the redirect URI. Note the value of this parameter. Later you will set this in the OAuthVerifier connection property.

Next, you need to 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).
OAuthClientId (custom applications only): The client Id assigned when you registered your application.
OAuthClientSecret (custom applications only): The client secret assigned when you registered your application.
OAuthSettingsLocation: The location where the encrypted OAuth authentication values are saved and persist.

Test the connection to generate the OAuth settings file, then re-set the following properties to connect:

InitiateOAuth: REFRESH.
OAuthClientId (custom applications only): The client Id assigned when you registered your application.
OAuthClientSecret (custom applications only): The client secret assigned when you registered your application.
OAuthSettingsLocation: The location containing the encrypted OAuth authentication values. Make sure this location gives read and write permissions to the cmdlet to enable the automatic refreshing of the access token.

Option 2: Transfer OAuth Settings

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

After completing the instructions in "Desktop Applications", the resulting authentication values are encrypted and written to the location 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.

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

InitiateOAuth: REFRESH.
OAuthClientId (custom applications only): The client Id assigned when you registered your application.
OAuthClientSecret (custom applications only): The client secret assigned when you registered your application.
OAuthSettingsLocation: The location of the OAuth settings file you copied from the machine with the browser. Make sure this location gives read and write permissions to the cmdlet to enable the automatic refreshing of the access token.

Service Accounts

To authenticate with a Server Account (Enterprise only), use a Personal Access Token by setting these connection properties:

InitiateOAuth: OFF.
OAuthAccessToken: Your access token value.

For more more information, see the Asana documentation for personal access tokens and service accounts.

Retrieving Data

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

$results = Select-Asana -Connection $conn -Table "projects" -Columns @("Id, WorkspaceId") -Where "Archived='true'"

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

You will notice that we piped the results from Select-Asana 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-Asana -InitiateoAuth "GETANDREFRESH" -OAuthClientId "YourClientId" -OAuthClientSecret "YourClientSecret" -CallbackURL "http://localhost:33333"
PS C:\> $row = Select-Asana -Connection $conn -Table "projects" -Columns (Id, WorkspaceId) -Where "Archived = 'true'" | select -first 1
PS C:\> $row | ConvertTo-Json
{
  "Connection":  {

  },
  "Table":  "projects",
  "Columns":  [

  ],
  "Id":  "MyId",
  "WorkspaceId":  "MyWorkspaceId"
}

Deleting Data

The following line deletes any records that match the criteria:

Select-Asana -Connection $conn -Table projects -Where "Archived = 'true'" | Remove-Asana

Modifying Data

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

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

Cmdlets for Asana