WisebotAI
Use cases & roadmap

Coming soon connections (+ more sources)

Planned and requested connectors beyond today’s uploads, crawl, and MCP integrations—aligned with the “+ More Sources” roadmap.

Coming soon connections (“+ more sources”)

Today you can upload files, crawl websites, connect MCP integrations (Slack, GitHub, Google, Notion, Confluence), and use Channels (WhatsApp, Facebook, Instagram, Telegram, SMS) plus the widget.

The “+ More Sources” lane on the platform map is where we add enterprise connectors so WisebotAI can sync, ingest, and understand data where it already lives—without another migration.

Connection themes (roadmap)

Below are typical requests; availability and order depend on product roadmap and your plan. Treat this as a planning guide, not a commitment date for each item.

CRM & revenue

  • Salesforce — Accounts, cases, opportunities for support and sales copilots.
  • HubSpot — Marketing and CRM context for lead and ticket workflows.
  • Pipedrive / Copper — Lighter CRMs for SMB pipelines.

Helpdesk & ITSM

  • Zendesk — Deep ticket bi-directional sync (beyond generic APIs).
  • Intercom / Front — Conversations and macros.
  • ServiceNow / Jira Service Management — Enterprise IT and change workflows.

Work management & dev

  • Jira / Linear / Asana — Issues, sprints, and approvals for operations use cases.
  • GitLab — Alongside existing GitHub MCP patterns.

Data platforms

  • Snowflake / BigQuery — Governed read-only analytics for reporting answers (with strict RBAC).
  • Postgres / MySQL — Read replicas or approved views for internal ops Q&A.

Email & calendar (expanded)

  • Microsoft 365 / Google Workspace — Shared mailbox and calendar automation beyond today’s ad hoc flows.
  • Thread-level ingestion with retention policies.

Industry-specific

  • EHR / practice systems (healthcare) — Through approved APIs and BAA-covered vendors only.
  • MLS / transaction platforms (real estate) — Listing and showing data where permitted.
  • Core banking APIs (financial) — Via partner gateways and compliance review.

How to request a connector

  1. Note your industry and system of record (see Use cases overview).
  2. Share read vs write needs and compliance constraints (HIPAA, SOC2, etc.).
  3. Pair with MCP or custom tools today if a generic HTTP or private MCP server can bridge the gap.

Clarity note

This page lists roadmap connectors. For currently available channels and their setup paths, use Channels overview. For plan and billing constraints, treat dashboard Billing as source of truth.

For execution sequencing and rollout gates, see the internal roadmap plan in docs/roadmap/EXECUTION_DETAILS.md.

Connector presets from this list are exposed in dashboard Agent Settings -> Tools -> Custom API Tools so teams can add and enable them per-agent before live upstream APIs are fully wired.