nickandClaude Sonnet 4.6
0b26fd86ad
Passwords are encrypted with AES-256-GCM before being written to users.json. The GET /api/users/:token endpoint no longer returns the password field, so the settings form asks users to re-enter only when changing it. Legacy plaintext passwords in users.json are decrypted transparently and re-encrypted on next save. Requires a new ENCRYPTION_KEY env var (64-char hex, 32 bytes). Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
AudioPen Nextcloud Webhook
A Node.js service that receives notes from AudioPen and uploads them to Nextcloud via WebDAV. Includes a web UI for self-service setup — each user enters their own Nextcloud credentials and gets a unique webhook URL.
When AudioPen sends a webhook, the service:
- Validates the token in the URL
- Parses the note content (title, body, original transcript)
- Creates a timestamped Markdown file
- Uploads it to the user's configured Nextcloud folder
Example filename:
2026-05-19T22-15-10.123Z-my-note-title.md
Setup
1. Configure environment
Generate an encryption key (required — used to encrypt Nextcloud passwords at rest):
node -e "console.log(require('crypto').randomBytes(32).toString('hex'))"
Create a .env file in the project root:
ENCRYPTION_KEY=paste-your-generated-key-here
ADMIN_PASSWORD=choose-a-strong-password
PORT=3000
# USERS_FILE=users.json # optional, defaults to users.json
ENCRYPTION_KEY is required — the server will not start without it. ADMIN_PASSWORD is required to create new accounts via the web UI; without it, registration is disabled (existing users can still update their settings via their token URL).
2. Run
npm install
node server.js
3. Register users
Open http://localhost:3000 in a browser. Each user fills in their Nextcloud credentials and the admin password, then receives:
- A webhook URL to paste into AudioPen (
/webhook/<token>) - A settings page URL to bookmark for updating credentials later (
/?token=<token>)
Returning users
Visiting /?token=<token> pre-fills the form with existing settings and allows updating credentials without needing the admin password.
Manual user management
User credentials are stored in users.json (gitignored). You can also edit this file directly — see users.json.example for the format.