Integrations
Deliberately route conversations, forwarded email, meeting transcripts, and webhook payloads into Timeline, or select records from connected tools. Timeline keeps the origin clear while it turns that work into chronology and cited answers.
Create your TimelineSend work in
Send messages, files, forwarded email, meeting transcripts, or webhook payloads to Timeline. Each route makes it clear what is saved and who can see it.
Conversation and capture
Talk to Timeline in a linked DM or group, capture an explicit note, or send a file or voice memo into the same evidence pipeline.
Conversation and capture
Ask Timeline from Slack, capture deliberate notes, and route linked conversations, files, and voice memos into the record.
Team inbox
Forward, CC, or BCC a message to the team address so decisions and attachments do not disappear inside personal inboxes.
Start with Email forwardingTimeline captures
Message body, sender and recipient context, and supported file, document, and audio attachments.
What to know
Email enters only when the team address is included. Accepted messages from unknown senders are retained as unverified evidence rather than silently mapped to a member. When the team sender whitelist is enabled, messages from unlisted senders are rejected.
Google Meet · Microsoft Teams · Zoom
Invite a silent notetaker to a live call, then keep the transcript, speakers, summary, and action items with the rest of the work.
Start with Meeting transcriptsTimeline captures
Transcripts from Google Meet, Microsoft Teams, and Zoom calls after the scheduling gate is satisfied.
What to know
By default, the scheduler must confirm that participants will be informed before the bot joins. Team admins can disable this gate when they have another legal basis. Timeline stores the transcript, not a copy of the raw meeting audio; provider setup is required.
Custom evidence
Give an internal tool or unsupported service a named, authenticated endpoint that writes its payload into Timeline as source evidence.
Start with Ingest webhooksTimeline captures
JSON, form, CSV, XML, YAML, GraphQL, NDJSON, and other textual request bodies up to 1 MB.
What to know
Webhook payloads can support an answer, but they cannot update or control records in the sending tool. Direct file or binary upload uses a separate route.
02Connect your tools
Choose the repositories, teams, drives, boards, channels, and projects that belong in the record. Each integration page explains exactly what Timeline keeps, what stays in the original tool, and which permissions it needs.
Timeline preserves the messages, threads, file-share metadata, reactions, and edits you choose, then places them beside work from other systems. Ask what was decided and inspect the conversation behind the answer.
See records become answers
Timeline turns selected repository activity into a chronological, citable record. Follow work from issue through review and release without treating a pull request title as the whole story.
See records become answers
Timeline captures selected Linear teams as cited history, including issue context, comments, priority, ownership, status, and project changes. Connect plans to the conversations and code that made them real.
See records become answers
Timeline saves supported file changes it sees after Google Drive is connected, so later answers can cite the document state captured at the time. You can limit the connection to a shared drive; choosing My Drive currently also includes changed files the connected account can access through Shared with me and other shared drives.
See records become answers
Timeline captures selected Monday.com boards and WorkDocs without reducing them to status snapshots. See the updates, replies, owners, columns, and nested work that explain how an operational record changed.
See records become answers
Timeline turns selected Sentry issues, alerts, and releases into incident evidence you can connect to code and team discussion. Project selection applies to scheduled history checks; after one matching webhook, later webhook events from another project in the same Sentry installation may also be captured.
See records become answers03Proof
Start with one operating question. Timeline orders selected records by time, keeps their source attached, and cites the evidence used in the answer. This Slack example shows that journey from conversation to chronology.
Fictional Acme example, not customer data.
What did we decide about the Acme rollout?
Maya Chen proposes a staged launch
Priya Shah confirms the 18-team beta cohort
Migration risk shared in the thread
Immutable events keep their source and order.
The team chose a staged Acme rollout for an 18-team beta cohort, with migration risk reviewed before broad release.
04More connections
Some connections add selected records to your Timeline. Others look up approved tools only when you ask a question. Local connections require Timeline on the same computer, and integrations listed as coming later cannot be connected yet.
Telegram, Slack conversations, email forwarding, meeting transcripts, ingest webhooks
GitHub, Linear, Google Drive, Monday.com, Slack, Sentry
Notion, Jira, Confluence, Stripe
Figma. Available only when Timeline runs on the same machine; not connectable from hosted Timeline.
HubSpot, Salesforce, Attio, Asana, Trello, Basecamp, GitLab, Bitbucket, Datadog, Discord, Pipedrive, Close, Zendesk, Intercom