Pantasso
Plan an evaluation

Setup guides

Source Connection Guide

Step-by-step instructions for connecting approved messaging, documents, project systems, CRM, files, databases, and structured imports.

Status: Live · Updated 2026-07-12

Source Connection Guide

Use this guide to bring approved company information into Pantasso without opening up an entire account or workspace. Start with one channel, folder, or project that can answer a useful question, then add sources as the need becomes clear. The Pantasso Connector Directory lists the available connection paths.

Availability varies by connector. The directory distinguishes app connections that are live now from developer/runtime paths and planned work.

Before you start

  • You need workspace owner access to connect sources.
  • Start with one source that matters this week. You can add more later.
  • Pantasso only accesses what you explicitly approve.
  • Hosted-flow connectors are added from the workspace control plane.
  • Runtime-complete expansion connectors use a connector manifest, server-side credential reference, approved targets, and the same checkpointed sync and audit contract.

Slack

Connect Slack to bring channel messages, threads, and decisions into your workspace.

  1. From the workspace control plane, select Add Source and choose Slack.
  2. Authorize Pantasso to access your Slack workspace.
  3. Select the specific channels you want to connect. You do not need to connect all channels.
  4. Pantasso imports messages and threads from approved channels.

What Pantasso sees: Only messages from channels you select. Private channels require explicit approval from the channel owner.

Google Drive

Connect Google Drive to bring shared files, folders, and documents into your workspace.

  1. Select Add Source and choose Google Drive.
  2. Authorize with your Google account.
  3. Select specific folders to connect. Pantasso does not access your entire Drive.
  4. Files in selected folders are imported and indexed.

What Pantasso sees: Only files in folders you approve. Shared drives require the same folder-level approval.

Google Docs

Connect Google Docs to bring documents, specs, and notes into your workspace.

  1. Select Add Source and choose Google Docs.
  2. Authorize with your Google account.
  3. Select specific documents or folders containing documents.
  4. Document content is imported with full text.

What Pantasso sees: Only the documents you select or documents within approved folders.

Gmail

Connect Gmail when approvals, commitments, handoffs, or support context live in email.

  1. Select Add Source and choose Gmail.
  2. Authorize with the approved Google account or use the workspace's managed Google connection.
  3. Choose the mailbox user, query, labels, and spam/trash policy.
  4. Pantasso imports the bounded message and thread context.

What Pantasso sees: Only the approved mailbox scope and query result set.

Google Calendar

Connect Google Calendar when meetings, deadlines, attendees, or operating rhythm should inform workspace answers.

  1. Select Add Source and choose Google Calendar.
  2. Authorize with the approved Google account or managed Google connection.
  3. Choose the calendars and time windows Pantasso may read.
  4. Pantasso imports approved event context and freshness metadata.

What Pantasso sees: Only events from approved calendars and time bounds.

Google Sheets

Connect Google Sheets when important trackers, lists, budgets, or operating tables live in spreadsheets.

  1. Select Add Source and choose Google Sheets.
  2. Authorize with the approved Google account or managed Google connection.
  3. Choose specific spreadsheets and tab ranges.
  4. Pantasso imports rows and range context into governed workspace objects.

What Pantasso sees: Only the spreadsheet ids and ranges you approve.

Google Admin Directory

Connect Google Admin Directory when Pantasso should understand users, groups, teams, and account context for identity resolution.

  1. Select Add Source and choose Google Admin Directory.
  2. Use the approved Google Workspace admin connection.
  3. Choose whether users, groups, or both should be included.
  4. Pantasso imports directory context for people, teams, and source ownership.

What Pantasso sees: Only the approved directory users and groups.

Microsoft 365

Connect Microsoft 365 when Teams, Outlook, SharePoint, OneDrive, Planner, or Entra ID are core operating sources.

  1. Create a Microsoft 365 connector manifest for the approved tenant.
  2. Store the Microsoft Graph credential as a server-side secret reference.
  3. Choose Graph targets such as users, groups, Teams channel messages, mail, calendar events, drive items, or Planner tasks.
  4. Run preflight, then sync the bounded targets with Graph pagination checkpoints.

