Moby connected system / 01

Every tool becomes part of the answer.

Integrations build durable business memory in the warehouse. Connectors bring live user context and approved action. Moby uses both to answer and operate.

Capabilities depend on connected accounts, granted permissions, plan, and the tools enabled for your team.

LIVE ORCHESTRATION / CONCEPTUAL VIEW
01 / Gathering context
Reasoning layer Moby Reading the business
Shopifycommerce truth
BigQuerywarehouse context
Slackdecision loop
Drivesource material
Meta Adsapproved action
Sheetsoperating ledger
HubSpotaccount context
Gmaildraft + send
Decision briefexceptions ranked
Launch decknarrative assembled
Operating sheetowners + next steps
Approval gate
What moved yesterday? Context → work → review → action
Capability classes User-level connector Warehouse integration Availability varies
One operating layer / 02

The work does not happen in one app.

Connectors make the handoffs visible: where context comes from, what Moby creates, and where an approved change can land.

01 / READ

Read the business.

Pull the thread through commerce, ads, support, CRM, documents, calendars, messages, and warehouse data without pretending those sources mean the same thing.

ShopifyAmazonBigQueryHubSpot
02 / MAKE

Make the work.

Turn business context into briefs, reports, models, decks, sheets, forms, creative directions, replies, and plans that are ready for review.

SlidesSheetsDriveNotion
03 / ACT

Change the system.

With the right permissions and approval, update campaigns, send messages, schedule meetings, publish work, sync audiences, and run recurring operating loops.

MetaGoogle AdsGmailCalendar
Workflow theater / 03

See the handoff, not just the logo.

Each recipe starts with real context, passes through a reasoning step, produces useful artifacts, and makes the action boundary explicit.

The payoff / 04

What changed yesterday, why, and what should we do before noon?

01Orders
02Spend
03Attribution
04Support
05CRM
06Plan
07Message
08Action
Trust boundary / 05

Read broadly. Write carefully.

Moby can work across a wide surface. Consequential actions still need the exact target, the current state, a clear proposed state, and the permission to proceed.

01

Preserve the exact account, entity, date range, metric, source, and scope.

02

Read the current state before a consequential write.

03

Show the user what will change and wait for approval when required.

04

Claim applied, sent, published, or scheduled only after the owning connector confirms it.

Budget change Review required
Target
Google Ads / Brand Search
Current
$4,800 per day
Proposed
$4,200 per day
Trigger
Contribution fell below the confirmed efficiency threshold.
Evidence
Attributed contribution + platform delivery + current budget owner.
Next
Approve, revise, or hold. No live change has been applied.
Connector directory / 06

A connector is useful when it has a job.

This directory mirrors the connector catalog itself. Paid-media and lifecycle integrations live in the integration layer, so they are intentionally excluded here.

0 connectors

No connector matches that view.

Clear the search and filters to return to the full switchboard.

Two connection layers / 07

Connectors act. Integrations remember.

Connectors are enabled per user and are mainly action-oriented, while still able to read live context. Integrations sync at the shop or account level and persist normalized history in the Triple Whale data warehouse.

User-level connector

Live context and action.

A person connects Slack, Gmail, GitHub, Zoom, or another tool. Moby can retrieve current context and perform supported actions with that user’s permissions.

Per userRead + writePermission scopedAction first
Warehouse integration

Durable business memory.

A shop or account connects commerce, media, lifecycle, fulfillment, and warehouse platforms. Their history is stored, normalized, and available for repeated analysis.

Shop levelHistorical syncNormalized dataWarehouse first

The same platform can live in both layers. Gmail can be a personal connector for searching or sending email; Google Workspace data can also participate in shop-level reporting. Meta can be a warehouse integration for historical ad delivery and a separate permissioned action surface for supported campaign work. The scope, permission model, and job determine the layer.

Motion explainer / 30 secondsConnectors + integrations
One business / two connection layers

Your systems connect in two fundamentally different ways.

One layer remembers the business. The other reaches into the tools where people work.

The distinction

Connectors are personal. Integrations are persistent.

Connectors

Enabled per user. Read current context. Take supported action with the user’s permissions.

SlackGmailGitHub

Integrations

Enabled for the shop. Sync history into the warehouse. Normalize the data for repeated analysis.

ShopifyMetaKlaviyo
Warehouse memory

Integrations keep the history available.

ShopifyOrders / refunds / productsSynced
MetaSpend / delivery / campaignsSynced
KlaviyoCampaigns / lifecycle activitySynced
AmazonMarketplace / ads / revenueSynced
WarehouseDurable + normalized
shop-level memory
Moby operating loop

Memory answers the question. Connectors move the work.

Revenue historyWarehouse context
Campaign deliveryWarehouse context
Customer lifecycleWarehouse context
MobyReason + decide
Send Slack briefUser connector
Draft Gmail replyUser connector
Create follow-upUser connector
The complete system

Business memory plus permissioned action.

Warehouse integrationsWhat the business knows
+
User connectorsWhere the work happens
=
MobyContext that can act
0:00 / 0:30
Sources: connector catalog screenshots, Triple Whale public integrations page, and current Help Center integration documentation. Product model: connectors are user-scoped; integrations are shop/account-scoped warehouse syncs. Playable HTML motion presentation; no MP4 has been rendered.
Warehouse integrations / 08

The business data layer.

These shop- or account-level integrations sync durable business history into Triple Whale or move governed data through warehouse and reporting pipelines. Search the full named catalog below.

60+Pre-built integrations in Triple Whale’s public product claim.
77Distinct named integrations and data pipelines cataloged here.
11Practical families from commerce and media to warehouses and CRM.
0 integrations

No integration matches that view.

Clear the search or select another category.

Evidence boundary: Triple Whale publicly claims 60+ pre-built integrations but does not publish one exhaustive 60+ list. This directory reconciles the named public catalog, current Help Center documentation, and the latest available in-product integration catalog capture. Beta and catalog-dependent entries are labeled; availability still depends on plan, region, account type, and rollout.
Practical questions / 09

A connector is normally enabled per user and is primarily used to retrieve live context or perform permissioned actions. An integration is enabled for the shop or account and syncs durable historical data into the Triple Whale warehouse.

Where the owning connector supports it, Moby can prepare or perform supported actions. Consequential changes remain permission-aware and approval-gated according to the active policy.

“60+” is the current public product claim, not a maximum. The 77-name directory reconciles the public website, Help Center, and the latest available in-product catalog capture, including regional, beta, input, output, and warehouse pipeline entries.

No. The switchboard and workflow diagrams are conceptual product storytelling. The connector names and capability boundaries are grounded in the current tool and integration evidence used for this build.

The connected teammate / 10

One teammate. Your whole operating stack.

Integrate the systems that hold the business history. Connect the tools where people work. Let Moby reason across both and take approved action where the tools allow it.