Contract-tested connectors · one-way
Shopify → Xero
TackQuote can run customer Flows from Shopify to Xero when both systems are connected. Each record type has its own page so a Customer path is not described as if it were an Order path.
Shopify Customer → Xero
A customer record on Shopify is normalized by TackQuote and written to Xero when the Flow is active and both connections pass server validation.
- 1
A customer record is read from Shopify (read, webhook).
- 2
Shopify can emit a webhook for this record type, which TackQuote can use as a Flow trigger when that webhook is already forwarded into Flows.
- 3
TackQuote calls the Xero Customer writer and requires a destination id or an explicit verified result before marking the run successful.
Frequently asked questions
Which Shopify → Xero records can TackQuote actually move?
Only the record types listed on this page: customer. Product Flows are omitted until an event-specific product writer exists.
What does the evidence tier on this page mean?
Both connectors declare the operations the Flow engine calls, and both are covered by connector contract tests. That is a statement about the two connectors, tested separately. This pair has never been recorded running end to end, and this is not a production-support commitment.
Does “Start with this Flow” create a live Flow?
No. The button opens the Flow builder with this source, destination, and record type selected. A Flow is stored only after both connections exist and the API accepts the combination.
Open the Shopify → Xero builder
This selects the pair in the builder. It does not create a Flow until both connections exist and the server accepts the combination.