Trello is a web-based list-making and task management application. Boards contain lists, and lists contain cards that represent tasks. The connector extracts members, boards, lists, cards, and board activity (actions) into your catalog.

Configuring Trello as a Source

In the Sources tab, click Add source in the top right, then select Trello. Click Next to open the account access step. The connector requires your API Key and Token. The Secret field from your Trello app is not used.

1. Add account access

Open the Trello developer page

Go to https://trello.com/app-key and log in if prompted.

Create an app (if needed)

If you have not created an app before, create one. Trello will then show a page with your API Key and Secret.

Copy your API Key

On that page, find API Key. This is the value you enter in the connector’s API Key field. Do not use the Secret; it is not used for this integration.

Generate your Token

On the same page, click the token link (under “Token”), or open this URL in your browser and replace YOUR_API_KEY with your actual API Key:https://trello.com/1/authorize?expiration=never&scope=read,write&response_type=token&key=YOUR_API_KEYAuthorize the app when prompted. Trello will display a token string; copy it and paste it into the connector’s Token field.

Enter the API Key and Token in the connector form, then click Next.

2. Select streams

Choose which data streams you want to sync. You can select all streams or only those relevant to your analysis. The hierarchy is: members → boards → lists and actions; lists → cards.

Tip: The stream can be found more easily by typing its name.

Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data), and the type of sync.

Layer: Choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
Folder: A folder can be created inside the selected layer to group all tables being created from this new data source.
Table name: We suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster.
Sync Type: You can choose between INCREMENTAL and FULL_TABLE.
- Incremental: Every time the extraction happens, we’ll get only the new data—which is good if, for example, you want to keep every record ever fetched (used by default for the actions stream).
- Full table: Every time the extraction happens, we’ll get the current state of the data—which is good if, for example, you don’t want to have deleted data in your catalog.

Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:

Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.

Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.

For you to be able to see it on your Catalog, you need at least one successful source run.

Streams and Fields

Below you’ll find all available data streams from Trello and their corresponding fields. Streams are nested: members is the root; boards are children of members; lists and actions are children of boards; cards are children of lists.

Members

Stream for the authenticated member (you). One record per source; used as the parent for boards.

Field	Type	Description
`id`	String	Unique identifier of the member.
`username`	String	Username of the member on Trello.
`fullName`	String	Full display name of the member.
`email`	String	Email address associated with the member account.
`url`	String	URL of the member’s Trello profile.
`aaId`	String	Atlassian Account ID.
`activityBlocked`	Boolean	Whether activity is blocked for the member.
`avatarHash`, `avatarUrl`	String	Hash and URL of the member’s avatar.
`bio`, `bioData`	String	Short bio; structured bio data (JSON string).
`confirmed`	Boolean	Whether the member account is confirmed.
`initials`	String	Member initials.
`memberType`	String	Type of member.
`status`	String	Member status.
`nodeId`	String	GraphQL node ID.
`dateLastActive`, `dateLastImpression`	DateTime	Last active and last impression date.
`idBoards`	Array of Strings	Board IDs the member has access to.
`idOrganizations`	Array of Strings	Organization IDs the member belongs to.
`idEnterprise`, `idEnterprisesDeactivated`, `idMemberReferrer`, `idPremOrgsAdmin`, `idEnterprisesAdmin`	String / Array	Enterprise and referral identifiers.
`limits`, `prefs`, `products`, `loginTypes`, `messagesDismissed`, `oneTimeMessagesDismissed`, `trophies`, `premiumFeatures`	String	JSON strings for limits, preferences, and related data.
`nonPublic`, `nonPublicAvailable`, `domainClaimed`, `marketingOptIn`, `isAaMastered`	Boolean	Profile and account flags.
`gravatarHash`, `uploadedAvatarHash`, `uploadedAvatarUrl`, `avatarSource`	String	Avatar-related fields.
`credentialsRemovedCount`	Integer	Count of removed credentials.
`aaBlockSyncUntil`, `aaEmail`, `aaEnrolledDate`, `sessionType`	String	Atlassian and session fields.
`ixUpdate`	String	Index update (API may return string or number).

Boards

Stream for boards the member has access to. Each board is a container for lists and has an activity feed (actions).

