Integrations
Open Settings → Integrations to review operational system connections. Every connection is inbound and read-only, shown against each tool in the list.
Slack and Google Chat are the tools Twelfth posts to, not reads from, so they have their own section — see Comms & chat. Integrations covers the operational systems Twelfth reads from.
The tools appear as a single list — connected tools sort to the top, everything else follows in catalogue order. You can filter by category and switch between grid and table views. Each row shows the tool, what it reads, and its one action.
Detailed guides
Every connector has its own page — the table below links each one. The most-used
guides:
- Shopify — connect a store over a live, read-only install.
- Google Merchant Center and Google Search Console — read-only Google connections over one shared grant.
- Google BigQuery — read-only queries against your own warehouse, with three approaches: customer-managed, transaction inbound, and outbound sync.
- Custom integrations — a bespoke read-only pipeline (S3, GCS, SFTP, read replica, or API).
- Request an integration — ask for a new connector, a deeper one, or missing data.
Available connections
| Connection | Category | Intended use | Current status |
|---|---|---|---|
| Shopify | Commerce | Orders, products and inventory | Connect a store from this page |
| Google BigQuery | Data warehouse | Read-only warehouse queries from your own dataset | Connect a dataset from this page |
| Google Merchant Center | Commerce | Product feed, prices and availability | Connect from this page, then choose a Merchant ID/domain |
| Google Search Console | Marketing | Search performance, queries and verified sites | Connect from this page, then choose a verified property |
| Snowflake | Data warehouse | Read-only warehouse queries from your own database | Planned |
| Databricks | Data warehouse | Read-only lakehouse queries from your own catalog | Planned |
| Retail Express | Retail & POS | Operational source of truth; syncs every 15 minutes | Planned |
| Adobe Commerce (Magento) | Commerce | E-commerce mirror | Planned |
| POS data feed | Retail & POS | Network sales and volume | Planned |
| Calendar | Workplace | Meeting-preparation briefs | Planned |
| Workplace | Briefing delivery and supplier threads | Planned | |
| Blue Yonder | Planning | Assortment and space | Planned |
Shopify has a self-serve install flow: enter your *.myshopify.com domain and choose Connect. Google Merchant Center and Search Console use incremental Google authorization: they are not requested at login, and each Connect action asks only for that integration’s scope. After consent, choose the Merchant ID or verified Search Console property the workspace should use. Google BigQuery has its own connect page (config-only, read-only). Owners and admins can connect and disconnect connectors, and each option only appears where that connector is configured for the environment. Some workspaces show BigQuery as managed by Twelfth instead of a self-serve connect flow.
Google data access
Twelfth keeps one encrypted, refreshable Google grant per workspace and adds scopes to it only when an owner or admin connects another Google integration. Connecting Search Console does not grant Merchant Center access, and connecting Merchant Center does not grant Search Console access. Both integrations use read operations only.
Use the same Google account when adding a second integration. Disconnect Google revokes the shared grant, so it disconnects Search Console, Merchant Center, and any Google Chat permission for that workspace together.
One store, one workspace
A Shopify store can be connected to only one Twelfth workspace at a time. If you try to connect a store that another workspace already holds, the connect dialog shows a warning and stops — no duplicate connection is created. To move the store, an owner or admin disconnects it from the other workspace first (its Manage → Disconnect), then connects it here. This keeps a single, unambiguous owner for each store’s read-only sync.
Custom integrations
For a system that isn’t listed — a data warehouse, an internal API, a nightly export, or a bucket of transaction or customer data — choose Set up on the Custom integration row. Twelfth reads it through a bespoke, read-only pipeline. See Custom integrations for the static-IP whitelist, the supported data shapes (SFTP, S3/GCS, read replica, API), and how the ETL is built and synced.
Requesting a connection
Planned connectors offer Request instead of Connect, and the Request an integration row at the end of the list opens the same form without preselecting a tool. See Request an integration for what each request option covers.