Outbound sync (BigQuery)
Outbound sync is the BigQuery approach for
getting Twelfth’s outputs into your own systems. Twelfth writes its results —
recommendations, decisions, and tracked pricing — to a destination dataset you
nominate, so your BI tools, reporting, and downstream systems can read them
alongside your other data.
It is inquiry only: outbound sync writes to a reporting destination you
choose for consumption. It never writes back into your operational systems, and
it doesn’t act on your behalf anywhere. Reach it from Settings → Integrations →
Google BigQuery; it’s set up with Twelfth rather than fully self-serve.
Outbound sync is configured with your Twelfth contact — you nominate the
destination and the tables you want. Only workspace owners and admins can
connect or change a warehouse connection.
When to use this
Use outbound sync when:
- You want Twelfth’s recommendations and decisions in your warehouse to blend
with your own reporting. - Another downstream system (a BI dashboard, a planning tool, a data mart) should
read Twelfth’s outputs.
This is the mirror of the inbound models: instead of Twelfth reading from your
warehouse, Twelfth writes its outputs to a destination you control.
How it works
- Nominate a destination. Choose the BigQuery dataset (in your project, or a
shared one) that should receive Twelfth’s outputs. - Grant write access to that destination only. Twelfth writes solely to the
destination you name — nowhere else. - Pick what syncs. Choose which outputs to publish — for example price-change
recommendations, purchase-order recommendations, stock-transfer
recommendations, and tracked pricing — and Twelfth keeps them refreshed on a
schedule.
Security and guarantees
- Inquiry only. The sync is for consumption downstream — it never writes back
into your operational systems and never changes source data. - Destination-scoped. Twelfth writes only to the destination dataset you
nominate, and nothing outside it. - You choose the payload. Only the outputs you select are published.
Related
- BigQuery overview — the two models and three approaches
- Customer-managed BigQuery — read-only inbound serving contract
- Transaction inbound — read raw transaction data in
- Request an integration — ask Twelfth to set this up