How we integrate with Trello

Get started

Sign in to your account, then go to Settings -> Apps, or reload this page for a link.

Reading from Trello

Which Trello content we read depends on how you configure fflow. If you do not configure integration, we will not read or import any content. The sections below explain content you can choose to read and import into fflow.

Writing to Trello

Trello integration is one way: we only read. We do not send or write any information from fflow to Trello. Nothing you configure in fflow will be reflected on the Trello side.

For best practice security, we recommend that you turn off write permission when you create a token in Trello. But if you do provide a token with write permissions, we will not use them.

Security

We use the authorization process provided by Trello.

One-time import

You can choose to import Members, Boards, Lists, and Cards from Trello as a one-time action. We create or update content in fflow based on the imported information, and we update the internal description to show that this was created automatically. Content won't be updated again, unless you import again, or set up Listeners (see below).

You can choose to import again. We create new content once and once only. If you import again, we will update any changed names, and Card Member -> Booking User.

If you have already created content with the same name as Trello Boards, Lists, or Cards, we do not overwrite the (internal) description.

We recommend you don't create content in fflow if you plan to import it from Trello: let the integration do any creating that maps Trello content.

Members

You can import all the Members from the Trello Board. We map each Trello member to a fflow user if we find a matching email address. We will skip over a Member if the email address is not provided or not matched.

If you do not choose to import Members, or if the Member email address for a Card is not matched, you can still import the Card and create a Booking, it will be Unassigned in fflow.

We only receive email addresses for Members from Trello if you configure the Token with account scope. If you do not configure account scope, we can not match users in fflow. Everything else will still work, we just won't assign Bookings to Users.

Boards

You can import each Board from your Trello account. When you do this, we create or update a project in fflow with the same name

Lists

You can import all the Lists for a Trello Board, initially we don't create content in fflow for these.

Cards

You can select an imported List, and import all its cards. We create or update one Task and Booking in fflow for each card. For existing Bookings, we update the finish date but not the start date.

Listeners

When you configure a listener, we listen out for updates from a matching Trello list. You do not have to configure listeners, and you can still import content from Trello, but anything you import will not be updated when Trello changes.

You can choose to set up a listener for each List in Trello. When you do this, you also choose a matching Booking State in fflow.

When you set up a listener, we create a Webhook in Trello.

When our listener receives incoming requests, we validate the IP addresses documented by Trello in the link above.

Actions we listen for

When a Card is moved between lists in Trello, we create or update the matching Booking, so that the state reflects the new list.

When a Card title is changed, we update the matching Task in fflow, if it was created by Trello import.

When a Card is archived in Trello, we mark the associated Booking as 'Abandon' in fflow. We think this is most useful because it gives you a chance to notice the action of archiving. If we were to Archive the Booking in fflow, it would be hidden and you might not notice the action.

Actions we don't listen for

Trello List webhooks do not send Member information, so if a Card Member changes, the listener does not update the Booking user. If you want to update fflow for Member changes, you can use the single import buttons above, to update existing Bookings.

Tidy up old listeners

We recommend that you delete Listeners when you no longer need them: they use up processing and network capacity for both Trello and fflow.

How to remove Trello Integration

You can stop the Trello integration at any time, by removing the configuration in fflow.

Listeners

When you remove a listener, we un-register the webhook in Trello. We keep any imported content in fflow, but it will not be automatically updated again.

Imported content

You can un-configure by clicking Remove connection and all imported content, this is the effect

  • Delete all imported Tasks
  • Delete all Listeners, and un-register the matching webhooks in Trello
  • Archive all imported Projects
  • Archive imported Bookings, this hides them in the Calendar. Bookings with Time booked are kept active.
  • Anything that was created by fflow users is kept

Feedback

We welcome questions and comments, please send any feedback to info@fflow.io