OpenSync integration

OpenSync is where teams keep specs, decisions and notes. Connect a space to your workspace, and transcripts worth keeping are saved there as Markdown notes: when Dcision picks Save to OpenSync, or when someone chooses it on a transcript. See Transcription and AI routing.

Each workspace connects its own space. Nothing is shared between workspaces.

Before you startCopy Anchor Link

• You need to be an admin of the workspace.
• In OpenSync, open the space, go to its Connect panel and create a token. It starts with osk_ and only gives access to that space.

Connect a spaceCopy Anchor Link

1. Go to Settings → Integrations: choose People in the sidebar, then the Integrations tab.
2. Under OpenSync, fill in:
   • Space link or ID: open the space in OpenSync and copy the address from the browser (https://opensync.space/spaces/…), or type just its ID.
   • Space token: the osk_… token.
   • Folder for meeting notes: where notes go inside the space. Default: Fishcamp/Meeting notes.
3. Choose Connect OpenSync.

Fishcamp checks the token with OpenSync before it saves anything. If OpenSync refuses, you see why, for example "OpenSync didn't accept the token for this space" or "OpenSync couldn't find this space". If OpenSync doesn't answer, you see "Couldn't reach OpenSync". Either way, nothing is saved.

If your team uses OpenSync at another address, choose Use a different OpenSync address and type it, for example https://api.opensync.space. It must be a public https address without a path.

What gets savedCopy Anchor Link

One Markdown note per audio room session, named after the time the room opened (UTC) and the channel:

Fishcamp/Meeting notes/2026-11-05 14-00 UTC · #planning.md

# 2026-11-05 14:00 UTC · #planning

Participants: Maya Lopes, Theo Park, Ana Souza (guest)

Source: Fishcamp audio room transcript (audio not stored).

## Transcript

- **14:02 Maya Lopes:** Let's ship the pricing page on Friday.
- **14:03 Theo Park:** I will update the copy by Thursday.

• Calls in a direct message are named direct call instead of the channel.
• Saving the same transcript again writes to the same note.
• The transcript then shows "Saved as" with the note's path, and the timeline says who saved it and where.

Check, edit or disconnectCopy Anchor Link

Once connected, the OpenSync card shows the space, the folder, the last characters of the token and when a note was last saved.

• Test connection asks OpenSync again and tells you whether it works.
• Edit changes the space, the folder or the address. To change only the folder, leave Space token blank to keep the current token. To change the space or the address, paste the token again: the stored token only works with the space and address it was saved for.
• Disconnect, after you confirm, removes the connection and the stored token. Transcripts stop going to OpenSync; notes already saved stay there.

If a save fails, the card says Connected, but the last attempt failed, with the reason.

When OpenSync isn't connectedCopy Anchor Link

If Save to OpenSync is chosen while the workspace has no connection, nothing leaves Fishcamp. The transcript shows Failed, and the timeline says: "OpenSync isn't connected to this workspace yet. An admin can connect it in Settings → Integrations". After connecting, open the transcript and choose Try again.

SecurityCopy Anchor Link

• The token is stored encrypted. The API never returns it: admins see only its last four characters, and everyone else only sees whether OpenSync is connected.
• One space only. The token can't reach other spaces, and Fishcamp only calls public https addresses, checked on every call.
• People only. Only admins connect, test and disconnect, and requests made with an API key are refused.

To do this from code, see Integration endpoints.