Feature Request: Automation support (n8n/webhooks)

[yrmuq]

Hello. I want to create tasks automatically using n8n. I know a standard server API is impossible because of E2E encryption.
Could you add a way to automate task creation without breaking E2E? Here are 3 short ideas:

1. Local Desktop API: The running desktop app opens a local port. n8n sends plain JSON to it, and the app encrypts and syncs the task.
2. Headless Client: A CLI/Docker background tool. We give it the encryption key, it receives local webhooks, encrypts data, and syncs to the server.
3. Unencrypted Inbox: The server receives plain text tasks via API. When the official app connects, it takes them, encrypts them, and moves them to the main database.

Please consider this. Thank you.

[jpbaril]

Automation / API support would be very nice.
In my case, I often create tasks by voice with Home Assistant, so to have a way for Home Assistant to create task through API calls would be awesome.

[CaryTrivett]

This software itself is based on a file-based database, with all the logic running in the browser.
This means there is no way to create or modify tasks via an API.

The current version does have a CLI mode. However, I’m concerned that the AI might corrupt the database, so for now, I’m accessing the local database of the desktop version in read‑only mode.

[CaryTrivett]

Hello. I want to create tasks automatically using n8n. I know a standard server API is impossible because of E2E encryption. Could you add a way to automate task creation without breaking E2E? Here are 3 short ideas:

1. Local Desktop API: The running desktop app opens a local port. n8n sends plain JSON to it, and the app encrypts and syncs the task.
2. Headless Client: A CLI/Docker background tool. We give it the encryption key, it receives local webhooks, encrypts data, and syncs to the server.
3. Unencrypted Inbox: The server receives plain text tasks via API. When the official app connects, it takes them, encrypts them, and moves them to the main database.

Please consider this. Thank you.

1 and 2 are actually already under consideration and design. The current plan is:

Provide a read‑only CLI. The CLI will include a command that sends modification requests to the local client. The local client can then approve the modifications.

Currently, the CLI functionality is insufficient. You can take a look at:
https://github.com/hamsterbase/tasks/blob/main/src/cli/index.tsx

3 is a great idea. I will develop it as soon as possible.