What Pantasso sees: Only approved Graph resources and target windows. Graph credentials are not exposed to agents.

Telegram

Connect Telegram to bring group chats and operating conversations into your workspace.

  1. Select Add Source and choose Telegram.
  2. Connect the Pantasso bot to your Telegram group.
  3. Select which groups the bot should read from.
  4. Messages from approved groups are imported.

What Pantasso sees: Only messages from groups where the bot has been added and approved.

GitHub

Connect GitHub when issues, pull requests, comments, and engineering context are part of the company operating record.

  1. Select Add Source and choose GitHub.
  2. Authorize the provider connection or use the workspace's managed credential.
  3. Choose approved repositories and whether issues, pull requests, and comments should be included.
  4. Pantasso imports bounded repository context for project memory and cited answers.

What Pantasso sees: Only approved repositories and selected record types.

Notion

Connect Notion when team knowledge lives in pages, databases, notes, or wikis.

  1. Select Add Source and choose Notion.
  2. Connect the approved Notion integration.
  3. Choose visible pages or databases, or use a narrow search query.
  4. Pantasso imports page and database context with source provenance.

What Pantasso sees: Only pages and databases visible to the connected integration and selected by the workspace owner.

Linear

Connect Linear when product work, bugs, projects, and status live in issues.

  1. Select Add Source and choose Linear.
  2. Connect the approved Linear account or managed token.
  3. Choose issues, projects, and archived-work policy.
  4. Pantasso imports active product execution context.

What Pantasso sees: Only approved issue and project scope.

Jira Cloud

Connect Jira Cloud when tickets, epics, projects, and sprint boards are the work system of record.

  1. Select Add Source and choose Jira Cloud.
  2. Connect the approved Jira site.
  3. Choose project keys or a narrow JQL query.
  4. Pantasso imports bounded ticket context with checkpointed sync.

What Pantasso sees: Only the approved site, projects, and JQL result set.

HubSpot

Connect HubSpot when contacts, companies, deals, tickets, and CRM context should inform workspace answers.

  1. Select Add Source and choose HubSpot.
  2. Connect the approved HubSpot private app or managed credential.
  3. Choose the object types and archived-record policy.
  4. Pantasso imports approved CRM context for cited retrieval and operating briefs.

What Pantasso sees: Only approved HubSpot objects and properties.

Salesforce

Connect Salesforce when account, opportunity, case, task, or campaign context should be part of the governed company record.

  1. Create a Salesforce connector manifest with the approved object allowlist.
  2. Store the Salesforce credential as a server-side secret reference.
  3. Choose SOQL bounds for each object type.
  4. Run preflight, then sync with timestamp checkpoints.

What Pantasso sees: Only approved Salesforce objects, fields, and SOQL result sets.

Stripe

Connect Stripe when billing events, charges, invoices, subscriptions, products, or account records should support operations and audit review.

  1. Create a Stripe connector manifest with approved event and resource targets.
  2. Store the Stripe API credential as a server-side secret reference.
  3. Choose event types and resource windows.
  4. Run preflight, then sync with cursor checkpoints.

What Pantasso sees: Only approved Stripe events and resource records.

Shopify

Connect Shopify when commerce orders, products, fulfillments, inventory, and contact records should join support, finance, and operations context.

  1. Create a Shopify connector manifest for the approved shop domain.
  2. Store the Shopify Admin API credential as a server-side secret reference.
  3. Choose resources and date windows.
  4. Run preflight, then sync bounded pages into canonical workspace records.

What Pantasso sees: Only approved Shopify resources and date windows.

QuickBooks Online

Connect QuickBooks Online when invoices, bills, payments, vendors, items, or accounts should inform finance and operations questions.

  1. Create a QuickBooks connector manifest for the approved realm.
  2. Store the accounting API credential as a server-side secret reference.
  3. Choose resource targets and query bounds.
  4. Run preflight, then sync with updated-time checkpoints.

What Pantasso sees: Only approved QuickBooks resources and query result sets.

Xero

Connect Xero when invoices, contacts, bills, payments, bank transactions, or accounts should be available for finance context.

  1. Create a Xero connector manifest for the approved tenant.
  2. Store the accounting API credential as a server-side secret reference.
  3. Choose resource targets and updated-time bounds.
  4. Run preflight, then sync checkpointed finance records.

