// Reference

Connect company apps

Connect the systems that already hold useful work. The connection gives ArtifactBridge a controlled way to read or act through the account you authorized.

App	Use it for
Google Docs	Bring Google documents and sheets into the shared Library and keep source identity.
Notion	Bring pages into the Library and keep them connected to their source.
Linear	Bring documents and issues into the workspace; connected workflows can also work around issue context.
Microsoft OneDrive	Bring supported text, Markdown and Word documents into the Library as a read-only source.
GitHub	Bring a repository or part of one through a reviewed import plan.
Slack	Connect a review channel, approvers, and supported workflow delivery from the Agent settings.
GitHub App	Post failed CI results and merge conflicts on a pull request into the rooms that have that pull request attached.

For document sources and the GitHub App, open Settings → Connected apps. Slack is managed from the Agent settings rather than the Connected apps list.

Connect an account and import content

Open Settings → Connected apps and choose the provider.
Sign in to the intended provider account and review the requested permission.
Return to ArtifactBridge and check the connection state.
Open Import and browse the documents or folders that account can access.
Select the source material and check the destination and import result.

Connecting an account makes a source available; it does not import everything in it. Source permissions, supported file types, and provider limits still apply.

Refresh a connected document

Open a synced document to inspect its source and freshness. A refresh reads the provider’s current content into ArtifactBridge. If a read fails, an earlier synced version may still be available; check its timestamp before relying on it. Reconnect the source when its authorization has expired or been revoked.

Source reads and agent actions

Connected document sources are read-only through the document workflow. Separately, Settings → Agent configures the built-in agent’s GitHub, Linear, and Slack capabilities. An owner can enable supported reads and scope the connection. Supported actions such as posting a GitHub comment or creating a Linear issue require the approval shown in the app.

Slack and knowledge collection

The Slack connection and its channel settings live under Settings → Agent. A company owner manages them. The agent can use the configured Slack sources for supported conversations and knowledge collection. Settings → Agent → Harvest shows harvest runs and findings. A harvest is a scan that extracts useful knowledge from the configured sources.

Inspect the run result and review a finding in the Inbox before accepting it. A skipped, rate-limited, or failed scan does not mean the source had no useful information. Harvest categories organize findings; they do not define who can access them. See Collect and review knowledge.

In the Slack settings, select Add to Slack and authorize the intended Slack workspace.
Return and confirm the Installed state.
Select the review channel and choose Save.
Map each Slack approver to the correct ArtifactBridge workspace member.
Check the mapping before relying on Slack decisions. Remove mappings for people who no longer belong to the workspace.

If installation reports a workspace conflict, that Slack workspace is already connected to a different ArtifactBridge workspace. Resolve the existing connection before trying again. Workflow delivery to Slack is a separate output setting on each workflow.

GitHub App: CI results in rooms

The ArtifactBridge GitHub App reports CI results on pull requests to your rooms. When CI fails on a pull request, ArtifactBridge posts one event in each open room that has that pull request attached. When a later commit of the same pull request passes the same CI check, ArtifactBridge posts one “back to green” event. The App also posts a merge conflict: when a pull request can no longer merge into its base branch, for example after the base branch moves, ArtifactBridge posts one “Merge conflict” event in each open room that has the pull request attached, and one “Merge conflict resolved” event when a later commit can merge again. This needs nothing new from the installer. The GitHub App is separate from the GitHub connection that imports repositories. ArtifactBridge 0.5.116 and later wake the room’s agents whose runtime is enabled for wakes in the ArtifactBridge app. Other agents see the event the next time they read the room.

Who can install it. A workspace owner installs the App from Settings → Connected apps with Install GitHub App. The owner must also be allowed to install GitHub Apps on the GitHub organization or account. Every workspace member can see the installations. If the row shows Not available on this deployment, this ArtifactBridge deployment has no GitHub App.

Permissions. The App asks for read-only access: Actions, Checks, Pull requests, and Metadata. It cannot write to GitHub.

What is posted in a room. Each event contains the CI name, the conclusion, the short commit SHA, and a link to the run on GitHub. Logs, pull request text, commit messages, and the name of the person who pushed are not posted.

Attach the pull request. Only rooms that have the pull request attached receive events. A result for a pull request with no attached room is not stored. Archived rooms receive nothing. To attach the pull request to a room that exists, an agent that joined the room calls artifactbridge_attach_work_object_to_agent_room. The agent gives owner/repo#N in the exact letter case that GitHub shows, or the pull request URL. To start a new room for the pull request, an agent calls artifactbridge_open_agent_room with provider github, object type pull_request, and external id owner/repo#N. A bare number, such as 3594, does not work, because it does not identify the repository. Automatic attach from the branch name. When the branch name of a pull request contains a Linear issue key, for example ai-123-short-name, and exactly one open room in the workspace has that Linear issue attached, ArtifactBridge attaches the pull request to that room by itself on the next GitHub Actions workflow run of the pull request. CI results and merge conflicts of that run and later runs then reach that room as described above. If no open room has the issue, or more than one has it, nothing is attached: attach the pull request by hand as before.

Open Settings → Connected apps and select Install GitHub App.
On GitHub, choose the organization or account and the repositories, then install.
Return to ArtifactBridge and confirm the message GitHub App connected and the new installation row.
Attach the pull request to a room. Ask an agent that joined the room to call artifactbridge_attach_work_object_to_agent_room with owner/repo#N or the pull request URL. Or ask an agent to open a new room for the pull request with artifactbridge_open_agent_room. CI results on that pull request now reach the room.

If the install reports that the installation is already connected to another workspace, disconnect it there first. To add another organization, select Install GitHub App again.

Disconnect and uninstall. A workspace owner selects Disconnect on the installation row. This unlinks the App in ArtifactBridge only: CI results stop reaching rooms in this workspace, and the App stays installed on GitHub. To remove it from GitHub too, follow the uninstall it on GitHub link in the confirmation, or select Manage on GitHub on the row. If a GitHub admin uninstalls or suspends the App on GitHub, ArtifactBridge stops posting results for it. Events already posted stay in the room.

Disconnect or repair a connection

Check the provider account and permission when expected content is missing. Reauthorize through Settings when required. Disconnecting a source stops future use of that connection; it does not imply that already imported content or previously posted comments were removed. Review those items separately.