Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.runwita.com/llms.txt

Use this file to discover all available pages before exploring further.

Runwita is local-first. Everything works without external integrations. But two connections, one for tasks and one for transcripts, 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.
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.

​
MeetingScribe (transcription auto-import)

MeetingScribe is a personal AI meeting recorder, separate app, but Runwita knows how to read its output folder. If you point Runwita at the folder where MeetingScribe drops its transcripts, every new transcript appears in Runwita’s Inbox automatically.
1

Find MeetingScribe's output folder

Open MeetingScribe → Settings → Output folder. Copy the path.
2

Paste it into Runwita

Settings → Connections → Meetings folder. Paste the path. Save.
3

Verify

Open the Inbox. Any past transcripts in that folder should already be visible. Any new transcript MeetingScribe writes there will appear within a few seconds.
Runwita reads, never writes, to this folder. MeetingScribe’s files stay where they are; deleting an inbox item in Runwita doesn’t delete the underlying transcript file. If you don’t use MeetingScribe, leave the field blank. You can still drag-drop or paste transcripts 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.