What Pantasso sees: Only approved Xero resources and tenant-scoped records.

Vercel

Connect Vercel when projects, deployments, and release context are part of company operations.

  1. Select Add Source and choose Vercel.
  2. Connect the approved Vercel account or managed token.
  3. Choose team or project targets and whether deployments should be included.
  4. Pantasso imports release and deployment context for operations memory.

What Pantasso sees: Only approved Vercel teams, projects, and deployments.

GitLab

Connect GitLab when groups, projects, issues, merge requests, pipelines, and commits should support delivery memory.

  1. Create a GitLab connector manifest for approved groups or projects.
  2. Store the GitLab credential as a server-side secret reference.
  3. Choose issue, merge request, pipeline, commit, and note targets.
  4. Run preflight, then sync with cursor or updated-time checkpoints.

What Pantasso sees: Only approved GitLab groups, projects, and resources.

Bitbucket

Connect Bitbucket when repositories, pull requests, issues, commits, and pipelines should be available for project context.

  1. Create a Bitbucket connector manifest for approved workspaces and repos.
  2. Store the Bitbucket credential as a server-side secret reference.
  3. Choose resource targets and page bounds.
  4. Run preflight, then sync checkpointed code-work records.

What Pantasso sees: Only approved Bitbucket workspaces, repositories, and resources.

PagerDuty

Connect PagerDuty when incidents, services, escalation policies, on-call schedules, and status updates should be searchable.

  1. Create a PagerDuty connector manifest for approved teams or services.
  2. Store the PagerDuty credential as a server-side secret reference.
  3. Choose incident windows and service targets.
  4. Run preflight, then sync incident and escalation context.

What Pantasso sees: Only approved PagerDuty services, schedules, incidents, and users.

Datadog

Connect Datadog when monitors, events, incidents, service catalog entries, dashboards, or SLOs should support operations review.

  1. Create a Datadog connector manifest for the approved site and account.
  2. Store the Datadog credential as a server-side secret reference.
  3. Choose resource targets and time windows.
  4. Run preflight, then sync with timestamp checkpoints.

What Pantasso sees: Only approved Datadog resources and time windows.

Sentry

Connect Sentry when issues, events, releases, commits, and alerts should support error triage and release review.

  1. Create a Sentry connector manifest for approved organizations and projects.
  2. Store the Sentry credential as a server-side secret reference.
  3. Choose issue, event, release, commit, and alert targets.
  4. Run preflight, then sync bounded records into engineering context.

What Pantasso sees: Only approved Sentry organizations, projects, and resources.

Cloudflare

Connect Cloudflare when zones, DNS records, firewall events, logs, Workers, Pages projects, or analytics should support edge operations.

  1. Create a Cloudflare connector manifest for approved accounts and zones.
  2. Store the Cloudflare credential as a server-side secret reference.
  3. Choose resources and time windows.
  4. Run preflight, then sync edge and security context.

What Pantasso sees: Only approved Cloudflare accounts, zones, and resources.

AWS CloudTrail

Connect AWS CloudTrail when account activity, service actions, identities, resources, and regions should be audit-ready.

  1. Create a CloudTrail connector manifest for approved accounts and regions.
  2. Store the AWS credential as a server-side secret reference.
  3. Choose lookup attributes, event windows, and region targets.
  4. Run preflight, then sync event history with timestamp checkpoints.

What Pantasso sees: Only approved CloudTrail event windows and account or region scope.

Obsidian

Connect Obsidian vaults by uploading vault folders through the Files source.

  1. Select Add Source and choose Files.
  2. Upload your Obsidian vault folder or specific note folders.
  3. Markdown notes are imported and indexed.

What Pantasso sees: Only the files you upload. Your local vault is not accessed directly.

Files

Upload individual files directly to your workspace.

  1. Select Add Source and choose Files.
  2. Upload Markdown, text, or JSON files.
  3. Files are imported and indexed immediately.

Supported formats: Markdown (.md), plain text (.txt), and JSON (.json).

Supabase

