Release Status Released Supported By Stitch
Availability Free Status Page Trello Status Page
Default Historical Sync 1 year Default Replication Frequency 30 minutes
Whitelisting Unsupported Destination Incompatibilities None

Connecting Trello

Connecting your Trello data to Stitch is a four-step process:

  1. Retrieve your Developer API Keys from Trello
  2. Add Trello as a Stitch data source
  3. Define the Historical Sync
  4. Define the Replication Frequency

Retrieving Your Developer API Keys from Trello

  1. Sign into your Trello account.
  2. Go to the Trello Developer API Keys page.
  3. Locate the Key and Secret fields.

Leave this page open for now - you’ll need it to complete the setup in Stitch.

Add Trello as a Stitch Data Source

  1. Sign into your Stitch account.
  2. On the Stitch Dashboard page, click the Add Integration button.

  3. Click the Trello icon.

  4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

    For example, the name “Stitch Trello” would create a schema called stitch_trello in the destination. Note: Schema names cannot be changed after you save the integration.

  5. Enter your Trello API Key and Secret into their respective fields.

Define the Historical Sync

The Sync Historical Data setting will define the starting date for your Trello integration. This means that:

  • For tables using Incremental Replication, data equal to or newer than this date will be replicated to your data warehouse.
  • For tables using Full Table Replication, all data - including records that are older, equal to, or newer than this date - will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Trello’s default setting of 1 year. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.

Create a replication schedule

In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Stitch offers two methods of creating a replication schedule:

  • Replication Frequency: This method requires selecting the interval you want replication to run for the integration. Start times of replication jobs are based on the start time and duration of the previous job. Refer to the Replication Frequency documentation for more information and examples.
  • Anchor scheduling: Based on the Replication Frequency, or interval, you select, this method “anchors” the start times of this integration’s replication jobs to a time you select to create a predictable schedule. Anchor scheduling is a combination of the Anchor Time and Replication Frequency settings, which must both be defined to use this method. Additionally, note that:

    • A Replication Frequency of at least one hour is required to use anchor scheduling.
    • An initial replication job may not begin immediately after saving the integration, depending on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.

To help prevent overages, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.

Initial and historical replication jobs

After you finish setting up Trello, its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.


Trello Schema

Stitch's Trello integration includes these tables:


trello_actions

Replication Method: Key-based Incremental
Primary Key: id
Contains Nested Structures?: Yes

The trello_actions table contains info about the actions related to cards, including the lists that a card belongs to.

Table Info & Attributes

trello_actions & Nested Structures

This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.

These items are marked with a *

trello_actions Attributes

While we try to include everything Trello has here, this may not be a full list of attributes. Refer to Trello's documentation for a full list and description of each attribute.

  • Action ID (id)

  • data__board__id

  • data__board__name

  • data__card__id

  • data__card__name

  • idmembercreator

  • member__avatarhash

  • member__fullname

  • member__id

  • member__initials

  • member__username

  • membercreator__avatarhash

  • membercreator__fullname

  • membercreator__id

  • membercreator__initials

  • membercreator__username

  • type

trello_boards

Replication Method: Full Table
Primary Key: id
Contains Nested Structures?: Yes

The trello_boards table contains details about all the boards that the connection (authorizing user) is a member of.

Table Info & Attributes

trello_boards & Nested Structures

This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.

These items are marked with a *

trello_boards Attributes

While we try to include everything Trello has here, this may not be a full list of attributes. Refer to Trello's documentation for a full list and description of each attribute.

  • Board ID (id)

  • closed

  • datelastactivity

  • datelastview

  • desc

  • descdata

  • idorganization

  • invitations

  • invited

  • labelnames__black

  • labelnames__blue

  • labelnames__green

  • labelnames__lime

  • labelnames__orange

  • labelnames__pink

  • labelnames__purple

  • labelnames__red

  • labelnames__sky

  • labelnames__yellow

  • name

  • prefs__permissionlevel

  • prefs__voting

  • prefs__comments

  • prefs__invitations

  • prefs__selfjoin

  • prefs__cardcovers

  • prefs__calendarfeedenabled

  • prefs__background

  • prefs__backgroundimage

  • prefs__backgroundimagesscaled*

  • prefs__backgroundtile

  • prefs__backgroundbrightness

  • prefs__canbepublic

  • prefs__canbeorg

  • prefs__canbeprivate

  • prefs__caninvite

  • memberships*

  • powerups*

  • shortlink

  • shorturl

  • starred

  • subscribed

  • url

trello_cards

Replication Method: Key-based Incremental
Primary Key: id
Contains Nested Structures?: Yes

The trello_cards table contains info about the latest state of all the cards that the connection (authorizing user) has access to.

Table Info & Attributes

trello_cards & Nested Structures

This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.

These items are marked with a *

This table is updated based on the actions table.

trello_cards Attributes

While we try to include everything Trello has here, this may not be a full list of attributes. Refer to Trello's documentation for a full list and description of each attribute.

  • Card ID (id)

  • desc

  • checkitemstates*

  • idchecklists*

  • idlabels*

  • idmembers*

  • labels*

  • closed

  • datelastactivity

  • due

  • duecomplete

  • idattachmentcover

  • idboard

  • idlist

  • idshort

  • manualcoverattachment

  • name

  • pos

  • shorturl

  • url

  • badges__attachments

  • badges__checkitems

  • badges__checkitemschecked

  • badges__comments

  • badges__description

  • badges__due

  • badges__duecomplete

  • badges__subscribed

  • badges__viewingmembervoted

  • badges__votes

trello_checklists

Replication Method: Key-based Incremental
Primary Key: id
Contains Nested Structures?: Yes

The trello_checklists table contains info about the latest state of all the checklists on cards that the connection (authorizing user) has access to.

Table Info & Attributes

trello_checklists & Nested Structures

This table contains nested structures. If you use a data warehouse that doesn't natively support nested structures, some of the attributes listed below may be in a subtable.

These items are marked with a *

This table is updated based on the actions table.

trello_checklists Attributes

While we try to include everything Trello has here, this may not be a full list of attributes. Refer to Trello's documentation for a full list and description of each attribute.

  • Checklist ID (id)

  • idboard

  • idcard

  • name

  • pos

  • checkitems*: Contains columns for idchecklist, name, pos, and state.

trello_lists

Replication Method: Full Table
Primary Key: id
Contains Nested Structures?: No

The trello_lists table contains info about all the lists the connection (authorizing user) has access to.

Table Info & Attributes

trello_lists Attributes

While we try to include everything Trello has here, this may not be a full list of attributes. Refer to Trello's documentation for a full list and description of each attribute.

  • List ID (id)

  • closed

  • idboard

  • name

  • pos

  • subscribed

trello_users

Replication Method: Full Table
Primary Key: id
Contains Nested Structures?: No

The trello_users table contains info about the users in your Trello account/organization.

Table Info & Attributes

trello_users Attributes

While we try to include everything Trello has here, this may not be a full list of attributes.

  • User ID (id)

  • fullname

  • username



Questions? Feedback?

Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.