Skip to main content
Runa connects to Muse as a read-only connector. Once it’s connected, Muse can search your meetings, open a meeting’s summary, key takeaways, action items, and full transcript, look up the people and companies you meet with, and see your upcoming meetings. The connector’s server address is:

​
Connect in Muse

  1. In Muse, open Settings → Connectors.
  2. Select Connect next to Runa, then Continue.
  3. Sign in to Runa with Google or Microsoft.
You can also ask Muse to “connect my Runa account.”
New to Runa? Signing in with Google or Microsoft when you connect creates your account. Meetings come from the Runa desktop app, so a new account has nothing to search until you record your first meeting.

​
What you can ask

  • “What was my most recent meeting, and what do I need to do next?”
  • “Where did we discuss pricing with Acme, and what did we decide?”
  • “What did Dana commit to in our last call?”
  • “Prep me for my next meeting: who’s attending and what did we last discuss?”
  • “List my open action items from the last two weeks.”

​
What the connector can read

  • Meetings: titles, dates, participants, summaries, key takeaways, action items, and full transcripts.
  • Search: your meetings, notes, and the documents in your folders.
  • People and companies: what Runa remembers about the people and companies you meet with.
  • Upcoming meetings: the next week, read live from the Google and Outlook calendars you connected to Runa, with the desktop app’s last sync covering the rest.
  • Apps you connected to Runa: live, read-only data from HubSpot, Salesforce, Gmail, Outlook, Google Drive, Slack, Linear, Notion, and Basecamp.
Results are limited to what you can already open in Runa and to your organization’s policy for AI assistants. Audio recordings and voice profiles are never shared.

​
Tools

Every tool is a read. None creates, changes, sends, or deletes anything, so none is a write or a sensitive write, and none has side effects. Each one declares readOnlyHint: true and destructiveHint: false. Each tool returns JSON, as text and as structuredContent: the items it found, each with a runa:// id or a link back to its source, and a cursor when there are more pages. Required inputs are in bold.

​
Sign-in and permissions

Runa uses OAuth 2.1 with PKCE, and supports Dynamic Client Registration and Client ID Metadata Documents. Muse asks for all ten of Runa’s scopes, and every one of them is read-only: fetch and runa_fetch_resource_page need the scope for the kind of item they open. Access is checked again on every call, so disconnecting takes effect on the next one.

​
Errors and limits

  • App not connected: a connected-app tool returns a note saying how to connect the app in Runa, instead of data.
  • Long results: a long transcript or document comes back in pages, and the result says how to read the rest.
  • Organization policy: if your workspace admin turned off AI assistants or a kind of data, the result says so.
  • Disconnected: once you disconnect, the next call returns an error saying the connection is no longer valid. Connect Runa again to continue.
  • Rate limits: each connection has an hourly usage budget, and each app you connected to Runa has an hourly call limit per user. A call over either one returns an error saying how long to wait, and calls work again at the top of the hour.
Errors come back as tool results with isError: true and a plain-language message.

​
Disconnect

In Runa, open Settings → Connectors → AI assistants and switch off Muse. The connection stops working on its next request. You can also disconnect Runa in Muse under Settings → Connectors.

​
Get help

Email admin@joinruna.com.