Which systems does Hub support?

Hub connects Salesforce, HubSpot, Shopify, Zendesk, Jira, Xero, and a growing library of managed MCP connectors. If a connector does not exist, we build it for you.

What if my system is not listed?

We build it. Hub is designed to grow with your stack — custom MCP connectors, scoped OAuth, and the same governance as managed ones.

How does Hub connect to Core and Atlas?

Hub provides the API connections Core uses to look up customers, orders, and tickets, and to propose Defined Actions. Atlas can also ingest documents from connected systems through Hub.

Is Hub secure for enterprise use?

Yes. Scoped OAuth, encrypted connections, role-based access, health monitoring, and a full audit trail on every call. Built for regulated teams that need visibility without sprawl.

Platform / Core PreSorted Atlas Hub

PreSorted Hub

Your stack, connected - governed, visible, ready for email.

PreSorted Hub is PreSorted's integration layer. Connect CRM, commerce, support, and custom systems once - then use them in investigation steps and Defined Actions, with health checks and credentials in one place.

View connections Book a demo

Connections

5 Healthy · All Scoped

Salesforce 142 ms Connected

salesforce . lookup_customer salesforce . add_note salesforce . update_contact

Shopify 98 ms Connected

shopify . list_orders shopify . issue_refund shopify . get_customer

Zendesk 115 ms Connected

zendesk . create_ticket zendesk . update_ticket zendesk . add_comment

PreSorted Atlas 61 ms Connected

atlas . query_policy atlas . search_docs atlas . get_citation

＋ Your ERP - We Build It

capabilities manifest in review

What Hub Is

MCP integrations built for operators, not just developers.

Hub uses the Model Context Protocol to expose real operations from your systems - catalogued, testable, and scoped to what your playbooks are allowed to call.

salesforce . lookup_customer shopify . list_orders zendesk . create_ticket shopify . issue_refund atlas . query_policy

You see Connections - status, tools, latency - not a black box of API spaghetti. Every operation is named, every credential lives in one place.

Hub + Core

Lookups in Reason. Writes in Execute.

Hub plays a different role in each phase of the pipeline - and never steps outside it.

Read phase Investigation (read)

Playbook steps call read operations: salesforce.lookup_customer


												shopify.get_orders


												atlas.query_policy

Write phase Defined Actions (write)

Proposed: create ticket, update notes, refund, replacement — gated until approved.

Nothing writes on its own.

Boundary Scope

Only operations enabled for your org appear in patterns — no surprise tool calls, ever.

What We Connect - and What We Build

Available now, and growing with you.

Common systems work out of the box. Industry-specific ones follow the same manifest - built for you on request.

Available now

PreSorted Atlas

atlas . query_policy atlas . search_docs

Salesforce

salesforce . lookup_customer salesforce . add_note

Shopify

shopify . list_orders shopify . issue_refund shopify . get_customer

Zendesk

zendesk . create_ticket zendesk . update_ticket

How we extend

New MCP connectors follow the same capabilities manifest. Your patterns reference operations - not raw API endpoints. That's how we add industry-specific systems without rewriting Core.

operation: erp.check_stock

inputs: sku, warehouse

outputs: qty, eta

mode: read

Request an integration → tell us the system; we ship the connector.

Why MCP Matters - in Plain English

One protocol. Many systems. One approval model.

Every connector behaves the same way, so governance never depends on which system you're touching.

Catalog

Each tool is named, typed, and documented — you always know what a pattern can call.

Test

Connection health verified before go-live — latency, auth, and permissions checked.

Trace

Every call visible in the email workbench — what was asked, what came back, when.

Governance

Writes never run without Defined Action approval — reads inform, humans decide.

Example

Chargeback dispute - evidence ready, approval gated.

Hub pulls order and tracking from connected systems; you approve the dispute pack.

Chargeback notification

Chargeback filed for order #ORD-80234 · $245.00 — reason: item not received. Evidence deadline is May 20. Please prepare and submit the dispute pack.

High Risk

1 Read

Chargeback · $245.00 Item not received Deadline May 20 Financial dispute

2 Reason

Order + tracking retrieved Delivered May 5th · signature No prior non-receipt contact Evidence pack compiled

3 Draft

“Evidence summary prepared for dispute submission.”

Order confirmation Tracking record Signed delivery

4 Propose

Not submitted to Stripe Zendesk dispute · May 20 flagged Finance manager alerted

Approve

Deadline met, evidence complete, dispute winnable.

Review Trace Edit Draft Approve & Send Escalate

FAQ

Hub questions, answered.

Connectors, custom builds, and how Hub powers Core.

PreSorted Hub is the integration layer. Connect CRM, commerce, support, and custom systems once — then Core uses them in Read, Reason, and Execute, with credentials, health checks, and scopes in one place.