Integrations

How Integrations Work

Integrations let Deep Notebook research across the tools and sources you already use. Depending on the connected app, a run can inspect files, messages, issues, documents, spreadsheets, repositories, and other work context.

Connections happen at the account level. Connect an app once, then choose the relevant connected sources when setting up a research session.

When to Use Integrations

Use integrations when the answer depends on private or team-specific context:

• •Customer, sales, or support history
• •Internal planning documents and spreadsheets
• •Project discussion in Slack or Teams
• •Engineering context from GitHub, Linear, or Jira
• •Existing research, notes, decks, or memos in Drive or Notion

For public-only research, a brief with domain filters may be enough. For internal or mixed-source research, integrations give the agent the context it cannot find on the open web.

Source Control

Only connect sources that are relevant to the session. Narrow source selection improves quality, reduces noise, and makes the final report easier to audit.

If you attach files, they become part of the research context for that session. If you select connected tools, the run can use those tools according to the permissions granted by the integration.

Security and Privacy

Deep Notebook uses OAuth or the provider's supported authentication flow where available. We do not ask for your app passwords. You can revoke connected apps from integration settings.

Treat connected sources as part of the research scope. If a run should not use a system or dataset, leave it out of the session.

Requesting New Integrations

Don't see a source you need? Let us know at madhava@autocomputer.ai. We prioritize integrations that unlock higher-quality research for common analyst and knowledge-work use cases.