The decision
Recover the meeting note and the evidence behind the choice.
The work
Connect the follow-up discussion, document and task without losing source meaning.
The outcome
Prepare the context and compare the resulting work against its acceptance criteria.
Slack
COLLABORATIONSelected channels, threads and decisions.
Scope & limits
- Example audience
- product and service teams.
- Important boundary
- Declared history coverage and access scope.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Microsoft Teams
COLLABORATIONSelected chats, channels and eligible transcripts.
Scope & limits
- Example audience
- enterprise and education.
- Important boundary
- Chat and transcript access are separate.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
WhatsApp Business
COLLABORATIONAuthorised business messaging.
Scope & limits
- Example audience
- retail, hospitality and services.
- Important boundary
- Personal exports are a separate import path.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Telegram
COLLABORATIONBot-visible channels/chats and selected exports.
Scope & limits
- Example audience
- communities and operations.
- Important boundary
- No whole-account history promise.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Granola
MEETINGSAuthorised notes and available transcripts.
Scope & limits
- Example audience
- product, consulting and sales.
- Important boundary
- Access depends on supported workspace capabilities.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Zoom
MEETINGSExisting authorised meeting artifacts.
Scope & limits
- Example audience
- sales, consulting and education.
- Important boundary
- A recording reference is not a transcript.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Google Meet
MEETINGSAvailable meeting artifacts and transcripts.
Scope & limits
- Example audience
- Workspace teams.
- Important boundary
- Artifacts must exist and remain accessible.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Google Calendar
CALENDARSelected events and meeting chronology.
Scope & limits
- Example audience
- cross-industry.
- Important boundary
- Private events, recurrence and time zones.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Outlook Calendar
CALENDARSelected events and meeting chronology.
Scope & limits
- Example audience
- Microsoft 365 teams.
- Important boundary
- Separate product from Outlook email.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Google Drive
KNOWLEDGESelected files, folders and supported exports.
Scope & limits
- Example audience
- cross-industry.
- Important boundary
- File restrictions and source permissions.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Notion
KNOWLEDGEAuthorised pages, blocks and records.
Scope & limits
- Example audience
- startups and agencies.
- Important boundary
- Shared scope and unsupported blocks remain visible.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Confluence
KNOWLEDGEPermitted spaces, pages and comments.
Scope & limits
- Example audience
- software and enterprise IT.
- Important boundary
- Page restrictions and deployment edition.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Obsidian
KNOWLEDGESelected local Markdown vault.
Scope & limits
- Example audience
- research and development.
- Important boundary
- Local companion and selected paths.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Linear
PROJECTSIssues, projects and comments.
Scope & limits
- Example audience
- software and product.
- Important boundary
- Authoritative issue status stays in Linear.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Jira
PROJECTSSelected projects, issues and comments.
Scope & limits
- Example audience
- enterprise IT and services.
- Important boundary
- Issue security and deployment edition.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Gmail
EMAILSelected messages and attachments.
Scope & limits
- Example audience
- small teams, sales and services.
- Important boundary
- Explicit read scopes and mailbox identity.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Outlook / Microsoft 365 Mail
EMAILSelected messages and attachments.
Scope & limits
- Example audience
- enterprise teams.
- Important boundary
- Shared mailbox grants are separate.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Zoho CRM
CRMAccounts, contacts, deals and notes.
Scope & limits
- Example audience
- small businesses and sales.
- Important boundary
- Other Zoho products have separate connection scopes.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Zendesk
SUPPORTPermitted tickets, comments and help articles.
Scope & limits
- Example audience
- SaaS and ecommerce.
- Important boundary
- Internal notes retain their audience restrictions.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Shopify
COMMERCEProducts and permitted order context.
Scope & limits
- Example audience
- retail and DTC.
- Important boundary
- Customer fields depend on approved scope.
- Access & processing
- The source account, granted permissions and selected processing route define the records this connection can use.
- Source continuity
- Source references and access boundaries stay attached to the knowledge used in a task.
Know what each integration brings into the task.
Integration scope is product-specific. Account access, supported records and processing boundaries determine what a connection can do.
Useful scope
Supported records, account requirements, history coverage and source-specific limits.
Clear boundaries
Required scopes, processing routes and permission handling, including when access changes.
Ongoing reliability
Refresh behaviour, source health and recovery from interrupted jobs.
GitHub, local Git, authorised conversation exports and supported agent adapters extend the workflow. Import-only paths remain distinct from live product integrations.
Discuss the connections your team uses