Integrations

Guide

Loading this Timeline guide.

Connected sources

First-party integrations and ingest paths can create durable evidence. MCP servers give the agent live reach into approved tools; successful team-shared results become team-visible evidence, while personal-server results stay private to their owner. MCP is not passive provider sync.

Google Drive syncs selected folders and files into the document drive.

GitHub and Linear bring engineering and project activity into the operational record.

Monday.com syncs selected boards, generic records, subitems, updates, columns, and WorkDocs.

Slack workspace ingestion syncs selected channels, threads, files, reactions, and edits.

Sentry syncs issue updates, resolved issues, and releases into cited events, evidence clusters, and customer/project associations.

Slack, Telegram, email, and meeting bots are capture surfaces for conversations and calls.

Custom MCP servers expose approved live tools and context to the agent; successful team-shared results become team-visible evidence, while personal-server results stay private to their owner. Passive provider activity still needs native sync or custom ingestion.

Security model

OAuth tokens and bearer secrets are encrypted at rest. Imported snippets are treated as external content before the agent sees them.

Admins control team-level source activation.

Connection owners control what provider resources are shared.

For Monday.com, selecting a parent board also captures its classic subitems; hidden “Subitems of …” helper boards are not selected separately.

Personal MCP connections are visible only to their owner.

Outbound Timeline MCP keys see only team-visible events.

Use Timeline from an agent

External agents can connect to Timeline through the outbound MCP endpoint. The GitHub plugin bundles that hosted connection with one general skill for choosing Timeline tools, expanding source evidence, and citing claims.

An administrator creates a bearer key on the Timeline MCP endpoint page; its plaintext is shown once.

Codex users can install the full plugin or the standalone Timeline skill for a self-hosted Timeline.

Default keys are read-only. Timeline agent access is a separate, optional scope for paid, proposal-only turns.

Connected sources

Google Drive syncs selected folders and files into the document drive.

GitHub and Linear bring engineering and project activity into the operational record.

Monday.com syncs selected boards, generic records, subitems, updates, columns, and WorkDocs.

Slack workspace ingestion syncs selected channels, threads, files, reactions, and edits.

Sentry syncs issue updates, resolved issues, and releases into cited events, evidence clusters, and customer/project associations.

Slack, Telegram, email, and meeting bots are capture surfaces for conversations and calls.

Security model

OAuth tokens and bearer secrets are encrypted at rest. Imported snippets are treated as external content before the agent sees them.

Admins control team-level source activation.

Connection owners control what provider resources are shared.

For Monday.com, selecting a parent board also captures its classic subitems; hidden “Subitems of …” helper boards are not selected separately.

Personal MCP connections are visible only to their owner.

Outbound Timeline MCP keys see only team-visible events.

Use Timeline from an agent

An administrator creates a bearer key on the Timeline MCP endpoint page; its plaintext is shown once.

Codex users can install the full plugin or the standalone Timeline skill for a self-hosted Timeline.

Default keys are read-only. Timeline agent access is a separate, optional scope for paid, proposal-only turns.

Guide

Integrations

Connected sources

Security model

Use Timeline from an agent

Related

Guide

Integrations

Connected sources

Security model

Use Timeline from an agent

Related

Help

Connected sources

Security model

Use Timeline from an agent

Related

Connected sources

Security model

Use Timeline from an agent

Related