This PR adds a connector for Outline.

Demo Video

Here’s a short demo showing the Outline connector in action:
https://www.youtube.com/watch?v=PHSSaawpFGc

Outline has a pretty straightforward model with collections and documents, so the connector pulls those in through the Outline API. Collections work like folders, and documents hold the actual content.

To build this, I used the BookStack connector as a guide since the flow is quite similar. I swapped in the Outline API calls and adjusted the transforms so the data maps cleanly into the Onyx document model.

I tested against a local Outline instance using an API token, and everything synced as expected. Collections and documents show up with titles, text, links back to Outline, and update timestamps. Polling also works with batch size so larger spaces can be processed in steps.

For setup, it’s kept simple. You just provide the base URL of your Outline workspace and an API token. With that, the connector can walk through all the content.

I added the icon, credential form, and config so Outline appears in the UI the same way as other sources.

I’m not a Python, so there might be some style tweaks needed, but functionally the connector is in place and ready.

/claim #3256

Summary by cubic

Adds an Outline connector that syncs collections and documents via the Outline API, with UI wiring, credential validation, and batching for large workspaces. Implements the requirements from Linear #3256.

• New Features

  • New Outline connector (backend + UI) for collections and documents.
  • Pagination-based polling; maps title, text, link, and updatedAt to Onyx docs.
  • Credential validation via auth.info with clear 401/403 errors.
  • Registered DocumentSource.OUTLINE, factory wiring, and Slack icon.
  • UI: source metadata, icon, connector config, and credential form.

• Migration

  • Provide Outline Base URL and API Token in the connector setup.
  • Works with hosted or self-hosted Outline.
  • Use “Test connection” to verify token permissions.