Send Shopify reports to Google Chat
Load Shopify into your data warehouse first, link it to the rest of your data with SQL keys, then post orders and their financial status where the store team follows the week. The message comes from your source of truth, not from an API call that can break.
ShopifyConnectedAbandoned Checko…Article Metafiel…ArticlesBlog Metafields
Google ChatIdAband…Compl…Daily 09:00The store team follows the week in Google Chat but sees Shopify orders only when someone opens the admin.
Paste this into your AI assistant. It loads Shopify into your data warehouse with OWOX Data Marts and posts orders and their financial status to the store team's Google Chat space, written up from that Data Mart.
The prompt
Read https://www.owox.com/ai-agent-setup.md and follow it to set up OWOX Data Marts for me, starting from /connectors/shopify-insights-to-google-chat.md. The task: post a daily Shopify summary to our store team's Google Chat space: yesterday's orders, revenue and how many are still unpaid, with a short note under the numbers. Tag the links you give me with utm_campaign=ai-task and utm_term=data-foundation. Use what you know about my context and goals
Shopify Endpoints
25 Shopify endpoints you can import. Each lands in its own table in your data warehouse.
Abandoned Checkouts
Checkout sessions that did not complete — customer info, items, and pricing for recovery campaigns.
20 fieldsTime seriesArticle Metafields
Custom metadata attached to articles — namespace, key, value, and type.
9 fieldsArticles
Blog articles — title, author, publication status, and timestamps.
15 fieldsBlog Metafields
Custom metadata attached to blogs — namespace, key, value, and type.
9 fieldsBlogs
Blogs in the store — title, handle, and template settings.
6 fieldsCollection Metafields
Custom metadata attached to collections — namespace, key, value, and type.
9 fieldsCollections
Product collections — title, sort order, product count, and last updated.
10 fieldsCustomer Metafields
Custom metadata attached to customers — namespace, key, value, and type.
9 fieldsCustomers
Customer accounts — contact info, marketing consent, order history, and lifetime spend.
22 fieldsTime seriesDiscount Codes
Discount codes — type, status, usage limits, and validity window.
12 fieldsFulfillment Orders
Fulfillment orders — items to ship, assigned location, delivery method, and status.
11 fieldsInventory Items
Inventory items (SKUs) — tracking status, shipping requirements, and country of origin.
9 fieldsLocation Metafields
Custom metadata attached to locations — namespace, key, value, and type.
9 fieldsLocations
Physical and virtual store locations — activity status, fulfillment capabilities, and address.
19 fieldsOrder Metafields
Custom metadata attached to orders — namespace, key, value, and type.
9 fieldsOrders
Orders placed in the store — financial and fulfillment status, customer info, totals, and timestamps.
96 fieldsTime seriesPage Metafields
Custom metadata attached to pages — namespace, key, value, and type.
9 fieldsPages
Static store pages — title, handle, publication status, and timestamps.
10 fieldsProduct Metafields
Custom metadata attached to products — namespace, key, value, and type.
9 fieldsProduct Variant Metafields
Custom metadata attached to product variants — namespace, key, value, and type.
9 fieldsProduct Variants
Product variants — SKU, price, inventory quantity, and availability.
18 fieldsProducts
Products in the store catalog — vendor, type, status, inventory, and price range.
21 fieldsTime seriesShop
Store settings — domain, currency, timezone, and plan details.
20 fieldsShop Metafields
Custom metadata attached to the shop — namespace, key, value, and type.
9 fieldsTender Transactions
Payment tender transactions — amount, currency, order reference, and processing time.
7 fields
Why Shopify does not go straight to Google Chat
Shopify records each order and its status, not which ad or session brought it. A message built straight from the source puts the source's own numbers in the space and does not tie them to the rest of the business reliably, at scale or business-ready, so the join happens in a warehouse first.
- An order has a total, a currency and a status, with no ad spend beside it
- The data analyst links the tables by SQL keys and controls what a message may say
- The space reads one scheduled message instead of several tabs and an export
ShopifyOrders, customersGoogle Chat
Data warehouseJoined by idStep 1: Load Shopify into your data warehouse first
Create a Data Mart with Shopify as the source and choose where the data lands. It works with any popular data warehouse.
- 25 endpoints to choose from, each endpoint in its own table
- Authorize with your shop domain and an Admin API access token
- Open the Shopify connector for your data warehouse below
ShopifyData MartGoogle BigQuery
AWS Athena
Snowflake
AWS Redshift
Databricksshopify.ordersStep 2: Link Shopify to ad spend and web analytics
In your data warehouse the model joins Shopify orders to web analytics sessions, and sessions to ad spend by date, source and medium. Pick an industry to see the shape of its model.
- Orders sit beside web analytics sessions, and sessions beside ad spend
- Sessions and orders join by SQL keys, not VLOOKUP and gut feeling
- The measures, such as conversion_rate, are defined once
ShopifyOrders
Facebook AdsAd spend
Google AdsAd spendStep 3: Send Shopify reports to Google Chat
Add an incoming webhook in the Chat space (Apps & integrations, Add webhooks), paste its URL into a Google Chat destination in OWOX, and attach a report of the Shopify Data Mart. The message is a Markdown template.
- The message is a card with the subject, the Data Mart name, your text and a link back to the report
- The table carries name, totalPrice, currencyCode and createdAt
- Tables arrive as monospace blocks, and a long report is split into numbered parts
Google ChatWeeklyWeekly Shopify orders reportnametotalPricecurrencyCodecreatedAtStep 4: Add a short analysis under the Shopify report in Chat
Write the reading under the table in the template, or let an Insight on the same Data Mart write it. Then add a trigger on the Triggers tab: OWOX runs the Data Mart first and checks the sending condition.
- Send always, or only when the result is not empty, so a quiet week stays quiet
- The reading comes from the report's fields and adds no cause the data does not show
- One space can receive several reports, each with its own trigger
Google ChatWeekly Shopify orders reportnametotalPricecurrencyCodecreatedAtAnalysisOrders with totalPrice and displayFinancialStatus.Orders not yet paid are listed apart from settled ones.currencyCode says which totals do not add up directly.Step 5: Reuse Shopify inside OWOX MCP
The Data Mart behind your Chat message also works in OWOX MCP, your assistant for data. Request any report, chat with your data, then get the report in Google Sheets or Excel in one click.
- Ask in plain words; the answer comes from your data warehouse
- Change the Shopify report once and the next Chat message reads the change
Google SheetsOpen
ExcelOpen
- 0.41.0Rotating a connector key is one change: Sources share reusable Credentials
- 0.41.0Reuse one Google Sheets or Google Chat key across Destinations
- 0.39.0Reload a year of history in one backfill, not twelve
- 0.38.0Shopify connector: more orders fields, including line-item discounts
- 0.37.0Clearer connector errors, and custom connectors that handle more APIs
Why OWOX for Shopify in Google Chat
Hand-built bots and webhook scripts post numbers into a space. OWOX also keeps the data yours, linked and ready to model.
- You own the data. Shopify lands in your own data warehouse, in tables you control.
- Orders where the store team talks. The order table is posted where a drop in paid orders gets a reply from the people who can act.
- The webhook stays simple. Paste the space's webhook URL once; it is stored write-only and several destinations can share it.
- Same numbers everywhere. The Shopify Data Mart behind the message also feeds your reports and your AI assistant.
- Maintained for you. No bot code to fix when Shopify changes its API.
You are booked. The invitation is on its way to , with the calendar invite and the meeting link.