Pantasso Connector Directory

Pantasso Connector Directory

Use this directory to see which company tools Pantasso can connect today and what kind of setup each connection requires. Each entry explains what Pantasso reads, how access is approved, and what evidence you can review after a sync.

Pantasso Data Platform (PDP) is the long-form platform reference used in technical material. The maturity labels below distinguish live app flows from developer/runtime support and planned work; they are not interchangeable.

The directory is not a list of logos. A Pantasso connector is complete only when it can create source evidence that supports SQL inspection, cited retrieval, agent context, replay, and audit.

Maturity Labels

What Every Connector Must Prove

Every connector in Pantasso should provide:

• Scoped approval: only approved channels, folders, projects, accounts, tables, mailboxes, calendars, files, event types, or API resources are read.
• Preflight evidence: credentials, target bounds, size risk, and source availability are checked before sync.
• Checkpointed ingest: each run records cursor, timestamp, offset, hash, or manual checkpoint state.
• Canonical mapping: provider payloads become Pantasso people, teams, conversations, messages, documents, files, tasks, projects, decisions, artifacts, meetings, or audit packets.
• Replayable payloads: source payload references are retained so a run can be debugged or replayed without guessing.
• Cited use: records are queryable through cited retrieval, SQL/object inspection, and scoped agent tools.
• Operational proof: source health, diagnostics, run status, and audit refs are visible after sync.

Hosted Flow Complete Families

Slack

Slack brings approved channels, threads, messages, and users into Pantasso so decisions, requests, handoffs, and working context become cited company memory. Success means selected channels sync with thread context, freshness, source refs, cited retrieval, and audit evidence.

Telegram

Telegram brings approved bot-visible chats into the same workspace as docs, files, and project work. Success means each approved chat has checkpointed message ingest, participant context, source health, cited retrieval, and audit refs.

Google Drive and Docs

Drive and Docs connect approved folders and documents so specs, notes, plans, policies, and shared files stay current and citable. Success means folder scope, Docs extraction, file metadata, first sync, freshness, citations, and replayable source payload evidence are visible.

Gmail

Gmail connects approved mailbox users, labels, and queries when commitments, approvals, or handoffs live in email. Success means bounded message and thread ingest, spam/trash policy, freshness, cited retrieval, and source audit are available.

Google Calendar

Calendar brings approved events, attendees, deadlines, and operating rhythm into workspace context. Success means calendar ids, time windows, event sync, deleted-event policy, freshness, and cited meeting context are recorded.

Google Sheets

Sheets connects approved spreadsheets and ranges for trackers, budgets, lists, and tabular facts. Success means range-scoped rows are imported with provenance and made available for object inspection, retrieval, and dashboard inputs.

Google Admin Directory

Google Admin Directory connects approved users and groups for identity resolution, ownership context, and policy defaults. Success means directory scope is recorded, people and teams are mapped, and source health is visible.

GitHub

GitHub connects approved repositories, issues, pull requests, and comments. Success means repository scope, updated-at checkpoints, project/task objects, cited engineering context, and source-health evidence are present.

Linear

Linear brings approved issues, projects, teams, and status metadata into Pantasso. Success means product work can feed roadmap briefs, task context, decision tracking, and active-work summaries.

Jira Cloud

Jira Cloud connects approved sites, projects, and JQL bounds. Success means bounded issues, epics, blockers, and sprint work become cited project context with preflight and source-health evidence.

Notion

Notion connects approved pages and databases for knowledge bases, notes, specs, and wikis. Success means visible pages or database targets sync into document, project, task, and decision context.

HubSpot

HubSpot brings approved contacts, companies, deals, tickets, and CRM context into the data plane. Success means object allowlists, property bounds, archived record policy, first sync, cited retrieval, and audit evidence are in place.

Vercel

Vercel connects approved teams, projects, deployments, and release metadata. Success means release context can support operations briefs, incident handoff, deployment-aware answers, and audit review.

Files and Obsidian

Files and Obsidian provide the fastest path for approved Markdown, text, JSON, and local note folders. Success means uploaded or configured files pass preflight, sync into workspace objects, answer cited questions, and carry backup and audit evidence.

Platform Path Complete Families

Supabase

Supabase imports approved tables through bounded PostgREST targets. Success means project URL, table allowlist, row identity columns, offset checkpoints, canonical writes, retrieval context, and replayable source payloads are present.

MCP-compatible JSON

MCP-compatible JSON imports structured agent-memory exports, protected JSON URLs, or files. Success means idempotent hash checkpoints, normalized records, replay support, and cited retrieval over imported memory.

Runtime Complete Expansion Families

Microsoft 365