Connect Supabase when application tables should join the company data plane.

  1. Configure a Supabase source with the approved project URL and credential reference.
  2. Choose specific tables and row identity columns.
  3. Run source doctor before ingest.
  4. Pantasso imports bounded table records with checkpoints and source payloads.

What Pantasso sees: Only the approved tables and rows available to the configured key.

Structured Database

Connect a structured database when approved operational tables or analytical query results should become part of Pantasso.

  1. Create a structured database connector manifest.
  2. Store the connection credential as a server-side secret reference.
  3. Choose table allowlists, query bounds, identity columns, and timestamp checkpoints.
  4. Run preflight, then sync bounded rows with replayable payload evidence.

What Pantasso sees: Only approved tables or query result sets.

MCP-Compatible JSON

Connect MCP-compatible JSON imports when external agent-memory exports or structured JSON records should be normalized into Pantasso.

  1. Configure a JSON file path or protected JSON URL.
  2. Add an optional bearer-token reference if the URL is protected.
  3. Run source doctor before ingest.
  4. Pantasso imports records idempotently using hash checkpoints.

What Pantasso sees: Only the configured JSON file or URL payload.

Zendesk

Connect Zendesk when tickets, comments, users, organizations, or help-center articles should be part of support and operations context.

  1. Create a Zendesk connector manifest for the approved subdomain.
  2. Store the Zendesk credential as a server-side secret reference.
  3. Choose ticket query bounds and whether comments or help-center articles are included.
  4. Run preflight, then sync with updated-time checkpoints.

What Pantasso sees: Only approved Zendesk tickets, comments, users, organizations, and articles.

Intercom

Connect Intercom when conversations, conversation parts, companies, contacts, admins, or tags should support team memory.

  1. Create an Intercom connector manifest for the approved workspace.
  2. Store the Intercom credential as a server-side secret reference.
  3. Choose conversation, contact, company, admin, and tag targets.
  4. Run preflight, then sync with cursor checkpoints.

What Pantasso sees: Only approved Intercom resources.

Freshdesk

Connect Freshdesk when tickets, conversations, contacts, companies, agents, or solution articles should be searchable with citations.

  1. Create a Freshdesk connector manifest for the approved domain.
  2. Store the Freshdesk credential as a server-side secret reference.
  3. Choose resource targets and updated-time bounds.
  4. Run preflight, then sync bounded support records.

What Pantasso sees: Only approved Freshdesk resources and date windows.

Help Scout

Connect Help Scout when mailboxes, conversations, threads, teams, users, or docs should support inbox and knowledge context.

  1. Create a Help Scout connector manifest for approved mailboxes.
  2. Store the Help Scout credential as a server-side secret reference.
  3. Choose mailbox, conversation, thread, team, user, and docs targets.
  4. Run preflight, then sync with cursor checkpoints.

What Pantasso sees: Only approved Help Scout mailboxes and resources.

Signed Webhooks

Use signed webhooks when internal systems, SaaS tools, forms, build pipelines, or workflow tools should send events directly to Pantasso.

  1. Create a webhook connector manifest with the approved event types.
  2. Store the signing secret as a server-side secret reference.
  3. Require idempotency keys or stable event ids.
  4. Verify signatures, then ingest events with hash checkpoints and audit links.

What Pantasso sees: Only signed, approved event payloads.

Connector SDK

Use the Connector SDK when a specialized source needs a first-class Pantasso connector.

  1. Define a connector manifest with source type, scopes, capabilities, and payload schema refs.
  2. Normalize provider records into Pantasso message envelopes.
  3. Emit checkpoint, source-payload audit link, and sync-status records.
  4. Add tests that prove pagination, redaction, checkpointing, and canonical output.

What Pantasso sees: Only what the custom connector emits under its approved manifest and scope.

After connecting

Once a source is connected, Pantasso:

  • Imports approved content into structured workspace objects.
  • Makes the content available for cited retrieval queries.
  • Shows source health in the workspace dashboard.
  • Reports any sync issues or access problems.
  • Records checkpoints, audit references, and replayable source payload evidence where the connector supports replay.

You can disconnect or modify source access at any time from the workspace control plane.