Add task automation workflows

Problem Statement

Kaneo currently requires users to manually perform many repetitive actions that could be triggered automatically based on events or conditions.

For example, users may want to automatically assign a task when it is created, change its status when something happens, add a label when a due date is approaching, create a follow-up task when another task is completed, or send information to an external service.

Without a built-in automation system, users have to repeatedly perform these actions manually or rely on external automation tools and integrations.

Kaneo already has integrations and webhook capabilities, but a general automation system would allow users to define simple workflows directly within Kaneo without requiring an external automation platform.

Proposed Solution

Add a native automation system to Kaneo based on a simple trigger → conditions → actions model.

For example:

WHEN:

• A task is created
• A task is moved to a different status
• A task is assigned to someone
• A task is completed
• A task's priority changes
• A label is added or removed
• A due date is approaching
• A comment is added

IF (optional):

• Project is X
• Status is X
• Priority is X
• Label contains X
• Assignee is X
• Task matches specific conditions

THEN:

• Change task status
• Assign/unassign a user
• Add/remove a label
• Change priority
• Set/change due date
• Add a comment
• Create a task
• Move a task to another project
• Send a webhook
• Trigger an integration

The automation builder could provide a simple UI where users create rules such as:

"WHEN a task is moved to Done → create a follow-up task"

or:

"WHEN a task is created with the Bug label → assign it to the engineering team"

or:

"WHEN a task is due tomorrow → add the Urgent label and send a webhook"

Automations should be scoped appropriately (for example workspace/project level), have an enable/disable toggle, and provide basic execution history/logs so users can see whether an automation ran successfully or failed.

The system should remain simple for basic use cases while allowing more advanced workflows to be built incrementally.

Alternative Solutions

N/A

Relevant Context

Kaneo already has integration and webhook functionality, which provides a foundation for event-driven workflows.

There is also an existing feature request for native Kaneo nodes in n8n (#1514), demonstrating interest in connecting Kaneo with automation workflows.

This proposal is complementary to external integrations: native automations would handle common Kaneo-only workflows directly, while webhooks/integrations could remain available for workflows involving external services.

Does this feature align with Kaneo's focus on simplicity?

Yes, because automations can remain optional and simple: users who don't need them can continue using Kaneo exactly as they do today, while users with repetitive workflows can define a small number of straightforward rules. This follows Kaneo's principle of solving real problems without making routine work heavier.

---

Originally requested by @ShadowGaming100 on 2026-09-25. Original GitHub request #1781.