Connect sources
Connect Slack, Google Drive, Gmail, Notion, GitHub, Jira and Linear, see what is syncing, reconnect an expired sign-in, and disconnect safely.
A source is a tool Breno reads from. Once connected, its content arrives as items that keep a link to the original, and stay in step as it changes.
Connect an app#
- Open Sources in the left navigation and stay on Browse.
- Search, or filter by category and status. Apps that bring knowledge in carry an Ingests knowledge badge.
- Select the app, then Connect it. You sign in to the app in a popup (OAuth) or paste an API key, depending on the app.
- When the popup closes, the app moves to Connected and its first sync is queued.
Connecting and disconnecting sources is limited to people who can manage the workspace (Owners and Admins). See Roles and permissions.
What syncs, and how#
- Sync runs on a durable queue, in the background, fairly across workspaces, with a limit on how fast each provider is called so a busy provider slows a sync down instead of failing it.
- A first sync backfills everything the app lets Breno list. Very large sources continue across batches until done.
- Slack and GitHub also notify Breno when something changes, so those syncs start within seconds.
- Each item records its connection, the item's id in the source, its address, its author and the times it was created and changed at the source.
Edits and deletions#
| At the source | In Breno |
|---|---|
| An item is edited | The same item is updated, its previous text is kept as a version, and it is re-indexed. |
| An item is deleted | It moves to Trash (it is not purged straight away), for the apps that report deletions. |
| The listing is incomplete or capped | Nothing is deleted. The sync log says the listing was partial and skips removal. |
Slack and Teams messages arrive as per-sync digests, and a Slack message that is deleted or edited is applied to that one message. Some apps give Breno no deletion signal at all (Teams, Linear, GitLab, Asana, ClickUp, HubSpot, Salesforce), so an item deleted there stays in Breno until you remove it.
See what is happening#
The Connected tab lists each connection with its state. Open its activity drawer to see recent jobs, logs and health, including per-kind errors when a sync partially failed.
Reconnect#
If a sign-in expires or is revoked, the connection shows Reconnect. It re-authorizes the same connection, so its settings and history are kept.
Disconnect#
Disconnect removes the stored tokens. You choose whether the items it brought in stay in your knowledge or move to trash.
Limits to know about#
- Full listings are capped per provider. Beyond the cap, deletions are not propagated, and the job log says so.
- Breno is built for a thousand connected sources. A test at that scale did not meet its latency target, so treat a thousand as a goal. See Known limits.
- Connecting an app does not copy its permissions. Items arrive with Breno's defaults (workspace-visible, sensitivity
internal), so review what a private source brings in. See How access works.