By Rudderstack Team

How to load data from Trello to Redshift

Trello is one of the most popular collaborations and project tools. But it gets filled with data. How can you analyze the data you have on Trello in Amazon Redshift? The purpose of this post is to help you define a process or pipeline, for getting your project management-related data from Trello to Redshift for further analysis.

We will see how to access and extract your data from Trello through its API and how to load it into Redshift. This process requires you to write the code to get the data and make sure that this process will run every time new data is generated.

Alternatively, in order to load your data from Trello to Redshift you can use products like RudderStack that can handle this kind of problem automatically for you.

About Trello

Trello is a collaboration tool that organizes your projects into visual boards. In one glance, Trello tells you what’s being worked on, who’s working on what, and where something is in progress. Trello is simple but flexible enough to allow you to organize your boards using any methodology that you like, for example, many people use Trello to run Kanban.

Trello is simple on the surface, but cards have everything you need to get stuff done. You can post comments for instant feedback. Upload your files from Google Drive, Dropbox, Box, and OneDrive. Add checklists, labels, due dates, and more. Notifications make sure you always know when important stuff happens.

It offers a very simple pricing scheme:

  • Free: This first tier might cover the majority of users. You have access to all the basic functionalities that Trello
  • Business Class & Enterprise: Charged per seat and per month. The main difference between the two is the number of teams that are supported. Also, app integration, team overview, increased file size allowed, file encryption, better support, restricted membership, and enterprise-grade security is provided compared to the Free.

As more and more teams rely on Trello to run and track their projects, there is valuable data to be pulled from it that can help you to better understand the productivity of your company. For example, by pulling data out from Trello and storing it into Amazon Redshift, you can calculate numerous metrics about your sprint, like its current burndown rate. Identify projects with problems and figure out potential bottlenecks. In this article, we will find out how we can pull data from Trello to Redshift for further analysis.

About Amazon Redshift

Amazon Redshift is one of the most popular data warehousing solutions which is part of the Amazon Web Services (AWS) ecosystem. It is a petabyte-scale, fully managed data warehouse as a service solution that runs on the cloud. It is SQL-based and you can communicate with it as you would do with PostgreSQL, actually you can use the same driver although it would be better to use the drivers recommended by Amazon. You can connect either through JDBC or ODBC connections.

Extract your data from Trello

Trello exposes a very rich API to developers. It is the same API that is used internally to build the web and mobile Trello apps that we all use and love. It is possible to build a completely new application on top of the API using the different components and resources that it exposes, or just use it to pull out data as we plan to do in our case.

The Trello API follows the RESTful principles and it can be accessed through HTTP. As a RESTful API, interacting with it can be achieved by using tools like CURL or Postman or by using http clients for your favourite language or framework. A few suggestions:

Trello also offers an official Javascript client/wrapper for its API, that can be found here. It is also possible to find numerous other unofficial SDKs, all it takes is a quick search on Google or Github.

Trello API Authentication

Authentication and Authorization are supported by the Trello API by implementing the OAuth protocol. It’s important to understand that the Authentication Token, obtained through the oAuth workflow execution, gives your application the ability to make calls on behalf of your user, from their context. This token grants access to the authenticated user’s boards, lists, cards, and other settings, depending on the permissions you requested in the authenticate method. So you have to handle it with care.

Trello rate limiting

To help prevent strain on Trello’s servers, our API imposes rate limits per API key for all issued tokens. There is a limit of 300 requests per 10 seconds for each API key and no more than 100 requests per 10-second interval for each token. If a request exceeds the limit, Trello will return a 429 error.

Endpoints and available resources

The Trello API exposes a large number of resources together with their associated HTTP endpoints that allow the users to interact with the platform as the web and mobile applications of Trello do. The most important resources are the following:

  • Board: anything related to the boards a user can create and manage in Trello
  • Card: operations about the cards that can be created inside boards
  • Checklist: it allows the creation and manipulation of checklists inside cards
  • Label: operations related to labels that can be created inside cards
  • List: operations on lists
  • Member: operations related to members of a board
  • Notification: operations about the notification system of the platform
  • Organization: manage organizations inside Trello

Let’s assume that you have a board that helps you track one of your projects, the methodology doesn’t matter at this points, what is important is that you most probably will have cards associate to tasks, and these cards are holding the information that you would like to p