Skip to main content
Runwita is local-first. Everything works without external integrations. But two connections, one for tasks and one for an external notes folder, are useful enough that they’re built in.

​
TickTick (two-way action sync)

When you save an engagement with action items, Runwita can push those actions to your TickTick task list. When you complete a task in TickTick, that change syncs back to Runwita and the action shows as done. Set up:
1

Get TickTick OAuth credentials

Head to developer.ticktick.com. Create a new app. The redirect URI Runwita expects is http://localhost:9876/callback, you’ll set that on TickTick’s side. Copy the Client ID and Client Secret.
2

Paste them in

Settings → Connections → TickTick. Two fields: Client ID and Client Secret. Save.
3

Click Connect

A browser window opens to TickTick’s auth page. Approve. You’ll be redirected back to Runwita and the connection status flips to Connected.
4

Force a sync

First time, click Force sync now to pull in any tasks Runwita should know about and push out any open actions you’ve already saved.
After that, sync runs in the background every few minutes. You can force a sync at any time. The sync is two-way for completion state only. Editing the title of a task in TickTick doesn’t change the action in Runwita, and vice versa, the engagement is the source of truth for what the action is; TickTick is just where you check it off. The TickTick task description includes a back-link to the engagement. To disconnect, click Disconnect TickTick. This clears your access token; Runwita keeps the actions but stops syncing them. You can reconnect later with the same Client ID/Secret.

​
Notes folder (auto-import)

If you already have a folder where transcripts and notes accumulate, point Runwita at it. Any file in that folder appears in Runwita’s Inbox automatically, and any new file dropped in shows up within seconds. This is useful when something else (a transcription tool, a synced notes app, a script of your own) is already writing files to a known location. Runwita doesn’t care what put the files there. As long as they land in the watched folder, they’re picked up.
1

Pick a folder

Anywhere on disk. A typical choice is your transcription tool’s output folder, or a dedicated ~/Notes/Runwita-inbox/ directory you’ll drop files into manually.
2

Paste it into Runwita

Settings → Connections → Notes folder. Paste the absolute path. Save.
3

Verify

Open the Inbox. Any existing files in the folder root should already be visible. Any new file written there will appear within a few seconds.
Two things to know:
  • Read-only. Runwita reads from the folder, it never writes to it or deletes from it. Deleting an inbox item in Runwita doesn’t touch the underlying file.
  • Root only. Only files at the top level of the folder are watched. Subfolders are ignored, so you can move processed files into a subdirectory if you want them out of the Inbox without losing them.
If you don’t want this connection, leave the field blank. You can still drag-drop or paste content into the Inbox manually.

​
Anything else?

That’s it for now. Future integrations on the roadmap:
  • Calendar (Google Calendar, Outlook), to pre-populate engagement metadata from the actual calendar event.
  • Slack, to ingest threads as engagements.
  • Email beyond manual .eml import, to watch a label/folder and auto-import.
None of these are wired yet. When they are, they’ll appear in this panel.