Field	Type	Description
`id`	String	Unique identifier of the board.
`name`	String	Name of the board.
`desc`	String	Description text of the board.
`closed`	Boolean	Whether the board is closed (archived).
`url`, `shortUrl`, `shortLink`	String	URL and short link for the board.
`dateLastActivity`, `dateLastView`, `dateClosed`, `datePluginDisable`	DateTime	Activity and view timestamps.
`nodeId`	String	GraphQL node ID.
`descData`	String	Structured description data (JSON string).
`creationMethod`, `creationMethodError`, `creationMethodLoadingStartedAt`	String / DateTime	Creation metadata.
`idOrganization`, `idEnterprise`, `idBoardSource`, `idMemberCreator`	String	Organization, enterprise, and creator IDs.
`limits`, `prefs`, `labelNames`, `powerUps`, `templateGallery`, `premiumFeatures`, `memberships`	String	JSON strings for limits, preferences, labels, power-ups, and memberships.
`pinned`, `starred`, `subscribed`, `enterpriseOwned`	Boolean	Board flags.
`idTags`	Array of Strings	Tag IDs.
`type`	String	Board type.
`member_id`	String	Member ID (from parent context).
`ixUpdate`	String	Index update (API may return string or number).

Lists

Stream for lists (columns) on a board. Cards belong to lists.

Field	Type	Description
`id`	String	Unique identifier of the list.
`name`	String	Name of the list.
`closed`	Boolean	Whether the list is closed (archived).
`idBoard`	String	Identifier of the board this list belongs to.
`pos`	Number	Position of the list on the board.
`color`	String	List color.
`subscribed`	Boolean	Whether the member is subscribed to the list.
`softLimit`, `datasource`	String	Soft limit and datasource (JSON string if object).
`type`	String	List type.
`board_id`	String	Board ID (from parent context).
`ixUpdate`	String	Index update (API may return string or number).

Cards

Stream for cards (tasks) within a list. Cards can have labels, due dates, descriptions, checklists, and members.

Field	Type	Description
`id`	String	Unique identifier of the card.
`name`	String	Title of the card.
`desc`	String	Description text of the card.
`closed`	Boolean	Whether the card is closed (archived).
`idBoard`, `idList`	String	Identifier of the board and list this card belongs to.
`url`, `shortUrl`, `shortLink`	String	URL and short link for the card.
`dateLastActivity`, `due`, `start`	DateTime	Last activity, due date, and start date.
`dueComplete`	Boolean	Whether the card’s due date has been marked complete.
`pos`	Number	Position of the card within its list.
`labels`	Array of Objects	Labels on the card. Each object has `id`, `name`, `color`, `idBoard`, `idOrganization`, `nodeId`, `uses`.
`idChecklists`, `idMembers`, `idMembersVoted`, `idLabels`	Array	Checklist IDs, assigned member IDs, voters, and label IDs.
`idShort`	Integer	Short numeric ID of the card.
`idAttachmentCover`	String	ID of the cover attachment.
`agent`, `badges`, `checkItemStates`, `descData`, `dueReminder`, `manualCoverAttachment`, `cover`	String	JSON strings for agent, badges, checklist states, description data, reminder, cover.
`email`	String	Card email address.
`nodeId`	String	GraphQL node ID.
`pinned`, `subscribed`, `isTemplate`	Boolean	Card flags.
`cardRole`, `mirrorSourceId`	String	Card role; ID of source card if this is a mirror.
`list_id`	String	List ID (from parent context).

Actions

Stream for activity on a board (e.g. card moves, comments, updates). Synced incrementally using the date field so only new actions are fetched after the first run.

Field	Type	Description
`id`	String	Unique identifier of the action.
`idMemberCreator`	String	Identifier of the member who created the action.
`type`	String	Type of the action (e.g. `updateCard`, `addMemberToBoard`, `commentCard`).
`date`	DateTime	Timestamp when the action occurred.
`data`	String	Contextual data payload (JSON string; varies by action type).
`board_id`	String	Board ID (from parent context).
`appCreator`, `limits`, `member`, `memberCreator`	String	App creator, limits, and member info (JSON strings).

Data Model

The following diagram illustrates the relationships between the Trello streams. The arrows indicate parent-child and join keys.

Members is the root (one record: the authenticated user). Boards are fetched per member (/members/{member_id}/boards).
Lists and Actions are fetched per board (/boards/{board_id}/lists, /boards/{board_id}/actions).
Cards are fetched per list (/lists/{list_id}/cards).

Use idBoard and idList on cards to join with boards and lists; use board_id and list_id from the sync context or from the card fields for relationships.

Documentation

Get started

Using Nekt

Workspace

Resources

Trello as a data source

Configuring Trello as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

Data Model

Documentation

Get started

Using Nekt

Workspace

Resources

​Configuring Trello as a Source

​1. Add account access

​2. Select streams

​3. Configure data streams

​4. Configure data source

​5. Check your new source

​Streams and Fields

​Data Model

Configuring Trello as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

Data Model