Trello integration: More Properties to Sync

I would like to add a few specific points from my real Trello → Akiflow workflow.

The main issue for me is that the integration currently transfers too little information from Trello. I use Trello for team and project management, while Akiflow is where I want to plan my personal execution and calendar.

For this workflow to work properly, I would like Akiflow to sync the following Trello properties:

1. Start and end time

If a Trello card already has a start date/time and an end date/time, Akiflow should use them instead of importing only the due date and assigning a default duration.

The task is already planned in Trello, so I should not have to plan its duration again in Akiflow.

2. Duration

I have a Duration field in Trello that matches the duration concept in Akiflow.

If Trello says that a task takes 30 minutes, 45 minutes, 1 hour, 2 hours, etc., this value should be transferred directly into the Akiflow task.

3. Priority

I also have a Priority field in Trello with values that correspond to Akiflow priorities.

For example, if a Trello card has:

Priority: Goal

it should become a Goal in Akiflow automatically.

The same principle could apply to the other matching priority values.

Ideally, Akiflow could allow users to map Trello custom fields to Akiflow fields. This would make the integration flexible enough for different Trello setups instead of requiring everyone to organize Trello in exactly the same way.

4. Repeating tasks

If a Trello card has recurrence information, it would be very useful for Akiflow to understand that recurrence rather than importing it as an isolated task.

5. Subtasks / checklist items

Trello checklists are often part of the actual task structure. It would be useful to have an option to bring these into Akiflow as subtasks or checklist items.

My ideal workflow is simple:

Trello = team/project management → Akiflow = personal execution and time planning.

I do not want to rebuild the task manually after it arrives in Akiflow. If the task already contains its priority, duration, dates and structure in Trello, Akiflow should preserve as much of that information as possible.

One additional idea related to this workflow is reusable task and Time Slot templates.

For example, I regularly need a two-hour block for travel. Instead of creating and configuring the same task every time, I would like to create a template such as:

Travel — 2 hours

with predefined duration, project, labels, priority and other properties.

Then I could simply insert or drag this template into my calendar whenever I need it.

For people who use Akiflow as their main planning layer, these two improvements — richer Trello synchronization and reusable templates — would remove a lot of repetitive setup.