Skip to content
OverlordThe Docs

Integrations

Integrations connect Overlord with external providers and agent tools. Configure them from the workspace or project settings, then test the connection before relying on it in an automated workflow.

The integration catalog and available permissions can vary by deployment. Only enable the providers your team needs.

Available integrations

Section titled “Available integrations”
  • Knowledgebase — let the Overlord assistant read your notes, and edit them when you allow it.
  • Everhour — time tracking synced to your missions and projects.
  • Webhooks — send mission events to your own external systems.

Knowledgebase

Section titled “Knowledgebase”

Connect your personal Knowledgebase account so the Overlord assistant can read your notes in the organization you are working in. On Overlord Cloud nothing needs to be set up first.

  1. Open Connected accounts. In Overlord, open Settings → Connected accounts (or the Knowledgebase shortcut in Chat).
  2. Click Connect. Overlord sends you to the Knowledgebase sign-in page.
  3. Sign in and approve access. Choose which Knowledgebase workspaces Overlord may read, then approve.
  4. Check the result. You return to Connected accounts. The Knowledgebase row shows Connected, the workspaces you shared, and the server it is connected to.

Notes:

  • The connection belongs to you, in this organization only. Teammates connect their own accounts.
  • Overlord stores the sign-in encrypted on the server. It never sends it to your browser or to agents.
  • The assistant only reads your notes by default. It can edit a workspace only when you allow edits for that one message.
  • To skip asking each time, turn on Let the assistant edit notes in all authorized workspaces on the Knowledgebase row. The assistant can then read and write every workspace you shared, in any conversation. Turn it off to go back to per-message edits; it takes effect immediately, even for a conversation already running.
  • If you cancel the sign-in, nothing is connected. Click Connect again whenever you are ready.
  • Needs reconnecting means the sign-in expired or was revoked. Click Reconnect to sign in again.
  • Disconnect erases the stored sign-in and revokes it in Knowledgebase. Conversations that cited your notes then show those sources as unavailable.
  • Not configured on this server means an administrator turned Knowledgebase off, or the server cannot store credentials securely yet. Ask your administrator.

For administrators

Section titled “For administrators”

Knowledgebase works without extra settings. The backend connects to the standard server, https://knowledge.chaselubitz.com/mcp. It encrypts credentials with a key derived from the deployment’s BETTER_AUTH_SECRET. These settings are optional:

  • KNOWLEDGEBASE_MCP_URL: another HTTPS server, or off to turn Knowledgebase off. The backend only contacts that server’s origin and any KNOWLEDGEBASE_EGRESS_ORIGINS you list.
  • ACCOUNT_CONNECTIONS_ENCRYPTION_KEY: a dedicated 32-byte credential key. When you add one, existing connections are re-encrypted with it the next time they are used. Nobody has to reconnect.

Keep BETTER_AUTH_SECRET stable. If you change it while no dedicated key is set, everyone has to reconnect Knowledgebase.

Everhour

Section titled “Everhour”

Connect an Everhour account to track time directly from Overlord missions.

Everhour timers are per user, so each teammate adds their own API token.

  1. Get your API token. In Everhour, open Settings → My Profile and copy the value under API Token.
  2. Save it in Overlord. Open your account settings, paste the key into the Everhour section, and save. The key is stored per user with row-level security.
  3. Sync a project. Open a mission in the target organization, and in the Project section choose Sync Projects to Everhour. Synced projects show an (Everhour) marker in the dropdown.
  4. (Optional) Share one Everhour project across several Overlord projects so their time rolls up together — under a project’s Settings → Integrations, link an Everhour project already connected to another Overlord project in the same organization.
  5. Verify. Open any mission, start and stop a timer under Time Tracking, and confirm entries appear.

Notes:

  • Timers are per user, and only one can run at a time — starting a timer on another mission stops the previous one.
  • A mission must have a project assigned, and that project must be synced to Everhour.

Related: Webhooks · Credentials and external providers