Trello is a team communication app that organizes your projects into boards. Trello’s boards, lists and cards enable you to organize and prioritize your personal and work life in a fun, flexible and rewarding way.
Cloud Firestore is a cloud-hosted, NoSQL database that your iOS, Android, and web apps can access directly via native SDKs.Cloud Firestore Integrations
Trello + Cloud FirestoreCreate Cloud Firestore Document from Cloud Firestore from Card Updated to Trello Read More...
Trello + Cloud FirestoreCreate Cloud Firestore Document to Cloud Firestore from New Notification in Trello Read More...
Trello + Cloud FirestoreCreate Cloud Firestore Document to Cloud Firestore from New Card in Trello Read More...
Trello + Cloud FirestoreCreate Cloud Firestore Document to Cloud Firestore from New Activity in Trello Read More...
Trello + Cloud FirestoreCreate Cloud Firestore Document to Cloud Firestore from New Label Added to Card in Trello Read More...
It's easy to connect Trello + Cloud Firestore without coding knowledge. Start creating your own business flow.
Triggers the moment a Card is archived in your Trello account.
Triggers once a Card is moved to a Trello List within the same board.
Triggers the moment you update a Card in Trello.
Triggers on every new activity in Trello.
Triggers every time a new attachment is added on board, list or card in Trello.
Triggers when you add a new board in your Trello account.
Triggers when a new card is added.
Triggers every time a new checklist is created in Trello.
Triggers once a Comment is added to a Trello Card.
Triggers the moment you create a new label in Trello.
Triggers once you add a new label in a Trello Card.
Triggers whenever a new list is added on a board.
Triggers when a new card is added in Trello account.
Triggers the moment you receive a new notification in Trello.
New Document Within a Firestore Collection
Adds a new (or existing) checklist to a Trello card.
Adds an existing label to a specific card.
Adds one or multiple members to a specific Trello card.
Archives a card.
Complete an existing checklist Item in a Trello Card.
Creates a new board.
Creates a new card on a specific board and list.
Creates a new checklist item in a Trello card.
Creates a new comment to the specified Trello card.
Adds a new label to your chosen board.
Removes an existing checklist on a card.
Moves your selected card to a list on a specific board.
Delete an existing label from a Trello card.
Update a basic information of card such as name, description, due date, or position in list.
Creates a new document within a Cloud Firestore collection.
Cloud Firestore is a NoSQL database that allows developers to store data in the cloud and directly access it from their applications. On the other hand, Trello is a project management top which helps organize work between different teams. This article discusses how to integrate these two platforms together.
After signing up to Cloud Firestore, the first thing to do is to create a project, which is similar to creating an account on Trello. As shown in Figure 1, there are two options to choose from to create a project. The first option is to create a blank project and the second one is to use an existing Google Cloud Platform project. In this case, the user will be prompted to select a project from the list of projects that they have access to.
Figure 1. Creating a project
Once the project has been created, the next step is to add a few documents. In this example, we will add a few documents that represent information about Trello cards. To do this, click on the “ADD” button on the top left corner as shown in Figure 2.
Figure 2. Adding a document
Clicking on the “ADD” button will open up a modal window as shown in Figure 3. Here, the user can provide some information about the document. In this case, the user needs to provide a name for the document, specify whether it is a cplection or an object, and then specify its schema.
Figure 3. Add document modal window
A document represents each card on Trello. It includes fields such as title and description. A cplection represents all of the cards that are assigned to a board or lists as shown in Figure 4. A cplection contains documents; however, it does not have any additional properties beyond what is defined in its schema. A document has a reference field that points to another document that represents a property of the parent document. In this case, the user will define a reference field for each of the cards on Trello and link them back to the parent card using an ID field as shown in Figure 4. This way when a user clicks on any one of their cards, they will be able to see all of the details about that card without having to flip back and forth between Trello and Cloud Firestore.
Figure 4. Schema of a document created on Cloud Firestore
The schema in figure 4 defines four fields. title, description, boardId, and listId. The boardId and listId fields are references fields because they are pointing back to a card on Trello with an ID field as shown in Figure 5. A reference field can point only one master document. Therefore, if more than one card points back to another card, which means more than one card shares the same ID number on Trello, then there should be one master ID field for all cards just like what was done in Figure 5. Note that there is no master ID field because only one card is being referenced by all other cards as shown in Figure 4. Another important thing to note about reference fields is that they are read-only fields because all of their constraints are set up with “read” only permission. Therefore, users can only read data from those fields but cannot modify or delete them from Cloud Firestore.
Figure 5. Setup referencing fields with read permission only
The boardId and listId fields define two object properties named boardName and listName respectively as shown in Figure 6. They are used to store names of boards and lists in Trello. For example, suppose if a user wants to create a card on a specific board or list on Trello, they can use that property to find out the name of boards and lists on Trello without searching through all of their cards and boards on Trello to find where they need to create a new card. Also, note that object properties do not have any referencing field because there is no need for them since they are not linked back to any other document in Trello like those reference fields in Figure 4. They are simply used for storing information about boards and lists within a given card on Trello. The rest of the fields include title and description which are simply used for storing text information about cards within Trello as shown in Figure 6. The last field is dateCreated which represents the date when documents were created on Cloud Firestore for each card within Trello. All other fields are required fields since they are included in the schema definition, which means that all documents will have these fields regardless of whether they are used or not as shown in Figure 6.
Figure 6. Definition of object properties with strings type
To finish setting up Cloud Firestore documents, users can also define their own custom JSON objects if they would like as shown in Figure 7. As discussed before, users need to provide an ID field for every object property within Cloud Firestore to uniquely identify every property within their documents as shown in Figure 7. For example, suppose if users want to store information about their company within their Cloud Firestore documents; they can easily do it by adding object properties with IDs such as “companyName” and “companyDescription” as shown in Figure 7 and then linking those properties back to those IDs from other documents on Trello and Google Drive so that all those pieces of information will be stored together in one place instead of being scattered around within different documents inside Cloud Firestore and Google Drive. Finally, note that there is no limit for how many properties users can add into their documents within Cloud Firestore but they must make sure that each property has its own ID field otherwise it will be impossible for them to write data into their documents later on once they start connecting it back to documents within Cloud Firestore from other platforms such as Google Drive or Trello. After all of those settings have been made, users can click on “Save” button at the bottom right corner as shown in Figure 7 so that they can return back to their document list with all of the new documents added as shown in Figure 8 below.
Figure 7. Definition of custom JSON object properties with integers type
Figure 8. List of new documents added by users on Cloud Firestore
In conclusion, we discussed how users can use Cloud Firestore to connect data on Trello with Google Drive or any other third-party application through “reference fields” and “object properties” features within Cloud Firestore. By doing this, users will be able to organize their data across multiple platforms by storing it within Cloud Firestore instead of having it scattered around multiple applications such as Google Drive or Trello alone.
The process to integrate Trello and Cloud Firestore may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.