Microsoft 365 brings Teams, Outlook, SharePoint, OneDrive, Planner, and Entra ID context into Pantasso through Microsoft Graph. Success means Graph target definitions, OAuth scope review, OData pagination checkpoints, message envelopes, source-payload audit links, and cited use across messages, files, meetings, tasks, users, and groups.

Salesforce

Salesforce connects approved objects and SOQL bounds for accounts, contacts, opportunities, cases, tasks, and campaigns. Success means object allowlists, field bounds, timestamp checkpoints, normalized CRM records, cited account briefs, and audit evidence.

Stripe

Stripe connects events, charges, invoices, subscriptions, products, and accounts. Success means event-type targets, cursor checkpoints, redacted diagnostics, replayable payment event history, and evidence suitable for billing operations review.

Shopify

Shopify connects approved orders, products, fulfillments, inventory, and contact records. Success means shop-domain scope, resource allowlists, date windows, checkpointed pages, protected-data posture, and commerce records that can be used in support, finance, and operations.

QuickBooks Online

QuickBooks Online connects invoices, bills, payments, vendors, items, and accounts. Success means realm scope, query bounds, updated-time checkpoints, finance objects, transaction lookup, and audit-ready source evidence.

Xero

Xero connects invoices, contacts, bills, payments, bank transactions, and accounts. Success means tenant scope, resource allowlists, updated-time checkpoints, finance context, cash-flow review support, and replayable payloads.

Structured Database

Structured Database connects approved relational, warehouse, or analytical tables through bounded query targets. Success means connection references, table allowlists, primary-key and timestamp checkpoints, normalized rows, SQL inspection, retrieval context, and reconciliation support.

Zendesk

Zendesk connects approved tickets, comments, users, organizations, and help-center articles. Success means subdomain scope, ticket query bounds, comment inclusion, updated-time checkpoints, token redaction, support briefs, and source-payload audit links.

Intercom

Intercom connects conversations, conversation parts, companies, contacts, admins, and tags. Success means workspace scope, cursor pagination, updated-time bounds, normalized conversation records, support trend review, and cited retrieval.

Freshdesk

Freshdesk connects tickets, conversations, contacts, companies, agents, and solution articles. Success means domain scope, resource allowlist, updated-time checkpoints, normalized support records, knowledge lookup, and sync status.

Help Scout

Help Scout connects mailboxes, conversations, threads, teams, users, and docs. Success means mailbox scope, thread inclusion, cursor pagination, support handoff context, knowledge lookup, and replayable payload evidence.

GitLab

GitLab connects approved groups, projects, issues, merge requests, pipelines, commits, and notes. Success means group/project bounds, resource toggles, updated-time checkpoints, engineering briefs, and cited delivery context.

Bitbucket

Bitbucket connects approved workspaces, repositories, pull requests, issues, commits, and pipelines. Success means workspace/repository scope, cursor pagination, normalized code-work records, delivery summaries, and audit refs.

PagerDuty

PagerDuty connects incidents, services, escalation policies, users, on-call schedules, and status updates. Success means service and team bounds, incident windows, timestamp checkpoints, incident briefs, escalation context, and source health.

Datadog

Datadog connects monitors, events, incidents, service catalog entries, dashboards, and SLOs. Success means site/account bounds, timestamp windows, rate-limit diagnostics, reliability context, and cited operations review.

Sentry

Sentry connects approved organizations and projects for issues, events, releases, commits, and alerts. Success means project bounds, issue filters, timestamp checkpoints, error triage context, release health review, and audit evidence.

Cloudflare

Cloudflare connects zones, DNS records, firewall events, logs, Workers, Pages projects, and analytics. Success means account/zone scope, time-window bounds, edge operations context, security event review, and replayable payloads.

AWS CloudTrail

AWS CloudTrail connects approved event history for account activity, service actions, identities, resources, and regions. Success means account/region scope, lookup attribute bounds, timestamp checkpoints, cloud audit review, and replayable audit payloads.

Signed Webhooks

Signed Webhooks accept approved events from internal systems, SaaS webhooks, forms, build pipelines, and workflow tools. Success means signature verification, event-type allowlists, idempotency keys, hash checkpoints, normalized event records, replay, and audit evidence.

Connector SDK

The Connector SDK is the extension path for specialized sources. Success means new connectors can emit deterministic manifests, normalized message envelopes, checkpoints, source-payload audit links, sync status, redacted diagnostics, and canonical records that work with SQL, retrieval, agents, replay, and audit.

Directory Growth Rule

Pantasso should add new connectors only when they strengthen the shared data plane. A new connector is ready for the directory when it can prove source scope, preflight, checkpointed ingest, canonical mapping, cited use, and operational evidence in the same contract used by the rest of the platform.