Trello Integration with Odoo

The module connects Odoo with Trello using Trello's secure API Key and Token authorization. Administrators authorize their Trello account once, choose the Trello workspace to work with, and the connection is stored securely for all further data exchange between the two platforms.

The module stores the Trello API key and token in fields restricted to system administrators. Trello tokens can be issued without an expiry date, so the connector does not need frequent re-authorization. If the token is revoked or becomes invalid, the connector detects it, marks the connection as expired, and prompts the administrator to authorize again.

A connection testing option is provided to verify whether Odoo is successfully connected to Trello. It also shows basic information about the connected Trello member and workspace, such as name, username, and the number of accessible boards, helping administrators confirm that the integration is working correctly.

The connector supports synchronization between Trello boards and Odoo projects. Boards can be imported from Trello as projects in Odoo, and Odoo projects can be exported to Trello as boards. Board name, description, and open or closed status are synchronized, and the relationship between each board and project is maintained.

Trello lists are mapped to Odoo project stages. The connector transfers list names and their order, so the workflow columns in Trello match the stages shown in the Odoo project, and cards moved between lists are reflected as stage changes in Odoo.

The module synchronizes Trello cards with Odoo project tasks in both directions. Important information such as card name, description, due date, list or stage, and archived status can be exchanged between the two systems, while the synchronization status of each record is maintained.

Trello labels are mapped to Odoo task tags. Label names and colors are transferred, and labels added or removed on a card are reflected on the matching task, helping keep categorization consistent across both platforms.

Trello board members are mapped to Odoo users through a configurable mapping table. Once mapped, card members become task assignees in Odoo and the reverse, so responsibility for each piece of work stays consistent in both systems.

Scheduled synchronization allows records to be updated automatically without requiring users to start the process manually. The system identifies recently modified cards, lists, and boards and synchronizes only those, helping reduce unnecessary processing and keeping both systems up to date.

A centralized dashboard provides an overview of the synchronization process. It displays information such as imported records, exported records, pending records, failed records, and connection status. Users can also manually trigger synchronization for specific data types, such as boards, lists or cards, when required.

The module maintains synchronization logs to provide a history of data exchange between Odoo and Trello. These logs help users identify failed operations, understand synchronization issues, and track the status of individual synchronization activities.

Trello supports webhooks that notify Odoo as soon as a card is created, updated, moved or archived. The connector can register webhooks per board so changes arrive almost instantly, with scheduled synchronization kept as a fallback in case a notification is missed. This requires the Odoo server to be reachable from the internet over HTTPS.

Trello checklists and their items can be synchronized with Odoo. Because Odoo Community has no native checklist feature, checklist items can be created as sub-tasks or stored as a checklist inside the task, and completion status can be kept in sync.

Comments written on Trello cards can be imported into the Odoo task chatter, and messages posted on the task in Odoo can be sent back to Trello as card comments, with the author name and date preserved in the text.

Files attached to Trello cards can be downloaded and stored as Odoo attachments on the related task. Files added to the task in Odoo can be uploaded back to the card, with file size limits and duplicate checks applied.

Card due dates and start dates can be mapped to Odoo task deadlines, and the card's due-complete flag can be mapped to a done or closed stage, so deadlines and progress match in both systems.

Trello custom fields (text, number, date, checkbox, and dropdown) can be mapped to custom fields on Odoo tasks through a configurable mapping. This works only on boards where the Custom Fields Power-Up is enabled.

The order of cards within a list can be preserved, so the board looks the same in Trello and in the Odoo Kanban view of the project.

Archived Trello cards and lists can be mapped to archived Odoo tasks and stages, with a configurable choice of whether to archive, ignore, or delete the matching record in the other system when something is removed.

Administrators get additional controls over the synchronization process:

• Configurable synchronization direction for each data type (Trello to Odoo, Odoo to Trello, or both).
• Selective synchronization of chosen boards, lists, labels, or members only.
• Duplicate detection using stored Trello record IDs.
• Conflict handling when a card is changed in both systems, such as latest change wins or a chosen master system.
• Automatic retries with delay for temporary API errors and rate limits.
• Configurable synchronization intervals.

Cards on selected boards, for example, a sales pipeline board, can be converted into Odoo CRM leads or opportunities, with list names mapped to CRM stages. This requires the CRM module.

Each Odoo company can maintain its own Trello connection, credentials, board mappings, and synchronization settings, with record rules so every company sees only its own data.

A comparison report shows the number of boards, lists, and cards in Trello against the matching projects, stages, and tasks in Odoo, and highlights missing, duplicated, or out-of-date records so discrepancies can be found quickly.

Administrators can be notified by email or by an Odoo activity when a synchronization fails repeatedly, or the Trello token becomes invalid.